- From: Thomas Bassetto <thomas.bassetto@insa-rouen.fr>
- Date: Mon, 25 May 2009 11:27:50 +0200
- To: public-esw-thes@w3.org
Hello, I want to create a Web Service for a medical database. The response from the Web Service should be a valid SKOS document (inside a SOAP envelope). Hopefully a lot of SKOS elements match my needs. However, there are some additional information without specific SKOS element available. According to http://www.w3.org/TR/skos-primer/#secskosspecialization , "Users can create their own properties and classes and attach them to the standard SKOS vocabulary elements by using the rdfs:subPropertyOf and rdfs:subClassOf properties from the RDF Schema vocabulary". I plan to create an element for each additional information (like <myns:ATCID/>)[1] for defining a specific ID. But the client doesn't agree. He thinks that this solution is "proprietary" since I create new elements which are not described in the norm. He propose two alternate solutions : * use rdf:parseType as attribute to existing SKOS element. To be frank, I can't see how it could be a solution. * create a new attribute to <skos:Concept/> ant put ALL the additional information into it, separated by a coma. Example : <skos:Concept rdf:about="http://site.fake#diagnostic" myns:annotation="ADDINF1=value1,ADDINF2=value2,ADDINF3=value3,..."> What do you think ? I believe that specialising SKOS elements remains the best solution. Moreover, I'm wondering if it's really possible to create a new attribute for <skos:Concept/>. How ? I'm have never used RDF and SKOS before. Finally, I have another question. I want to use JENA[2] in order to generate a Java file to create a SKOS document. JENA needs an ontology or other vocabulary file. In the document called "SKOS RDF Schema"[3] I have found this Schema : http://www.w3.org/2004/02/skos/core.rdf. Is it up to date with the last CR of SKOS Reference ? I hope I'm clear enough. Feel free to ask me further information. Regards, Thomas Bassetto [1] This is not the best example :) For specific ID, I have understand that <skos:notation/> is better. [2]http://jena.sourceforge.net [3]http://www.w3.org/TR/2009/CR-skos-reference-20090317/skos.html
Received on Monday, 25 May 2009 11:04:00 UTC