Register your interest in SKOS by adding your organisation's details to the /RelevantOrgs wiki page.
A wiki area for collaborative work on SKOS schemas and APIs, supporting documentation and resources.
/DataZone | /ToolShed | /SkosCore | /SkosMapping | /SkosApi | /SkosFaq | /ThesaurusLinks | /ModelClassifications | /AuthorityFiles | /NiceIdeas | /ChangeProcess | /SchemaManagement | /SkosMeeting09072004 | SchemaChangeWithOwl | ExtendingSkosCore | /SkosOwlDl | /ClassificationPubGuide | /RelevantOrgs | /RequiredReading | /CoOrdination
Most recent drafts:
Mailing lists
Best practices for naming resources of type skos:Concept with HTTP URIs
Here's draft text for best practice statement here:
You MAY use an HTTP URI of any form to name a resource of type skos:Concept.
If you use an HTTP URI of the form /http:[^#]*$/ (a 'slash URI', e.g. http://slash.example.com/concepts/love) to name a resource of type skos:Concept, then an HTTP GET request SHOULD return a 303 see other (redirect) response code. The agent SHOULD be redirected to an information resource that describes the original resource, that by default returns a response with content type 'application/rdf+xml', that MAY support content negotiation, and that MAY support the SPARQL HTTP protocol.
If you use an HTTP URI of the form /http:[^#]+#[^#]+$/ (a 'hash URI', e.g. http://hash.example.com/concepts#love) to name a resource of type skos:Concept, then the resource denoted by the URI before the hash (the primary resource, e.g. http://hash.example.com/concepts) SHOULD be an information resource that describes all associated secondary resources, SHOULD respond to an HTTP GET request with a 200 response code, SHOULD return a response with content-type 'application/rdf+xml' by default, MUST NOT support content negotiation, and MAY support the SPARQL HTTP protocol.