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:

Re: naive comments on BIBFRAME and annotations

From:

Shlomo Sanders <[log in to unmask]>

Reply-To:

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

Date:

Sun, 12 May 2013 06:39:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (36 lines)

+1

Thanks,
Shlomo

Sent from my iPad

On May 10, 2013, at 21:48, "Karen Coyle" <[log in to unmask]> wrote:

> Simeon,
> 
> Your 2c is well worth it :-). I wish to mention, however, that library bibliographic data does not treat scholarly articles in any depth because libraries, with few exceptions, do not catalog them. Article metadata (journal and newspaper) is produced by the abstracting and indexing services, which libraries then subscribe to. [1] This doesn't mean that BIBFRAME could not or will not be extended to include metadata elements that are important for scholarly articles, but that will not be an early focus, IMO, of the effort.
> 
> kc
> 
> [1] http://en.wikipedia.org/wiki/Indexing_and_abstracting_service
> 
> On 5/10/13 4:23 AM, Simeon Warner wrote:
>> I was recently looking around for ontologies that might be used to express/exchange information about scholarly articles and the different versions produced by publishers and held in repositories (like arXiv.org that I'm involved with). BIBFRAME was appealing because I think that "FRBR-lite" Work/Instance model of BIBFRAME is a practical and useful level of granularity. I'm also interested in RDF expressions of library data as we are creating a new discovery system in our library where all our MARC records are being mapped into RDF in order to merge them with additional information held in systems other than our LMS.
>> 
>> I've been following with interest the discussion of annotation in BIBFRAME and am left wondering what special value is added by BIBFRAME adopting a model not-quite-compatible with OAC. From [1] it seems that the BIBFRAME "special sauce" regarding annotations is twofold: first is a specialized set of types of annotation tied to community needs, and second is a simple syntax/structure for the use of literals. I don't see that either of these is a compelling reason for a different approach. The specialized set of annotation types very nicely maps onto the (more readily extensible) oa:motivatedBy model where instances of oa:Motivation could be usefully subclassed. The use of literal bodies can be handled with the (admittedly slightly more cumbersome) oa:ContentAsText mechanism. A possible good side-effect is that this might discourage the use of "not on the web" literal annotations except in cases such as those Karen Coyle mentioned where user tags perhaps "deserve to be literal strings, dangling off the edge of information space".
>> 
>> My conclusion is that the value-add of BIBFRAME is not in its annotation model and I think it would be better to promote a profiled use of OAC to support interchange within the target community (while also supporting uses by others not yet imagined, presumably one of the goals of going the RDF route).
>> 
>> 2c,
>> Simeon
>> 
>> [1] http://bibframe.org/documentation/annotations/20130430.html
> 
> -- 
> 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

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