From Alistair Miles and Antoine Isaac on behalf of the W3C Semantic Web Deployment Working Group ...
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.
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.