Re: VIAF contributor model

Jeff,


>
> Thanks for the feedback. It is altering my thinking about "the aggregate
> model". Now I'm "pretty convinced" that
> http://viaf.org/ontology/1.1/#Heading should go away in favor of
> straight use of skosxl:Label. What was I thinking?
>
> The real issue I'm trying to work around is the
> http://www.w3.org/TR/skos-reference/#S14 integrity constraint on
> skos/xl:prefLabel, In "the contributor model" this constraint shouldn't
> be a problem. In the aggregate model, though, contributed prefLabels
> collide and VIAF isn't (currently?) prepared to pick a winner for each
> language tag. It would be a shame to dumb them all down to
> skosxl:altLabel. In VIAF 1.1, we coined
> http://viaf.org/ontology/1.1/#hasEstablishedForm and
> http://viaf.org/ontology/1.1/#hasXrefAlternate to sidestep the S14
> constraint. How would people feel about us upgrading these properties
> like so:
>
> viaf:hasEstablishedForm a owl:ObjectProperty ;
> 	rdfs:subClassOf skosxl:altLabel ;
> 	rdfs:domain skos:Concept ;
> 	rdfs:range skosxl:Label .
>
> viaf:hasXrefAlternate a owl:ObjectProperty ;
> 	rdfs:subClassOf skosxl:altLabel ;
> 	rdfs:domain skos:Concept ;
> 	rdfs:range skosxl:Label .
>
> Contributed skos:Concepts could then be associated with a common set of
> skosxl:Labels using skosxl:prefLabel/altLabel. If and when VIAF picks
> language tag winners, these properties could be deprecated.


[Ignoring all the aspects related to my other mail for one second,] this latter modeling recipe seems very good to me!

Cheers,

Antoine


>
> Jeff
>
>
>> -----Original Message-----
>> From: Antoine Isaac [mailto:aisaac@few.vu.nl]
>> Sent: Friday, October 29, 2010 11:47 AM
>> To: Young,Jeff (OR)
>> Cc: public-lld
>> Subject: Re: VIAF contributor model
>>
>> Hi Jeff,
>>
>> On that specific one:
>>
>>
>>> I'm also pretty convinced that the
>> http://viaf.org/ontology/1.1/#Heading class needs to be bound to
>> skosxl:Label class in some way (rdfs:subClassOf?). I don't think it
> can
>> completely go away, though, because of inconvenient restrictions on
> the
>> skosxsl:prefLabel and skosxl:altLabel.
>>
>>
>> I guess it would be possible to have viaf:Heading rdfs:subClassOf
>> skosxl:Label, yes.
>> The issue then is the practical value of such a thing to which (SKOS)
>> entity should these label be attached? skosxl:Label are nice per se,
>> but linking them to something using
>> skosxl:prefLabel/altLabel/hiddenLabel makes them much more
> interesting.
>> http://viaf.org/viaf/102333412 is not a skos:Concept, and I guess it
>> shouldn't be--your decision to have
>> http://viaf.org/viaf/102333412/#skos:Concept linked to it makes this
>> even clearer. So you would attach these xl:Labels to
>> http://viaf.org/viaf/102333412/#skos:Concept ? I guess that can be
>> fine, I don't see any restrictions in SKOS-XL [1] that would prevent
>> it, in fact.
>>
>> Cheers,
>>
>> Antoine
>>
>> [1] http://www.w3.org/TR/skos-reference/skos-xl.html
>
>
>

Received on Monday, 1 November 2010 16:23:10 UTC