Skip to content

premis:RightsBasis should be a subclass of prov:Agent/prov:Entity/prov:Activity ? #6

Description

@remiColletGG

Hello there,

I am investigating to use premis/prov to describe data governance at my company (Infrabel, the Belgian railway infrastructure manager).

According to premis' guidelines (https://www.loc.gov/standards/premis/ontology/pdf/premis3-owl-guidelines-20220426.pdf) on page 12 :

Image

One should link premis:RightsBasis to prov:Agent using prov:wasInfluencedBy (or its inverse property, but let's use this example).
However, prov:wasInfluencedBy https://www.w3.org/TR/prov-o/#wasInfluencedBy clearly describes that the domain and range of the property should be a prov:Agent/prov:Entity/prov:Activity. According to https://id.loc.gov/ontologies/premis-3-0-0.html#c_RightsBasis, premis:RightsBasis is not subclassed to any of the three.

While prov-o heavily implies that we should use a more specialized version of prov:wasInfluencedBy, it still looks like premis is bending the rules a little too much here, and should mint its own property to relate a premis:RightsBasis to a prov:Agent (both ways, of course).

To be clear, my use case would look something like :

ex:ABCDataOwnerRights a premis:RightsBasis ;
    premis:governs ex:DataSetABC ;
    prov:wasAttributedTo ex:Michael .

ex:Michael a prov:Agent .

ex:DataSetABC a premis:Object .

Am I misunderstanding something here ? Should I mint my own property to link my ex:DataOwnerRights to a prov:Agent ?

Thanks anyway for this ontology that is in line with a w3c standard, and for the thorough documentation. It is truly a thing of beauty and I am thankful that we have ontologists like you who work for the greater good !

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions