Re: referencing a concept scheme as the code list of some referrer's property

On 28/08/12 20:39, Antoine Isaac wrote: Sorry, my owl:someValuesFrom should have been owl:allValuesFrom, I guess. Actually I think owl:someValuesFrom is right though the easiest construct is owl:hasValue : some:codeAConcept owl:equivalentClass [ owl:intersectionOf ( skos:Concept

Re: referencing a concept scheme as the code list of some referrer's property

Hi all I'm with Antoine and Dave on this - as previously written (I think). owl:hasValue is indeed a nice and too much overlooked OWL construct allowing to define a class based on any property-value pair, e.g., A Blue Thing is a Thing of which property color has value Blue ex:BlueThing a

Re: referencing a concept scheme as the code list of some referrer's property

You're right, Dave--thanks for the correction! And thanks to Bernard for the additional case. Though there might be a problem with owl:hasValue and it does not prevent an instance of such a class to belong to another skos:ConceptScheme. My previous owl:someValuesFrom was perhaps a bit more fit

Re: referencing a concept scheme as the code list of some referrer's property

Hi Thomas, all, I disagree with you on the fact that sub-classing skos:Concept would solve all representation needs. There is data to be asserted at the concept scheme-level, which would be inappropriately captured when being directly attached to a class of concepts. E.g., the creator of a

Re: referencing a concept scheme as the code list of some referrer's property

Sorry, my owl:someValuesFrom should have been owl:allValuesFrom, I guess. Antoine Hi Thomas, all, I disagree with you on the fact that sub-classing skos:Concept would solve all representation needs. There is data to be asserted at the concept scheme-level, which would be inappropriately

Re: referencing a concept scheme as the code list of some referrer's property

Hi Simon, Did you consider using skos:notation and the 'match' properties, such as skos:exactMatch? This might come in handy to convert a plain literals, e.g. a SNOMED CT code from a database, to a datatyped literal. In turn the latter is linked as object to a SKOS concept (blank node) with

Re: referencing a concept scheme as the code list of some referrer's property

Simon, exactly. Your example will be understood by every standard reasoner without having to know what a skos:Concept is. skos:inScheme does not add any information. If we want to refer to the domain specific notion of concept schemes, we might say: skos:inScheme rdfs:subPropertyOf

Re: referencing a concept scheme as the code list of some referrer's property

[Apologies for continuing the cross-posting] A pattern of using sub-classes of skos:Concept to denote a group of concepts (and thus be able to use rdfs:range in associated ontologies) is a good one. It is recommended best practice in data.gov.uk linked data work, for example. This does not

Re: referencing a concept scheme as the code list of some referrer's property

Am 23.08.2012 10:40, schrieb Dave Reynolds: [Apologies for continuing the cross-posting] A pattern of using sub-classes of skos:Concept to denote a group of concepts (and thus be able to use rdfs:range in associated ontologies) is a good one. It is recommended best practice in data.gov.uk

Re: referencing a concept scheme as the code list of some referrer's property

Hi Thomas I've been munching over this issue for maybe as many years as you have :) ... but somehow arrived to different conclusions. Regarding the Geonames example you quote, the Geonames feature classes and feature codes have been modeled as they are, as skos:ConceptScheme and skos:Concept

Re: referencing a concept scheme as the code list of some referrer's property

On 23/08/12 10:22, Thomas Bandholtz wrote: Am 23.08.2012 10:40, schrieb Dave Reynolds: [Apologies for continuing the cross-posting] A pattern of using sub-classes of skos:Concept to denote a group of concepts (and thus be able to use rdfs:range in associated ontologies) is a good one. It is

Re: referencing a concept scheme as the code list of some referrer's property

Dear Thomas, I'm ccing public-esw-t...@w3.org. Perhaps this was the one you were looking for! (1) (2) You probably mean, if a ConceptScheme could be defined as a class, of which the concepts of a given concept scheme are instances? That would be the way to proceed, if you want to use the

Re: referencing a concept scheme as the code list of some referrer's property

Hi Antoine and CCs and everybody, nice answer, and I'm glad you have detected my question in this haystack. I think I have to tell more about the context of this question. We have a new RD project about Linking Open Environment Data [1]. Here we try to bring together Data Cubes (prefix qb:) [2],

RE: referencing a concept scheme as the code list of some referrer's property

Thomas - I've come to the same conclusion. my:property1 rdfs:range some:codeA . my:property2 rdfs:range some:codeB . some:codeA rdfs:subClassOf skos:Concept . some:codeB rdfs:subClassOf skos:Concept . some:item1 a some:codeA . # also a skos:Concept because of subclass relationship some:item2

referencing a concept scheme as the code list of some referrer's property

This is about SKOS usage in LOD. Yesterday I sent a post to public-swd...@w3.org, but obviously it has not been distributed, although it can be found in the archive. http://lists.w3.org/Archives/Public/public-swd-wg/2012Aug/.html public-swd...@w3.org isn't very active any more, so