- From: Juan Antonio Pastor Sánchez <pastor@um.es>
- Date: Tue, 10 Aug 2010 12:02:42 +0200
- To: Alistair Miles <alimanfoo@googlemail.com>
- Cc: public-esw-thes@w3.org
Hi Alistair: Yes, basically this is my question. Thinking primarily in an application where a KOS can be represented with several Conceptscheme. A response from Christophe I understand the need to use DC to describe each Conceptscheme as a resource. I would also add SKOS labels for querying and browsing the KOS. For now, the solution I implemented in the KOS Management System, I am developing is: * Each Concept, Conceptscheme and Collection, must be labeled with at least one prefLabel. * Optionally, the user can add Dublin Core Metadata. So, I think it would be best to label a Conceptscheme with at least one prefLabel, and optionally add DC. What do you think? Cheers Juan El día 10 de agosto de 2010 10:39, Alistair Miles <alimanfoo@googlemail.com> escribió: > Hi Juan, > > I'm not sure I understand your question. > > Are you asking whether... > > <X> rdf:type skos:ConceptScheme ; dc:title "My First Thesaurus"@en . > > ...or... > > <X> rdf:type skos:ConceptScheme ; skos:prefLabel "My First Thesaurus"@en . > > ...is best practice? > > Cheers > > Alistair > > On Sat, Aug 07, 2010 at 08:50:12PM +0200, Juan Antonio Pastor Sánchez wrote: >> Hello everyone: >> >> I doubt arises regarding labeling practices of SKOS Conceptscheme. The >> most common practice is the labeling by dc: title. From my point of >> view might have to distinguish between the description of an action by >> a metadata schema (in this case Dublin Core) and the need for >> consistent Conceptscheme from the perspective of the SKOS model. >> >> In the latter case I think would be labeled by concepts prefLabel >> schemes, altLabel, and even hiddenLabel for and applications using >> SKOS data, to query a specific KOS, using these properties. >> >> DC labels should be limited to the description of a SKOS element in >> the environment of other data sets for other applications (such as a >> digital repository). >> >> In this regard, my analysis of most of the SKOS Dataset has led me to >> the conclusion (maybe I'm wrong) that for the most common practice to >> represent a KOS, normally used only one Conceptscheme. >> >> I have the feeling that this practice creates KOS too "monolithics", >> limiting their interoperability and reusability. Perhaps this is why >> normally used dc: title instead of SKOS properties to label >> Conceptscheme. >> >> What do you think? >> >> Greetings. >> >> Juan. >> >> -- >> Ph.D. Juan Antonio Pastor Sánchez >> Dep. of Information and Documentation >> Faculty of Communication and Documentation >> University of Murcia >> phone: +34 868 88 8780 >> http://webs.um.es/pastor >> pastor@um.es >> > > -- > Alistair Miles > Head of Epidemiological Informatics > Centre for Genomics and Global Health <http://cggh.org> > The Wellcome Trust Centre for Human Genetics > Roosevelt Drive > Oxford > OX3 7BN > United Kingdom > Web: http://purl.org/net/aliman > Email: alimanfoo@gmail.com > Tel: +44 (0)1865 287669 > -- Ph.D. Juan Antonio Pastor Sánchez Dep. of Information and Documentation Faculty of Communication and Documentation University of Murcia phone: +34 868 88 8780 http://webs.um.es/pastor pastor@um.es
Received on Tuesday, 10 August 2010 10:03:15 UTC