The date-related properties are set for today, but may need to be changed to reflect an eventual publication date.
I would like some feedback on the hasMember property, especially related to the rdfs:domain and rdfs:range. The documentation indicates that the domain can be either pcdm:Collection or pcdm:Object (hence the use of the parent class ore:Aggregation). The documentation also suggests that, when the subject is a pcdm:Object, the range can only by a pcdm:Object; however, when the subject is a pcdm:Collection, the range can be either a pcdm:Object or a pcdm:Collection. That constraint is not enforced in this ontology.
This is a draft implementation of the Portland Common Data Model
The date-related properties are set for today, but may need to be changed to reflect an eventual publication date.
I would like some feedback on the
hasMember
property, especially related to therdfs:domain
andrdfs:range
. The documentation indicates that the domain can be eitherpcdm:Collection
orpcdm:Object
(hence the use of the parent classore:Aggregation
). The documentation also suggests that, when the subject is apcdm:Object
, the range can only by apcdm:Object
; however, when the subject is apcdm:Collection
, the range can be either apcdm:Object
or apcdm:Collection
. That constraint is not enforced in this ontology.