Re: [Proposal][SKOS-Core] Local (non-URI) identifiers for concepts

dc:identifier has recently occurred to me here also.

What if we go ahead with the deprecation of skos:externalID, and replace with 
dc:identifier?  (And drop the proposal for a new property skos:localID).

The problem of how to cope with concepts that may have more than one identifier 
(possibly deriving from different schemes) still remains, however.

What if we recommend here that a sub-property of dc:identifier is created by the 
scheme owners for each identifier?  So e.g.

<skos:Concept rdf:about="http://example.org/topics/098">
	<ex:conceptNumber>098</ex:conceptNumber>
	<ex2:id>A.34.12</ex2:id>
</skos:Concept>

Where ex:conceptNumber and ex2:id are both hypothetical properties created by 
scheme owners, and both are declared to be subPropertyOf dc:identifier by scheme 
owners.  (Scheme owners can also declare these props as inversefunctional if 
they choose).

Comments?

Al.



Charles McCathieNevile wrote:
> What's wrong with dc:identifier here?
> 
> On Thu, 5 Aug 2004, Miles, AJ (Alistair)  wrote:
> 
> 
>>These proposals are in response to the requirements outlined in [1].
>>
>>(see also the wiki page <http://esw.w3.org/topic/SkosDev/SkosCore/LocalId>)
>>
> 
> 
> Chaals
> 
> 

-- 
Alistair Miles
Research Associate
CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Chilton
Didcot
Oxfordshire OX11 0QX
United Kingdom
Email: a.j.miles@rl.ac.uk
Tel: +44 (0)1235 445440