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  June 2013

BIBFRAME June 2013

Subject:

Re: Annotations: External and inline

From:

Thomas Dukleth <[log in to unmask]>

Reply-To:

Thomas Dukleth <[log in to unmask]>

Date:

Tue, 25 Jun 2013 13:26:39 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (59 lines)

How might bf:Annotation function to treat an individual occurrence of a
particular property as the target of an annotation?

Such granular targets would often be necessary in a linked data
environment where we hope to be readily exchanging a little bit of data
here, there, and everywhere.  The postponed issue of provenance seems to
require such granular annotation for provenance to be meaningful in a
linked data environment.  If our automation systems would already be doing
all that they should do for us, we should already have provenance for MARC
records provided automatically without any necessary human effort at the
individual occurrence of every field, indicator, and subfield.

I can imagine that such granular annotation for BIBFRAME could function
inline if bf:Annotation could be the property of any other BIBFRAME
property.  Yet, how would such granular annotation work as an external
annotation to provide a target for bf:annotates?

Do individual occurrences of a particular property have implicit
identifiers in the context of a bf:Resource (bf:Work, bf:Instance,
bf:Authority, or bf:Annotation) or would it be necessary to add an
identifier to the property for the particular occurrence of the property
to function as a target?

How would such granular annotation function for any individual occurrence
of any RDF property using the Open Annotation Data Model,
http://www.openannotation.org/spec/core/ ?

"BIBFRAME Annotation Model - BIBFRAME Community Draft - 30 April 2013 -
bibframe.org/documentation/annotations/ " describes some thinking by the
early experimenters about annotation prior to annotation having been added
to the vocabulary.

The addition of annotation to the vocabulary provides little additional
information without additional notes and with code examples broken by some
bug.  [Nate Trail explained to me in a simple message perhaps mistakenly
sent offlist that if code examples have supposedly been added to
particular parts of the vocabulary but do not resolve properly on the
relevant vocabulary pages, then there is a bug.]

Target is described under roles, section 2.2, in BIBFRAME Annotation Model.

"Target of the Annotation: A BIBFRAME Work, Instance, or Authority".

Restricting the scope of targets for bf:Annotation to bf:Resources either
inline or using externally using bf:annotates seems unnecessarily
restrictive in a linked data environment.


Thomas Dukleth
Agogme
109 E 9th Street, 3D
New York, NY  10003
USA
http://www.agogme.com
+1 212-674-3783


[..]

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