- From: Sean Bechhofer <sean.bechhofer@manchester.ac.uk>
- Date: Thu, 14 May 2009 15:56:13 +0100
- To: John Graybeal <graybeal@mbari.org>
- Cc: public-swd-wg@w3.org, Carlos Rueda <carueda@mbari.org>, Bermudez Luis <bermudez@sura.org>
John Thanks for your input. We are using the SKOS issue tracker to manage implementation experience, and this has been logged in the SKOS Issue tracker as [ISSUE-220] and [ISSUE-221]. Sean On 8 Apr 2009, at 01:08, John Graybeal wrote: > Alistair, Antoine, > > Congratulations on your release, good show. > > We will be basing the next release of our MMI semantic framework[4] > tools[1],[2],[3] in large part using the latest SKOS release. We > expect the next release to be out within a month or so. > > Some details are below. > > === Vocabularies/Mappings > > We will be creating a very large number of vocabularies, many of > them from existing non-RDF resources on the web. Many of the > details will vary. We will be using SKOS as thoroughly as makes > sense to us (probably pretty thoroughly). > > We will be creating a number of mappings (we already have a number > using the previous SKOS). These will be community-owned so many of > the details will vary. The data will all be publicly available at > the repository [1]. > > == Software Implementations == > > * name of the software: MMI Ontology Registry and Repository, > including voc2rdf [2] and VINE[3] tools. > > * name of person and/or organisation responsible for the > implementation > Implementer: Carlos Rueda > Principal Investigator: John Graybeal > Organization: Marine Metadata Interoperability > Organization: Monterey Bay Aquarium Research Institute et al > > * URLs for software home page and/or download location if publicly > downloadable: see [1] > > * can the software read SKOS data? Yes > > * can the software write SKOS data? Yes > * can the software check consistency of SKOS data with respect to > the SKOS data model? not sure...probably not > > - main purpose and functionality of the softwarer: community > ontology repository for marine science (and ...) > - the programming language and/or software frameworks used: Java > mostly; details on request > - any other URLs describing the software or providing further > information: see [1], [2], [3], [4] > > John > > P.S. Expert consultation on our use of SKOS will be welcome... > (See the VINE interface mockup, notably the pop-up help for the > buttons in the middle) > > [1] Repository: http://mmisw.org/or > [2] voc2rdf: http://mmisw.org/ontmd/voc2rdf > [3] VINE: description of download at http://marinemetadata.org/ > vine, web-based mockup at http://mmisw.org/vine > [4] Semantic Framework description: http://marinemetadata.org/ > semanticframework > > > > > semantic-web@w3.org > From: aisaac@few.vu.nl > Subject: Request for Implementation Input: SKOS Simple Knowledge > Organization System > > Date: April 7, 2009 3:38:06 PM PDT > > To: public-esw-thes@w3.org, semantic-web@w3.org, DC- > GENERAL@JISCMAIL.AC.UK, dc-architecture@JISCMAIL.AC.UK, > ecoterm@npogroups.org, public-owl-dev@w3.org, public-owl-wg@w3.org, > facetedclassification@yahoogroups.com, NKOS-L@OCLC.ORGand 8 more… > Cc: public-swd-wg@w3.org > > The W3C Semantic Web Deployment Working Group is pleased to announce > the publication of a Candidate Recommendation for the Simple Knowledge > Organization System (SKOS) Reference: > > http://www.w3.org/TR/2009/CR-skos-reference-20090317/ > > A new Working Draft of the accompanying SKOS Primer has also been > published: > > http://www.w3.org/TR/2009/WD-skos-primer-20090317/ > > The Working Group now *calls for implementations.* > > We would like to hear of any vocabulary (thesaurus, classification > system, subject heading system, taxonomy or other KOS) or mapping > between vocabularies that has been published in the Web as > machine-readable data using SKOS, and/or has been made available via > programmatic services using SKOS. > > We would also like to hear of any software that has the capability to > read and/or write SKOS data, and/or can check whether a given SKOS > dataset is consistent with the SKOS data model. > > If you would like to notify us of a vocabulary, vocabulary mapping, > and/or software as a SKOS implementation, *please send an email to > public-swd-wg@w3.org before 30 April 2009*, providing the information > described below. Please also begin the subject line with "SKOS > Implementation:". > > == Vocabulary Implementations == > > If you are notifying us of one or more vocabularies or vocabulary > mappings as an implementation, please provide *at least* the following > information: > > * vocabulary title(s) (e.g. Library of Congress Subject Headings) > > * name of person and/or organisation responsible for the > implementation > > * a list of the SKOS constructs used (e.g. skos:Concept, > skos:ConceptScheme, skos:inScheme, skos:broader, skos:prefLabel, > skos:closeMatch ... etc.) > > * URL(s) where the published SKOS data may be obtained, if the data > are publicly available > > We would also welcome any further information you care to provide, > however this is *not mandatory*. For example, we would be interested > to know the scope and size of the vocabulary, what it is primarily > used for, in what languages the vocabulary is provided, any other URLs > describing the vocabulary or providing further information. > > == Software Implementations == > > If you are notifying us of software as an implementation, please > provide *at least* the following information: > > * name of the software (e.g. SKOSEd) > > * name of person and/or organisation responsible for the > implementation > > * URLs for software home page and/or download location if publicly > downloadable > > * can the software read SKOS data? > > * can the software write SKOS data? > * can the software check consistency of SKOS data with respect to > the SKOS data model? > > For more information on what we mean by reading, writing or checking > SKOS data, see: > > http://www.w3.org/2006/07/SWD/wiki/SKOSImplementationReport > > We would also welcome any further information you care to provide, > however this is *not mandatory*. For example, we would be interested > in the main purpose and functionality of the software, the programming > language and/or software frameworks used, details of the SKOS > constructs which are supported, any other URLs describing the software > or providing further information. > > Kind regards, > > Alistair Miles and Antoine Isaac > > on behalf of the W3C Semantic Web Deployment Working Group > > -------------- > John Graybeal <mailto:graybeal@mbari.org> -- 831-775-1956 > Monterey Bay Aquarium Research Institute > Marine Metadata Interoperability Project: http://marinemetadata.org > > -- Sean Bechhofer School of Computer Science University of Manchester sean.bechhofer@manchester.ac.uk http://www.cs.manchester.ac.uk/people/bechhofer
Received on Thursday, 14 May 2009 14:54:28 UTC