atom feed27 messages in org.w3.public-esw-thesRE: revisions and change in skos
FromSent OnAttachments
Rob TiceSep 28, 2008 11:56 pm 
De Smedt JohanSep 29, 2008 12:15 am 
Sini, Margherita (KCEW)Sep 29, 2008 1:30 am 
Aida SlavicSep 29, 2008 2:13 am 
De Smedt JohanSep 29, 2008 2:26 am 
Sini, Margherita (KCEW)Sep 29, 2008 2:32 am 
Rob TiceSep 29, 2008 3:30 am 
De Smedt JohanSep 29, 2008 4:05 am 
Aida SlavicSep 29, 2008 4:06 am 
Rob TiceSep 29, 2008 4:53 am 
Sini, Margherita (KCEW)Sep 29, 2008 5:05 am 
Sini, Margherita (KCEW)Sep 29, 2008 10:48 am 
Houghton,AndrewSep 29, 2008 11:07 am 
Sini, Margherita (KCEW)Sep 29, 2008 9:13 pm 
Alan RuttenbergSep 29, 2008 9:29 pm 
Sini, Margherita (KCEW)Sep 29, 2008 11:00 pm 
Alan RuttenbergSep 29, 2008 11:26 pm 
Antoine IsaacSep 30, 2008 2:55 am 
Stephen BoundsSep 30, 2008 3:49 am 
Leonard WillSep 30, 2008 4:43 am 
Panzer,MichaelOct 1, 2008 8:19 am 
Joseph TennisOct 1, 2008 1:02 pm 
Sini, Margherita (KCEW)Oct 1, 2008 1:04 pm 
Alan RuttenbergOct 2, 2008 3:16 am 
Antoine IsaacOct 2, 2008 7:23 am 
Alistair MilesOct 2, 2008 9:29 am 
Sini, Margherita (KCEW)Oct 2, 2008 11:27 am 
Subject:RE: revisions and change in skos
From:Panzer,Michael (panz@oclc.org)
Date:Oct 1, 2008 8:19:27 am
List:org.w3.public-esw-thes

Hi Rob,

I am currently dealing with similar problems and have been experimenting with using DCMI terms:

For deprecation (vacating a concept completely) I am using dcterms:isReplacedBy:

<Concept rdf:about="a"> <historyNote rdf:parseType="Resource"> <dcterms:isReplacedBy rdf:resource="b"/> </historyNote> </Concept>

However, it is debatable if the added semantics induced by the history note property warrant the creation of a blank node in your resource description, or if dcterms:isReplacedBy should be used directly outside of the note.

In addition, some other DC terms like dcterms:created, dcterms:updated, dcterms:issued, dcterms:coverage and dc:isVersionOf come in handy for indicating version dependencies.

Cheers Michael

-----Original Message----- From: Rob Tice [mailto:rob.@k-int.com] Sent: Mon 9/29/2008 13:53 To: Sini, Margherita (KCEW) Cc: publ@w3.org Subject: RE: revisions and change in skos

Hi Margherita

Thanks for the response.

When it comes to change control one of our main use cases is so that other systems can gain all the info that they need to ensure that updates and mappings are cascaded to end users of the reference data.

I can see that your proposed solution could be a usable work around in certain cases, however our actual goal is to expose a link between concept a and b to inform systems that any previous reference to the uri of concept a should now use the uri for concept b. To that end for us the deprecation part of the work around is actually a different use case.

How do you/the list think we should present this link info?

Best Regards