Request: Add a missing objectType subProperty rdano:P80174 [has related entity of nomen]

[jarmosaarikko]

The property rdan:P80174 "has related entity of nomen"
Obviously, this would be pointing to an entity. However, there is only a datatype subproperty nothing within rdano: namespece.

Request

In the namespace http://rdaregistry.info/Elements/n/object/
should you add the property http://www.rdaregistry.info/Elements/n/object/#P80174 ["has related entity of nomen"@en]
and define: rdano:P80174 rdfs:domain rdac:C10012 ; rdfs:range rdac:C10013 .

other cases

There seem to be other similar cases. e.g. rdaa:P50481 "has related entity of family"
If this is an editorial decision, is this explained somewhere, or is this just a slip?

[diseminger]

Hello,

The properties in the format "has related entity of RDA Entity" are intended to relate a RDA Entity to an entity that is a non-RDA entity.

The object element sets specify both a domain and a range for an object property. Both the domain and the range must be an RDA entity in order for the canonical version of a property to have a counterpart in the object element sets. Because the "has related entity of [RDA entity]" properties do not have a range of an RDA entity, they do not appear in the object element sets.

This is also true for properties whose expected value is a concept from a Vocabulary Encoding scheme. For example, the RDA property rdae:P20001 (has content type) is only in the canonical and datatype element sets. It is not in the object element sets, because its expected value is a concept.

There are high-level elements that can be used to relate an RDA entity to another RDA entity. Each RDA entity has a suite of elements in the form "has related [RDA entity] of [RDA entity]". From these elements, all of the other RDA elements are derived.

Hope this helps,
Damian

[jarmosaarikko]

ok, thanks!
I continued looking these and noticed also that there were in some cases two separate properties handling this type or cases, but it was not obvious in the cases I brought up:

• rdaa:P50310 "has related RDA entity of person" - has both types of subproperty
• rdaa:P50482 "has related entity of person" - has only datatype subproperty

At NatLibFI we've run into same kind of mapping problems in our modeling work when trying to define values for a property to be picked up from a controlled vocabulary. If there were a type definition of a particular Class for all the items in a vocabulary, that class could then be defined as the range for the property. But it seems that the RDA registry ValueVocabularies setup would not allow this.