LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  January 2015

BIBFRAME January 2015

Subject:

Re: What is a BIBFRAME Resource?

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Thu, 29 Jan 2015 09:56:34 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

There exists a bf:Instance identified by URI "http://bibframe.org/resources/BKw1416525962/779299instance18".

I'm not sure that the notion of aboutness is all that helpful, here. It's another case of RDF/XML leading us astray with the hypnotic allure of ghostly semantics that don't really obtain.

---
A. Soroka
The University of Virginia Library

On Jan 29, 2015, at 9:44 AM, "Denenberg, Ray" <[log in to unmask]> wrote:

> But Jeff:
>
> <bf:Instance rdf:about="http://bibframe.org/resources/BKw1416525962/779299instance18">
>
> I have always understood to say:
>
> bf:Instance “is about” http://bibframe.org/resources/BKw1416525962/779299instance18
>
> How do you interpret that statement?
>
> Ray
>
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Jeff Young
> Sent: Wednesday, January 28, 2015 6:30 PM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] What is a BIBFRAME Resource?
>
> Ray,
>
> You said this:
>
> But that line is also saying that this bf:Instance is an RDF description
>
> Rib and I are saying that the bf:Instance is NOT the RDF description. That's why Linked Data depends on two identifiers. The problem isn't what we call the description. The problem is what we mean by the phrase "is a".
>
> Jeff
>
> On Jan 28, 2015, at 5:45 PM, Denenberg, Ray <[log in to unmask]> wrote:
>
> Jeff - I use RDF description in the “plain english” sense, to mean, well “an RDF description”, not rdf:Description. I think we use it (here) frequently and I don’t think it has ever been used (here, or in BIBFRAME) to mean rdf:Description. Is there another expression, that means “an RDF description” that you prefer? (We can always go back to calling it an “RDF record”.)
>
> Ray
>
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Young,Jeff (OR)
> Sent: Wednesday, January 28, 2015 5:24 PM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] What is a BIBFRAME Resource?
>
> Ray,
>
> I think this is very well stated up to this point:
>
> “But that line is also saying that this bf:Instance is an RDF description.”
>
> Note that “RDF description” (as in <rdf:Description>) is not an ontological class. It is a bizarre artifact of RDF/XML to accommodate the potential lack of an explicit type assignment. Note, for example, that rdf:Description isn’t manifested in other RDF serializations like a real class would be. It drops out.
>
> It’s not surprising that people assume it is an ontological class, though, because Striped RDF/XML has some syntactic sugar that allows you to swap it out for one of the rdf:types, if you want to.
>
> http://www.w3.org/2001/10/stripes/
>
> RDF/XML is evil. J
>
> Jeff
>
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Denenberg, Ray
> Sent: Wednesday, January 28, 2015 4:55 PM
> To: [log in to unmask]
> Subject: [BIBFRAME] What is a BIBFRAME Resource?
>
> I seemed to have caused some confusion (my apologies) by my post week-before-last; I was away (on vacation) all last week, so I have just gotten back to this. I want to try to explain my view of what a BIBFRAME resource is, in simple terms, without using terminology that I don’t think we have agreed-upon definition for, such as “real-world-object”, “thingy”, and “r-ball”. (I have no idea what an r-ball is, only a vague idea what a thingy is, and I know what my definition of an RWO is but am not sure we all agree.) If I use any term that anyone thinks does not have a commonly agreed-upon definition, please call me out.
>
> So let me try to work through this.
>
> At:
> http://bibframe.org/resources/BKw1416525962/779299instance18.rdf
>
>
> The first line is:
>
> <bf:Instance rdf:about="http://bibframe.org/resources/BKw1416525962/779299instance18">
>
> These are two distinct URIs:
>
> 1. http://bibframe.org/resources/BKw1416525962/779299instance18.rdf an RDF description,
> 2. http://bibframe.org/resources/BKw1416525962/779299instance18 the thing it describes.
>
> Rob says (I’m paraphrasing) “you can’t have one single URI identifying both the thing and it’s description” . But we don’t. These are two distinct URIs. The trick is, if you click on the “thing” you get the description, i.e. you get RDF, and that’s because that’s what web architecture and linked data principles say is supposed to happen: if a URI identifies a resource which is an abstract concept, if you dereference that URI there should be an HTTP 303 re-direct to an RDF description of that resource.
>
>
> And the line that says:
>
> <bf:Instance rdf:about="http://bibframe.org/resources/BKw1416525962/779299instance18">
>
> Is saying that this RDF description is ABOUT http://bibframe.org/resources/BKw1416525962/779299instance18 which is an abstract thing (an Instance). And the properties expressed within the RDF description are properties of that abstract thing.
>
> But that line is also saying that this bf:Instance is an RDF description.
>
> So a bf:Instance is an RDF description. That’s the part that seemed to cause anguish. So how do we get around that? I propose we say “a bf:Instance is a description, and a BIBFRAME Instance is an abstract concept”.
>
> Does this help?
>
> Ray
>
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
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
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager