RE: revisions and change in skos

Hi Johan 

Thanks for the info. 

So in your system do you actually expose historical versions of concepts and
concept schemes via a machine interface, or do you access the 'history' only
through notes in the latest version of a concept.

We also include relationship information in our version control. Is anyone
else using SKOS to expose this type of change information.


Best Regards

Rob



> -----Original Message-----
> From: De Smedt Johan [mailto:Johan.DeSmedt@wkb.be]
> Sent: 29 September 2008 08:16
> To: Rob Tice; public-esw-thes@w3.org
> Subject: RE: revisions and change in skos
> 
> 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
> 
> best.
> 
> kr, Johan De Smedt
> e-mail: johan.de-smedt@tenforce.com
> ===================
> -----Original Message-----
> From: public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org] On Behalf Of Rob Tice
> Sent: Monday, 29 September, 2008 08:57
> To: public-esw-thes@w3.org
> 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.
> 
> So...
> 
> 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
> 
> 
> ------------------------------------------------------------------
> 
> 
> Rob Tice, Director
> Knowledge Integration Ltd
> 35 Paradise Street
> Sheffield
> South Yorkshire
> S3 8PZ
> email: rob.tice@k-int.com
> Tel: +44 (0)870 803 4661
> http://www.k-int.com
> 
> 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
> 
> 
> 
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.7.4/1695 - Release Date:
> 27/09/2008 13:11
> 

No virus found in this outgoing message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.7.5/1696 - Release Date: 28/09/2008
13:30

Received on Monday, 29 September 2008 10:31:28 UTC