- From: Kevin Ford <kefo@3windmills.com>
- Date: Sun, 16 Feb 2014 19:02:47 -0500
- To: public-esw-thes@w3.org
Dear Jacob, When it came time to convert our MARC Organizations dataset into RDF/SKOS, we did not want to lose information and granularity we had collected and maintained for years. We've formally maintained and published multiple codes for each Organization (one code is the "official" one; one code represents a normalized form; another possible code - though not presently included - is an ISIL [1]. Regardless, the ISIL, if we choose to include it, represents yet another perfectly valid code for the same Concept). In any event, we established two different datatypes, one for each code (the "official" one and the normalized one). See, for example: http://id.loc.gov/vocabulary/organizations/dlcmrc.skos.rdf Yours, Kevin [1] http://biblstandard.dk/isil/ -- Kevin Ford Library of Congress Washington, DC On 02/14/2014 01:53 PM, Voß, Jakob wrote: > Hi, > > I am designing a software that uses SKOS data and unsure about how to limit notations. Are multiple notations per concepts actually used? The advise to use custom datatypes is rather unhelpful because RDF has no default mechanism to express information about datatypes. If most concept schemes have only one notation per Concept, I'd rather make this a constraint instead of implementing edge cases that nobody makes use of anyway. See also my question at http://answers.semanticweb.com/questions/26492/are-skos-concepts-with-multiple-notations-actually-used > > Jakob > > -- > Jakob Voß > Verbundzentrale des GBV (VZG) > Abteilung Digitale Bibliothek > Platz der Göttinger Sieben 1 > 37073 Göttingen > Telefon: (49)551 39-10242 > Internet: www.gbv.de >
Received on Monday, 17 February 2014 00:03:17 UTC