|Rob Tice||Sep 28, 2008 11:56 pm|
|De Smedt Johan||Sep 29, 2008 12:15 am|
|Sini, Margherita (KCEW)||Sep 29, 2008 1:30 am|
|Aida Slavic||Sep 29, 2008 2:13 am|
|De Smedt Johan||Sep 29, 2008 2:26 am|
|Sini, Margherita (KCEW)||Sep 29, 2008 2:32 am|
|Rob Tice||Sep 29, 2008 3:30 am|
|De Smedt Johan||Sep 29, 2008 4:05 am|
|Aida Slavic||Sep 29, 2008 4:06 am|
|Rob Tice||Sep 29, 2008 4:53 am|
|Sini, Margherita (KCEW)||Sep 29, 2008 5:05 am|
|Sini, Margherita (KCEW)||Sep 29, 2008 10:48 am|
|Houghton,Andrew||Sep 29, 2008 11:07 am|
|Sini, Margherita (KCEW)||Sep 29, 2008 9:13 pm|
|Alan Ruttenberg||Sep 29, 2008 9:29 pm|
|Sini, Margherita (KCEW)||Sep 29, 2008 11:00 pm|
|Alan Ruttenberg||Sep 29, 2008 11:26 pm|
|Antoine Isaac||Sep 30, 2008 2:55 am|
|Stephen Bounds||Sep 30, 2008 3:49 am|
|Leonard Will||Sep 30, 2008 4:43 am|
|Panzer,Michael||Oct 1, 2008 8:19 am|
|Joseph Tennis||Oct 1, 2008 1:02 pm|
|Sini, Margherita (KCEW)||Oct 1, 2008 1:04 pm|
|Alan Ruttenberg||Oct 2, 2008 3:16 am|
|Antoine Isaac||Oct 2, 2008 7:23 am|
|Alistair Miles||Oct 2, 2008 9:29 am|
|Sini, Margherita (KCEW)||Oct 2, 2008 11:27 am|
|Subject:||RE: revisions and change in skos|
|From:||De Smedt Johan (Joha...@wkb.be)|
|Date:||Sep 29, 2008 4:05:25 am|
The time constraint on the concept is used in the appication and in a user interface. The user can set any date he wants Navigation in time can be through link traversal (via change-notes or other user interface artifacts).
It would be possible to exchange it between machines but there is no standard for that (as far as I know). Hence it "is" not possible yet in a meaningfull way in the "open" world
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.
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: joha...@tenforce.com ===================
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.
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