Publisher as object property versus annotation property

[rsc3]

Use case name

Status:

Identifier:

Creator: Sidney Cox

Deliverable(s): DCAT1.1, DCAT-AP
''Which deliverable or deliverables does this UC relate to?''

Tags

''Optional space-separated list of tags out of the above catalog (extend on demand)''

Stakeholders

data producer, data publisher
''Mandatory list of stakeholders experiencing the problem. When describing the stakeholder, please be as specific as possible (e.g., data consumer, data producer, data publisher, program, etc.) and avoid using the term user.''

Problem statement

DCAT Spec indicates that the range for dct:publisher is Agent which made me think it was an object property, but it is an annotation property and thus this is not a legal range.

''Mandatory statement of the current situation, including a description of the problem, the stakeholders experiencing the problem, and what the stakeholder(s) are expected to supply (i.e. what contextual knowledge are they expected to have available) and/or receive to resolve the problem they are experiencing. In describing the stakeholder, please be as specific as possible (e.g., data consumer, data producer, data publisher, program, etc.) and avoid using the term user.''

Existing approaches

Don't use DCAT, define your own object property with DCAT_AP

''Optional references to standards and examples of established approaches with a potential for reuse in DCAT''

Links

''Optional link list to documents and projects this use case refers to''

Requirements

''Mandatory requirements suggested by this use case''

• Imperative sentence starting with a verb each describing an individual task in order to solve the stated problem

Related use cases

''Optional references to related local (refer to anchor identifier [[#Id...]]) and remote use cases (e.g. POE-WG UCs)''.

Comments

''Optional section for editorial comments, suggestion and their interactive resolution''

---

[andrea-perego]

@rsc3 , thanks for submitting this issue.

Please note that, even though not explicitly defined as such, dcterms:publisher is meant to be used as an object property, as indicated by the dcam:rangeIncludes statement in the DCTERMS definition of this property:

dcterms:publisher
    dcam:rangeIncludes dcterms:Agent ;
    dcterms:issued "2008-01-14"^^<http://www.w3.org/2001/XMLSchema#date> ;
    a rdf:Property ;
    rdfs:comment "An entity responsible for making the resource available."@en ;
    rdfs:isDefinedBy <http://purl.org/dc/terms/> ;
    rdfs:label "Publisher"@en ;
    rdfs:subPropertyOf <http://purl.org/dc/elements/1.1/publisher> .

BTW, OWL annotation properties can also be object properties (see, e.g., rdfs:seeAlso and rdfs:isDefinedBy). I suppose you meant instead "datatype properties".

[andrea-perego]

@rsc3 , unless you have any other comments, we consider this issue as closed.

[rsc3]

Thanks, that was super helpful!

…

On Mon, Mar 7, 2022 at 2:50 PM Andrea Perego ***@***.***> wrote: @rsc3 <https://github.com/rsc3> , unless you have any other comments, we consider this issue as closed. — Reply to this email directly, view it on GitHub <#1462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5JFIUIB4KITHMR2MKPABTU6ZMY5ANCNFSM5PKVFXCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>