Re: Using DBpedia resources as skos:Concepts?

François-Paul,

I was referring to the practical use-cases about stating different things
about the concept.  Many organizations state different things about the
same concept.  That's why skos:Concept exists.  Within the same
organization you might even have one department using one scheme, and
another department using a different scheme, but both sharing the same
skos:Concept but in different ways.



On Mon, Nov 12, 2012 at 9:06 AM, François-Paul Servant <
francois-paul.servant@noos.fr> wrote:

> Hi,
>
> I'm not sure to understand you because… I completely agree with what you
> say. Are you discussing my question about using different URIs for the
> skos:Concept  and for the HTML page that we get when getting the
> skos:Concept? I do understand why we must have different URIs for the
> concept and the value of foaf:focus (the "real world thing"), and how to
> combine information between different schemes thanks to that foaf:focus
> property.
>
> fps
>
> Le 12 nov. 2012 à 15:42, Thad Guidry <thadguidry@gmail.com> a écrit :
>
> Well, think of SKOS Concept as a line in a dictionary that gives
> additional description and additional knowledge about a phrase, term, or
> word..
>
> I might have a line in my dictionary (my scheme) that says "footy".
>
> Your dictionary (your scheme) might say "Australian Rules Football".
>
> They are both "describing" the same Thing, but we might apply them
> differently in our applications, but we can link and combine our
> applications knowledge by using FOAF focus or another property, where we
> happen to both point to the same URI , etc.
>
>
>
> On Mon, Nov 12, 2012 at 8:34 AM, François-Paul Servant <
> francois-paul.servant@noos.fr> wrote:
>
>> Dan, Bernard,
>>
>> thank you for your answers. I'll use foaf:focus.
>>
>> > As for distinction between the concept and the page about it, seems to
>> me the general consensus is to consider a skos:Concept as a non-information
>> resource, so it should have a URI distinct from the one of the page
>> representing it.
>>
>> well, I'm not convinced there is a big utility to it in the case of a
>> skos:Concept: I don't see practical use-cases where one would want to state
>> different things about the concept and the page (or the RDF data) returned
>> when dereferencing it. No "semantic collapse" to be afraid of ;-)
>>
>> > (I don't think or talk in those terms, personally; is 'Hamlet' an
>> > information resource? or the Bible? Or the London tube map? does it
>> > matter?)
>>
>> I wouldn't say that I usually think in those terms: I just wanted to know
>> if I have to have #URIs for skos:Concepts (or to 303-redirect) in order to
>> be a "good citizen" :-)
>>
>> Best Regards,
>>
>> fps
>>
>>
>
>
> --
> -Thad
> http://www.freebase.com/view/en/thad_guidry
>
>
>


-- 
-Thad
http://www.freebase.com/view/en/thad_guidry