W3C home > Mailing lists > Public > public-esw-thes@w3.org > October 2005

RE: [PORT] new editor's working draft of SKOS Core Vocab Spec

From: Houghton,Andrew <houghtoa@oclc.org>
Date: Sun, 9 Oct 2005 20:58:07 -0400
Message-ID: <D53793AA582576458786FBE27899DB18013A544D@OAEXCH2SERVER.oa.oclc.org>
To: "Bernard Vatant" <bernard.vatant@mondeca.com>, "Mikael Nilsson" <mini@nada.kth.se>
Cc: <public-esw-thes@w3.org>

> -----Original Message-----
> From: public-esw-thes-request@w3.org 
> [mailto:public-esw-thes-request@w3.org] On Behalf Of Bernard Vatant
> Sent: 09 October, 2005 16:44
> To: Mikael Nilsson
> Cc: public-esw-thes@w3.org
> Subject: RE: [PORT] new editor's working draft of SKOS Core Vocab Spec
> 
> Michael
> > Just as each XML language would specify what kinds of 
> extensions are 
> > allowed, each SKOS concept scheme will specify what policy 
> rules it follows.
> 
> That's an interesting idea, but can you provide any clue on 
> how you would envision such a specification?
> Unformal documentation? Formal attributes on the 
> skos:ConceptScheme element? Both?
> Anything else?
> 

You could simply issue a policy statement about a concept scheme in SKOS by specifying dcterms:conformsTo with a value of BS8723 or Z39.19 or use an appropriate URI like:

<http://www.niso.org/standards/#Z39.19>


Andy.
Received on Monday, 10 October 2005 00:58:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:54 GMT