Re: Failing to meet integrity constraint S14 when terminology evolves

Hi Christian and Osma,

Thanks for your advice, as well as sharing your nice work of SKOSify and 
qSKOS! We are now in favor of using a single URI for different versions. 
As we are not the official body of ICD10GM, we can keep our terminology 
server closed so as to avoid inconsistency with old published versions.
 
Hi Vladimir, thanks for your remark of avoiding the dot in prefixed names!

best regards,
Hong




From:   Christian Mader <maderc@semantic-web.at>
To:     public-esw-thes@w3.org
Date:   11/14/2013 01:54 AM
Subject:        Re: Failing to meet integrity constraint S14 when 
terminology  evolves



Hi Hong,

You're right, I see the problem now. Using (a subproperty) of 
skosxl:altLabel may be an option but I think this is also not completely 
satisfactory for you. I also agree with Osma's suggestion not to worry 
about S14 violations between different versions of your vocabulary.

Btw, thanks for referencing our journal paper; the patterns you propose 
are a very interesting contribution! Some of them dealing with circular 
relations are already found by my qSKOS [1,2] tool, some are beyond it's 
capabilities.

best,
Christian

[1] https://github.com/cmader/qSKOS/ 
[2] 
http://www.poolparty.biz/qskos-is-setting-a-new-standard-in-skos-thesaurus-quality-management/


Am Mittwoch, den 13.11.2013, 10:52 +0100 schrieb Hong Sun 
<hong.sun@agfa.com>:
> Thanks Christian! 
> 
> I tried to use skosxl:prefLabel and assign multiple skosxl:literalForm
> in case multiple labels exist. 
> Unfortunately, I found there is a restriction preventing me to do so: 
> 'restriction on skosxl:literalForm cardinality exactly 1' 
> I then find the problem I experienced in SKOS also exist with SKOS-XL,
> or do you have better ideas in formalizing the case with SKOS-XL? 
> 
> best regards, 
> Hong 
> 
> From: Christian Mader 
> To: Hong Sun/AXIFX/AGFA@AGFA 
> Cc: 
> Date: 11/13/2013 10:05 AM 
> Subject: Re: Failing to meet integrity constraint S14 when terminology
> evolves 
> 
> -------------------------
> 
>  Hi Hong,
> 
>  Maybe you could take a look at the SKOS-XL schema [1] which allows
> you 
>  to express your labels not only as text literals but as owl classes.
> You 
>  can then add history/versioning information to these label resources.
> 
>  [1] http://www.w3.org/TR/skos-reference/skos-xl.html [1]
> 
>  best,
>  Christian
> 
>  Am Dienstag, den 12.11.2013, 18:13 +0100 schrieb Hong Sun 
>  :
>  > Dear All,
>  >
>  > I have a problem in assigning labels to SKOS concepts within an
>  > evolving terminology, and am therefore looking for your opinions.
>  >
>  > In the ICD 10 coding system, Germany version, the text assigned to
> a
>  > code changes between different versions, e.g.
>  > in ICD10GM 2004, the code K12.23 has a label:Wangenabszeß
>  > in ICD10GM 2013, the code K12.23 has a label:Wangenabszess
>  >
>  > Before realizing the problem, I formalized the code as SKOS
> concept:
>  > icd10gm:K12.23 a skos:concept;
>  > skos:prefLabel "Wangenabszeß"@de.
>  > However, it ends up with
>  > icd10gm:K12.23 a skos:concept;
>  > skos:prefLabel "Wangenabszeß"@de;
>  > skos:prefLabel "Wangenabszess"@de.
>  > which is not consistent with the integrity constraint S14.
>  >
>  > As the ICD 10 GM publish a new version each year, and most of the
>  > labels are stable, it also seems to be overkill to create a concept
>  > for each version, e.g.
>  > icd10gm2004:K12.23 a skos:concept;
>  > skos:prefLabel "Wangenabszeß"@de.
>  > and
>  > icd10gm2013:K12.23 a skos:concept;
>  > skos:prefLabel "Wangenabszess"@de.
>  >
>  > I also consider to take the labels from the latest version as
>  > prefLabel, and those from an older version as altLabel, e.g.
>  > icd10gm:K12.23 a skos:concept;
>  > skos:prefLabel "Wangenabszess"@de;
>  > skos:altLabel "Wangenabszeß"@de.
>  >
>  > The problem for this approach is that in case the code changes in
>  > later versions(e.g. v2014), then the skos:prefLabel needs to be
>  > updated again. If the formalized terminology is already published,
>  > then such request to update will be a problem.
>  >
>  > I currently planed to formalize the concept as below:
>  > icd10gm:K12.23 a skos:concept;
>  > rdfs:label "Wangenabszess"@de;
>  > rdfs:label "Wangenabszeß"@de.
>  >
>  > Still not very satisfied with this solution yet. Is there any
> better
>  > solution with other SKOS properties? Meanwhile, is there a general
>  > principle/guideline for SKOS in formalizing (the labels) of an
>  > evolving terminology? Thanks!
>  >
>  > Kind Regards,
>  >
>  > Hong Sun | AGFA HEALTHCARE
>  > Researcher | HE/Advanced Clinical Applications Research
>  > T +32 3444 8108
> 
> 
> 
> Links:
> ------
> [1] http://www.w3.org/TR/skos-reference/skos-xl.html