W3C home > Mailing lists > Public > public-swd-wg@w3.org > May 2009

Re: SKOS Implementation : LCSH

From: Michael Hausenblas <michael.hausenblas@deri.org>
Date: Fri, 01 May 2009 07:49:27 +0100
To: Ed Summers <ehs@pobox.com>
CC: SWD WG <public-swd-wg@w3.org>, Dan Brickley <danbri@danbri.org>
Message-ID: <C6205A07.42CB%michael.hausenblas@deri.org>

Ed,

This is a non-issue. Once there was one, but this has been resolved [1].

Either one is talking about HTML elements (which is likely a rare case) such
as the case with RDForms [2], in which it is perfectly ok and encouraged to
use @id values in @about, or one talks about things that are not part of the
HTML document (people, books or whatever) which yields simple patterns
avoiding conflicts. Take the following excerpt from the SCOVO specification
[3], for example, being a simple RDF schema defined in RDFa:

<div id="c-Item" about="http://purl.org/NET/scovo#Item" typeof="rdfs:Class">
 <h3 property="rdfs:label">Item</h3>
 ...
</div>

<div id="p-dimension" about="http://purl.org/NET/scovo#dimension"
typeof="rdf:Property">
    <h3>dimension</h3>
    An <a rel="rdfs:domain" href="#c-Item"
resource="http://purl.org/NET/scovo#Item">Item</a> <span
property="rdfs:label">has a dimension</span> <a rel="rdfs:range"
href="#c-Dimension"
resource="http://purl.org/NET/scovo#Dimension">Dimension</a>.
</div>

No magic involved. Just a careful selection of @href, @id and @resource. To
say it with a good old friend of mine: YES WE CAN! ;)

Please, let us not threaten people using RDFa if there is no reason for it.

Cheers,
      Michael

[1] http://esw.w3.org/topic/RDFa_vs_RDFXML
[2] http://esw.w3.org/topic/PushBackDataToLegacySourcesRDForms
[3] http://purl.org/NET/scovo

-- 
Dr. Michael Hausenblas
DERI - Digital Enterprise Research Institute
National University of Ireland, Lower Dangan,
Galway, Ireland, Europe
Tel. +353 91 495730
http://sw-app.org/about.html
http://webofdata.wordpress.com/


> From: Ed Summers <ehs@pobox.com>
> Date: Thu, 30 Apr 2009 23:54:01 -0400
> To: Dan Brickley <danbri@danbri.org>
> Cc: SWD WG <public-swd-wg@w3.org>
> Subject: Re: SKOS Implementation : LCSH
> Resent-From: <public-swd-wg@w3.org>
> Resent-Date: Fri, 01 May 2009 03:54:42 +0000
> 
> Yes, I argued for removing the RDFa to avoid having to answer this
> question ... and also the problem of keeping the html in sync with the
> rdf/xml, n-triples and turtle views.
> 
> //Ed
> 
> On Thu, Apr 30, 2009 at 11:29 PM, Dan Brickley <danbri@danbri.org> wrote:
>> On 30/4/09 23:18, Ed Summers wrote:
>>> 
>>> (hopefully it's not too late to sneak this in ... the service just
>>> went live today)
>> 
>> Really great to see this back online!
>> 
>> A question about URIs, RDFa, conneg, http-range-14 etc:
>> 
>> (sorry!)
>> 
>> """          <div id="conceptDetailTab"
>> about="http://id.loc.gov/authorities/sh98002696#concept"
>> typeof="skos:Concept">
>>                <h1 property="skos:prefLabel" xml:lang="en">Bristol Bridge
>> Massacre, Bristol, England, 1793</h1>
>> 
>>                <span rel="skos:inScheme"
>> resource="http://id.loc.gov/authorities#conceptScheme"/>
>>                <div id="concept">
>>                    <br/>
>> 
>>                    <b>URI:</b>
>> 
>> &lt;http://id.loc.gov/authorities/sh98002696#concept&gt;
>>                    <br /><br />
>> """
>> 
>> If http://id.loc.gov/authorities/sh98002696#concept is the URI of the skos
>> Concept, aren't we supposed to avoid using it in the HTML markup when an
>> XHTML/RDFa representation is made available? ie I remember from a previous
>> thread that (against many intuitions) id="concept" should be avoided.
>> Otherwise we get into that boring thread about whether it is a URI for a
>> piece of HTML or for the thing the HTML describes / represents...
>> 
>> Sorry to nitpic, but I guess this is why W3C does implementation surveys...
>> 
>> Dan
>> 
>> 
>> 
>> 
>>> * Vocabulary Title
>>> 
>>>   Library of Congress Subject Headings
>>> 
>>> * Name of Organization Responsible for Implementation
>>> 
>>>   The Library of Congress, USA
>>> 
>>> * SKOS Constructs used
>>> 
>>>   skos:Concept
>>>   skos:ConceptScheme
>>>   skos:prefLabel
>>>   skos:altLabel
>>>   skos:example
>>>   skos:editorialNote
>>>   skos:scopeNote
>>>   skos:changeNote
>>>   skos:historyNote
>>>   skos:definition
>>>   skos:broader
>>>   skos:narrower
>>>   skos:related
>>>   skos:closeMatch
>>>   skos:inScheme
>>> 
>>> * URLs
>>> 
>>>   http://id.loc.gov/authorities
>>>   http://id.loc.gov/authorities/download/xml
>>>   http://id.loc.gov/authorities/download/ntriples
>>> 
>>> * Other Details:
>>> 
>>>    LCSH has been actively maintained since 1898 to catalog materials
>>>    held at the Library of Congress. By virtue of cooperative cataloging
>>>    other libraries around the United States also use LCSH to provide
>>>    subject access to their collections. In addition LCSH is used
>>>    internationally, often in translation.
>>> 
>>>    2,600,937 triples
>>>    309,408 concepts
>>>    72,376 skos:closeMatch links to RAMEAU SKOS Vocabulary
>>>    13 concept schemes
>>> 
>>> * Contacts
>>>    Clay Redding<cred@loc.gov>
>>>    Ed Summers<edsu@loc.gov>
>>> 
>>> 
>> 
>> 
> 
Received on Friday, 1 May 2009 06:50:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:56 UTC