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
ISO 25964 has precoordination but which is the official mapping to RDF (skos-thes is currently offline)? There is http://purl.org/iso25964/skos-thes#CompoundEquivalence but this class (!) seems to operate on labels (properties iso-thes:plusUF and iso-thes:plusUse)
TheSoz had/has(?) CompoundEquivalence similar to ISO 25964
Support of (pre-)coordinated/composed concepts has been added in 0.2.1 but the mapping to RDF is not fully clear. This issue summarizes #48 and #60.
mc2skos supports synthesized number components and uses mads:componentList for ordered parts
GND uses gndo:complexSeeReferenceSubject based on MARC field 260. Example http://d-nb.info/gnd/7507432-1 = http://d-nb.info/gnd/4126823-4 + http://d-nb.info/gnd/4161152-4 is included in JSKOS 0.2.1. MARC 260 is not processed for concept parts in mc2skos yet.
ISO 25964 has precoordination but which is the official mapping to RDF (skos-thes is currently offline)? There is http://purl.org/iso25964/skos-thes#CompoundEquivalence but this class (!) seems to operate on labels (properties
iso-thes:plusUF
andiso-thes:plusUse
)TheSoz had/has(?) CompoundEquivalence similar to ISO 25964
Maybe gndo:complexSeeReferenceSubject can be used for unsorted parts and mads:componentList for ordered parts?
The text was updated successfully, but these errors were encountered: