Dear Richard,
> The entry for a subject heading such as "School sports -- Fiction" [3]
> contains a <madsrdf:componentList>, within which "School sports" is
> analysed as a <madsrdf:Topic> (and given its own URL [4]) and "Fiction"
> is a <madsrdf:GenreFormElement> (surprisingly, perhaps, without its own
> URL).
-- That's a bug. I'll get that fixed.
> If this analysis of pre-coordinated headings is happening internally
> anyway, perhaps it would be possible for LOC to provide a web service
> which returns the URL - if any - for each component of a compound
> heading. That would make it possible to "URLify" the sorts of headings
> you are working with.
-- I've actually considered such a service (or variation thereof). I'll take this as a vote in favor of such a thing.
Cordially,
Kevin
> -----Original Message-----
> From: Ford, Kevin
> Sent: Wednesday, November 09, 2011 5:57 PM
> To: Ford, Kevin
> Subject: RE: [ID.LOC.GOV] Linking LCSH
>
>
>
> From: Authorities and Vocabularies Service Discussion List
> [mailto:[log in to unmask]] On Behalf Of Richard Light
> Sent: Wednesday, November 09, 2011 5:10 AM
> To: [log in to unmask]
> Subject: Re: [ID.LOC.GOV] Linking LCSH
>
>
>
> On 09/11/2011 09:39, Owen Stephens wrote:
> Here is an example of FAST in the CUL data - note the URIs in use, but
> also that they don't currently resolve
>
> http://data.lib.cam.ac.uk/id/entry/cambrdgedb_100022
>
> When I went to that entry, I could dereference the CUL URL for the FAST
> concept Science Methodology [1] - it was the OCLC URL [2] which it was
> owl:sameAs-linked to which didn't resolve. Is that what you found?
>
> Anyway, another line of thought occurs from looking at the RDF which
> LOC now provide for LCSH itself.
>
> The entry for a subject heading such as "School sports -- Fiction" [3]
> contains a <madsrdf:componentList>, within which "School sports" is
> analysed as a <madsrdf:Topic> (and given its own URL [4]) and "Fiction"
> is a <madsrdf:GenreFormElement> (surprisingly, perhaps, without its own
> URL).
>
> If this analysis of pre-coordinated headings is happening internally
> anyway, perhaps it would be possible for LOC to provide a web service
> which returns the URL - if any - for each component of a compound
> heading. That would make it possible to "URLify" the sorts of headings
> you are working with.
>
> Richard
>
> [1]
> http://data.lib.cam.ac.uk/id/entry/cambrdgedb_9904015b642acb376337cbe4d
> 4e8c4a4
> [2] http://id.worldcat.org/fast/fst01108313
> [3] http://id.loc.gov/authorities/subjects/sh2010112128
> [4] http://id.loc.gov/authorities/subjects/sh85118414
>
>
> Owen
>
> Owen Stephens
> Owen Stephens Consulting
> Web: http://www.ostephens.com
> Email: [log in to unmask]
> Telephone: 0121 288 6936
>
> On 9 Nov 2011, at 08:32, Richard Light wrote:
>
>
>
>
> On 08/11/2011 22:35, Karen Coyle wrote:
> Quoting Owen Stephens <[log in to unmask]>:
>
> Owen, thanks. It's interesting that your solution of separating the
> pre-coordinated "facets" is what worked best...
> Isn't this in effect the FAST [1] approach? Any news on FAST as Linked
> Data?
>
> Richard
>
> [1] http://www.oclc.org/research/activities/fast/default.htm
> --
> Richard Light
>
>
> --
> Richard Light
|