You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In RiC-CM v0.2 full draft, the following attributes whose schema value is 'controlled value', correspond to object properties + classes in RiC-O:
Content Type (in RiC-O: "hasContentOfType" object property with range ContentType class)
Documentary Form Type (in RiC-O: "hasDocumentaryFormType" object property with range DocumentaryFormType class)
Language (in RiC-O: "hasLanguage" object property with range Language class)
Legal Status (in RiC-O: "hasLegalStatus" object property with range LegalStatus class)
State (in RiC-O: "hasRecordResourceState" object property with range RecordResourceState class).
The specifications of each of these attributes in RiC-CM v0.2 full draft include the following sentence:
"May be used in a Record Set description when the attribute value is shared by some or all Record members."
In such cases, though in RiC-CM v0.2, as explained very clearly in the introduction to the attributes, the distinction has not been made between Record and Record Set, IMHO it would be far better to make it in RiC-O 0.2. As a matter of fact, content type, doc. form type, language, legal status and state are definitely features of Record or Record Part only - not of Record Set.
So, I suggest we add, for Record Set only, new object properties that could be used to handle the "some members" and "all members" use case.
They sould be useful in many situations, as we all have, for example, existing archival descriptions where a Record Set is associated (indexed) with several documentary form types, and we do not have the description of each of the records included in the record set - we only know that some records in the Record Set are maps, while other are photographs, etc. We cannot lose these data, since they provide important information, and should be queried.
In short, this would result in, e.g. for Documentary Form Type class (as a range):
a "hasDocumentaryFormType" object property, with domain the union of Record and Record Part (as it is now in RiC-O)
a new "hasSomeMembersWithDocumentaryFormType" object property, with domain Record Set
a new "hasMostMembersWithDocumentaryFormType" object property, subproperty of "hasSomeMembersWithDocumentaryFormType", with domain Record Set (if considered useful)
a new "hasAllMembersWithDocumentaryFormType" object property, with domain Record Set
In addition to this, the RecordResourceState class should be renamed RecordState.
The text was updated successfully, but these errors were encountered:
The following is associated with issue #9.
In RiC-CM v0.2 full draft, the following attributes whose schema value is 'controlled value', correspond to object properties + classes in RiC-O:
Content Type (in RiC-O: "hasContentOfType" object property with range ContentType class)
Documentary Form Type (in RiC-O: "hasDocumentaryFormType" object property with range DocumentaryFormType class)
Language (in RiC-O: "hasLanguage" object property with range Language class)
Legal Status (in RiC-O: "hasLegalStatus" object property with range LegalStatus class)
State (in RiC-O: "hasRecordResourceState" object property with range RecordResourceState class).
The specifications of each of these attributes in RiC-CM v0.2 full draft include the following sentence:
"May be used in a Record Set description when the attribute value is shared by some or all Record members."
In such cases, though in RiC-CM v0.2, as explained very clearly in the introduction to the attributes, the distinction has not been made between Record and Record Set, IMHO it would be far better to make it in RiC-O 0.2. As a matter of fact, content type, doc. form type, language, legal status and state are definitely features of Record or Record Part only - not of Record Set.
So, I suggest we add, for Record Set only, new object properties that could be used to handle the "some members" and "all members" use case.
They sould be useful in many situations, as we all have, for example, existing archival descriptions where a Record Set is associated (indexed) with several documentary form types, and we do not have the description of each of the records included in the record set - we only know that some records in the Record Set are maps, while other are photographs, etc. We cannot lose these data, since they provide important information, and should be queried.
In short, this would result in, e.g. for Documentary Form Type class (as a range):
In addition to this, the RecordResourceState class should be renamed RecordState.
The text was updated successfully, but these errors were encountered: