- From: Rob Tice <rob.tice@k-int.com>
- Date: Thu, 18 Jun 2009 11:46:29 +0100
- To: <Simon.Cox@csiro.au>, <public-esw-thes@w3.org>
- Cc: <steve.richard@azgs.az.gov>
Apologies for the commercial posting. Our desktop terminology editor (Lexaurus) is entirely format independent and can create and edit many different formats (including SKOS xml, VDEX, Zthes ,XVD etc). http://www.vocman.com/?q=lexauruseditor Cheers Rob Tice -----Original Message----- From: public-esw-thes-request@w3.org [mailto:public-esw-thes-request@w3.org] On Behalf Of Simon.Cox@csiro.au Sent: 18 June 2009 02:53 To: public-esw-thes@w3.org Cc: steve.richard@azgs.az.gov Subject: SKOS tools? Dear SKOS list - The GeoSciML project has been evaluating SKOS to implement its 'controlled concpet' model (see http://www.geosciml.org/geosciml/2.0/doc/GeoSciML/Vocabulary/package-summary .html for the UML representation, and you'll see how SKOS is a close match!). My colleague Steve Richard is the lead editor, on behalf of a consortium including many of the world's leading geological surveys*, for around 25 vocabularies related to geology. This is a significant effort in the natural sciences. Being a happy old XML hacker I can tolerate RDF/XML and a text editor for prototyping. But this obviously ain't acceptable for most users, doesn't scale to production work, and fails to provide the consistency checking and visualization that a proper editor would. We are mighty frustrated (and getting worse!) at the state of tool support. In particular, Protégé, even with the SKOS plugin, appears to be fatally flawed. I've used it from time to time for _viewing_ a concept scheme, but have never been able to successfully round trip through export/import, so it doesn't work as an editor. Steve is now finding further flaws - see below - e.g. labels implemented as objectProperty, no literal support or language attributes. This is all very disappointing. What tools are people people using successfully for development and management of SKOS instances? Simon Cox (*) See http://onegeology.org/technical_progress/geosciml.html and http://onegeology.org/participants/graphical_map.html ______ Simon.Cox@csiro.au CSIRO Exploration & Mining 26 Dick Perry Avenue, Kensington WA 6151 PO Box 1130, Bentley WA 6102 AUSTRALIA T: +61 (0)8 6436 8639 Cell: +61 (0) 403 302 672 Polycom PVX: 130.116.146.28 <http://www.csiro.au> ABN: 41 687 119 230 -----Original Message----- From: stephen richard [mailto:steve.richard@azgs.az.gov] Sent: Thursday, 18 June 2009 9:31 AM To: Cox, Simon (E&M, Kensington) Subject: Re: [Auscope-geosciml] Simple lithology vocabulary in MMI repository Right now I'm mostly frustrated- the new version of Protege (v4, released today) doesn't preserve language attributes on prefLabel elements, and the SKOS tool models prefLabel as an ObjectProperty, so you can't populate it with a literal, and it doesn't appear to be consistent with the current SKOS spec. What I started out to do was clean up the hierarchy in standardLithology, which is a mess. The owl/SKOS tools looked like a possible way to do it. Instead I've spun my wheels for 3 days. The idea is simply to be able to round trip between GeologicVocabulary and some brand of SKOS, for which there is a functional tool, build and fix hierarchies in SKOS, and convert back to GeologicVocabulary to update in the BRGM repository. Meanwhile there are the possibilities of vocabulary services that could assist with document validation and better yet query resolution with hierarchical properties... What's AuScope using for SKOS tools? steve Simon.Cox@csiro.au wrote: > Steve > Good hunting. > > A few comments and a bit of an update about where the AuScope vocabs/vocab-server work is at: > > > i. Terms and Labels - > skos:prefLabel, skos:altLabel, skos:hiddenLabel and skos:notation can and should be used to support the assignment of multi-lingual terms, synonyms, misspellings (!) and symbols to concepts, regardless of the encoding (OWL, SKOS, other RDF languages). The semantics of these are clear and relevant to our needs, and the rdfs:domain of all of these is unrestricted so they can be applied to any rdf resource. > > ... -- Stephen M. Richard Section Chief, Geoinformatics Arizona Geological Survey 416 W. Congress St., #100 Tucson, Arizona, 85701 USA Phone: Office: (520) 209-4127 Reception: (520) 770-3500 FAX: (520) 770-3505 email: steve.richard@azgs.az.gov No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.76/2183 - Release Date: 06/17/09 05:53:00
Received on Thursday, 18 June 2009 10:47:06 UTC