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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  May 2013

BIBFRAME May 2013

Subject:

http://bibframe.org/documentation/bibframe-authority/ and the "lightweight abstraction layer"

From:

Stuart Yeates <[log in to unmask]>

Reply-To:

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

Date:

Wed, 22 May 2013 08:58:08 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (17 lines)

As I understand it, the main question posed by http://bibframe.org/documentation/bibframe-authority/ is "Do we need a "lightweight abstraction layer""?

Equivalently, as I understand it, the question is "Can we attach the authority-related attributes directly to a person / document / place or do we need some separate resource for them?"

My answer is (a) yes we do need a separate resource for them and (b) we can do that very easily.

(a) yes we do need a separate resource for them
For Instances where the carrier is digital and we have a URL the instance, we already need to make a differentiation between our rdfs:Resource for metadata about the instance and the rdfs:Resource that is the instance. Otherwise we canít differentiate, for example, between the HTML version of the FRBR report and itís HTML catalog entry. Once we've made the distinction for digital Instances, having a different genre of 'thing' for our other entities in our model is a recipe for confusion.

(b) we can do that very easily
In the foaf vocabulary there is a foaf:Person, a foaf:Document and foaf:primaryTopic which are what they say on the tin and have, I believe, exactly the semantics weíre looking for. foaf:Agent and geo:Point are obvious contenders for Organisation and Place.  We can reuse them directly or via semantic sugar (a la madsrdf:hasCloseExternalAuthority). There are other namespaces, with coverage of these areas; pretty much any of them is better than rolling our own. foaf also has the benefit of already being used by VIAF (and I believe it works for them, I've certainly not seen any complaints). 

[I was going to use some viaf.org examples, but itís down as I write this...]

cheers
stuart

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager