atom feed27 messages in org.w3.public-esw-thesRE: revisions and change in skos
FromSent OnAttachments
Rob TiceSep 28, 2008 11:57 pm 
De Smedt JohanSep 29, 2008 12:16 am 
Sini, Margherita (KCEW)Sep 29, 2008 1:30 am 
Aida SlavicSep 29, 2008 2:14 am 
De Smedt JohanSep 29, 2008 2:26 am 
Sini, Margherita (KCEW)Sep 29, 2008 2:33 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:08 am 
Sini, Margherita (KCEW)Sep 29, 2008 9:13 pm 
Alan RuttenbergSep 29, 2008 9:30 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:03 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:30 am 
Sini, Margherita (KCEW)Oct 2, 2008 11:28 am 
Subject:RE: revisions and change in skos
From:De Smedt Johan (
Date:Sep 29, 2008 12:16:03 am

Hi Rob,

In my project I am using the following approach - URI are forever - the skos:Concept may be constraind in time using an applicability period - the skos Concept has a creation date. modification date and version(=introduction version) property - semantic relations are not versioned (skos would be more difficult to accommodate that) - Next to semantic relations, change-notes are used on versioned concepts. These change notes contain references to earlier/newr versions of a concept

This is sufficient for my curent projects


kr, Johan De Smedt e-mail: ===================

-----Original Message----- From: [] On Behalf Of Rob Tice Sent: Monday, 29 September, 2008 08:57 To: Subject: revisions and change in skos

Dear list members

The background to my questions is that we are currently considering developing a 'SKOS resolver' (for want of a better description) for our terminology management solution to sit alongside the other formats we currently implement.

This has however thrown up some questions.

As part of this requirement we (ideally)need to: 1 Expose versioning information 2 Allow identification of terminology changes between versions

As these are parts of our existing solution which are already exposed using other formats.


1. How should we expose versioning information given that uri's for concepts are fixed (please don't say timestamps on uri's :))

2. How should we identify and manage change between revisions of concept schemes as this 'seems' to result in imprecision. e.g. a concept 'a' is currently in thes 'A' and only has a preferred label. A new revision of thes 'A' is published and what was concept 'a' is now a non preferred concept and thus becomes simply a non preferred label for a new concept 'b'.

It seems to me that this operation loses some of the semantic meaning of the change as all references to the concept id of 'concept a' would be lost as it now is only a non preferred

label of a different concept with a different id (concept 'b').

Any comments would be much appreciated.

Best Regards



Rob Tice, Director Knowledge Integration Ltd 35 Paradise Street Sheffield South Yorkshire S3 8PZ email: Tel: +44 (0)870 803 4661

No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.4/1695 - Release Date: 27/09/2008 13:11