JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-RDA Archives


DC-RDA Archives

DC-RDA Archives


DC-RDA@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-RDA Home

DC-RDA Home

DC-RDA  June 2010

DC-RDA June 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Administrative metadata

From:

Ross Singer <[log in to unmask]>

Reply-To:

List for discussion on Resource Description and Access (RDA)

Date:

Tue, 15 Jun 2010 10:23:00 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (100 lines)

I think that obscuring the person in a blank node in a resource that
abstracts its way around the person is Herbert Van de Sompel's "one
bridge too far".  http://twitter.com/hvdsomp/status/15777598515

People want to talk about people, not abstractions of people.

-Ross.

On Tue, Jun 15, 2010 at 10:10 AM, Karen Coyle <[log in to unmask]> wrote:
> In my (librarian-ish) mind, the confusion goes away if we state that we have
> resource that is ABOUT a person/book/subject. We then describe the resource
> and its topic, something like:
>
>    <rdf:Description rdf:about="http://openlibrary.org/authors/OL20A">
>        <foaf:topic>
>        <foaf:person>
>            <foaf:name>Michael Madhusudan Dutt</foaf:name>
>            <foaf:page>
>             <foaf:Document
> about="http://www.poetseers.org/the_great_poets/in/dutt/">
>                  <rdfs:label>Dutt at Poet Seers</rdfs:label>
>              </foaf:Document>
>        </foaf:page>
>
>
> In this case, adding dcterms:modified at the rdf:Description level isn't a
> problem.
>
> It seems to me that the problem comes about when trying to assert that the
> URI represents the person that is the topic of the page, rather than
> accepting (maybe that's the wrong word) that what is on the web is a
> representation, one step away from the real world, and that we are
> manipulating representations that MAY stand for real world things. There
> will be many such representations for any truly real thing, and we'll be
> spending the rest of our time determining which ones assert information
> about the same thing. :-)
>
> kc
>
> Quoting Jonathan Rochkind <[log in to unmask]>:
>
>> Um, but now you're ignoring the original question, which was about
>> keeping assertions about the _administrative metadata record_ seperate
>> from assertions about the _actual thing_.   ('actual thing' being a
>> book, or an author in this case).
>>
>> Which is the URI  http://openlibrary.org/authors/OL2632437A for then,
>> under the below plan?
>>
>> At first Ed suggested that
>> http://openlibrary.org/authors/OL2632437A.rdf woudl be for the metadata
>> and http://openlibrary.org/authors/OL2632437A  would be for the book.
>> Then I brought up that ".rdf" is just one representation of the
>> metadata record, is that an identifier for just the RDF representation,
>> or is it an identifier for the "metadata record"?
>>
>> And now we've come around to saying, oh, well, yeah, then just use
>> http://openlibrary.org/authors/OL2632437A .   But then we're back to
>> the confusion over whether assertions involving that URI are for the
>> actual book (or the actual author/person in this case), or for the
>> metadata record about him/her/it.
>>
>> My conclusion:  There is no obvious answer here, probably no matter
>> what OL/Karen chooses to do, it's going to confuse some people.
>>
>> Jonathan
>>
>>> On Tue, Jun 15, 2010 at 4:24 AM, Felix Ostrowski  <[log in to unmask]>
>>> wrote:
>>>
>>>> http://openlibrary.org/authors/OL2632437A/about could be used as
>>>> the generic metadata URI serving the representation that is requested
>>>> via content negotiation. Assertions about the metadata can then be made
>>>> using that URI:
>>>>
>>>> @prefix dc:   <http://purl.org/dc/terms/> .
>>>> @prefix foaf: <http://xmlns.com/foaf/0.1/> .
>>>> <http://openlibrary.org/authors/OL2632437A/about>
>>>>  dc:modified "2010-06-15" ;
>>>>  foaf:primaryTopic <http://openlibrary.org/authors/OL2632437A> .
>>>>
>>>
>>> This is an excellent suggestion. And I don't think it necessary
>>> precludes also making a json document available at a non-content
>>> negotiated URL. Having URLs for the specific format is often handy so
>>> that people can look at them in their browser without having to
>>> twiddle with Accept headers.
>>>
>>> //Ed
>>>
>
>
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
>

Top of Message | Previous Page | Permalink

JISCMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
August 2012
July 2012
May 2012
April 2012
March 2012
February 2012
January 2012
October 2011
September 2011
August 2011
June 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
June 2010
February 2010
January 2010
December 2009
November 2009
October 2009
June 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
August 2007
July 2007
June 2007
May 2007
April 2006
February 2006
January 2006
December 2005


WWW.JISCMAIL.AC.UK

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager