LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


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

BIBFRAME March 2013

Subject:

Re: Reuse (or not) of existing ontologies

From:

Eric Miller <[log in to unmask]>

Reply-To:

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

Date:

Wed, 13 Mar 2013 17:13:00 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

On Mar 11, 2013, at 5:04 PM, Owen Stephens <[log in to unmask]> wrote:

> I don't think there has been any discussion on the list about this yet (sorry if I've missed it)

If you missed it, that makes two of us. But your question relates to an important design decision so thanks for bringing this up.  To back up a bit (and ensure shared context) the following is a bit dated, but I think still quite useful:

[[
The BIBFRAME Vocabulary

The BIBFRAME model is defined in RDF.
 
The RDF vocabulary for the draft BIBFRAME model, to be available shortly, will provide a convenient way of navigating around the RDF model.

The suggested namespace for the BIBFRAME model is http://loc.gov/bibframe/vocab. An RDF/XML serialization of this vocabulary is expected to be available at this location. While the recommendation of a singular namespace is counter to several current Linked Data bibliographic efforts, it is crucial to clarify responsibility and authority behind the schematic framework of BIBFRAME in order to minimize confusion and reduce the complexity of the resulting data formats. It will be the role of the Library’s standards stakeholders to maintain the connections between BIBFRAME model elements and source vocabularies such as Dublin Core, FOAF, SKOS and future, related vocabularies that may be developed to support different aspects of the Library workflow.

Identifier persistence is not a technology issue but rather an organizational, policy, and community one. A persistence policy should be defined stating clearly the persistence and change management mechanisms.
]]
-- http://www.loc.gov/marc/transition/pdf/marcld-report-11-21-2012.pdf

But certainly more background and detailed discussion is warranted. Quickly scanning the growing thread around this topic, it seems that many think so as well ;)

> Much of the practical work in the area of linked data and libraries has made use of common existing vocabularies to publish data. This commonly includes:
> 
> DC/DC Terms
> FOAF
> Bibliographic Ontology (aka Bibo)

And thats just a start!

> I think I've seen these in every implementation of linked data representations of library materials. They are often used alongside other existing vocabularies (Bio, frbr, isbd) and often a specifically created vocabulary to deal with elements that fall outside these existing vocabs (e.g. the BNB uses http://www.bl.uk/schemas/bibliographic/blterms#, Libris uses http://libris.kb.se/vocabulary/experimental#)

Our initial linked data analysis identified literally dozens of namespaces used in the Library community reflecting various stages of experimentation. More if you start to broaden analysis to the include museums, archives, galleries, etc.. And even more if you broaden into more of how we might imagine patrons / others adding value to this data.  This shouldn't be a surprise to anyone familiar with RDF / Linked Data. There isn't one vocabulary that works (or will work) for everything. ;)

> In light of this it seems notable that so far Bibframe doesn't specify the use of any vocabularies outside bibframe specific elements, and there is no information on how the bibframe elements might map to existing vocabularies.

Good point.  Eventually we do intend to work on non-normative transform and mappings from and too other vocabularies, which allows pragmatic reuse.  And over time, with usage experience some of those mappings might take on normative force.  But certainly this is underspecified and more work in this area is required. 

> So I guess my first question is - shouldn't Bibframe reuse existing vocabularies where possible? If there are arguments against this - what are they?


There are many benefits of vocabulary reuse, but as with many things, there are costs as well that need to be carefully considered.  As Ross points out, you can't control the fate of vocabularies you don't own. Designing systems that leverage multiple vocabularies managed by various stakeholders is a tricky issue and one that requires careful considerations. There are many reasons why namespaces / vocabulary "drift" over time (404 being a worse case example) and all of these may have an affect on systems. Business acquisitions (anyone recall http://my.netscape.com/rdf/* ?), economic factors, organizational changes, changing social interests, etc. are just a handful of reasons for causing such change, but thinking ahead to infrastructure to support the next 40+ years of Libraries, namespace persistence is a key point to consider when dealing with how best to integrate and invest in vocabulary terms outside of ones community.

We accept a level of risk by basing BIBFRAME on open, royalty free W3 standards because we have confidence in a shared (Web) community's investment in these underpinning vocabularies. Basing BIBFRAME on RDF (and the Web) allows us to more easily weave in additional vocabularies as new requirements, customization and localization demand while still achieving resilience in systems. While BIBFRAME is being built on a framework that supports mix-matching of terms, its taking an appropriately critical view regarding minting new terms vs adopting external ones. Making formal connections between BIBFRAME model terms and other vocabularies terms errs on the side of caution when striking a balance between the stability of BIBFRAME (and an existing community in which it serves) and a web of relationships with other communities.  And while I expect this will lead to some duplication of terms, as Karen pointed out, Library terms are generally more precise than other (intentionally broader) community terms.  So, while I expect Library’s standards stakeholders to maintain the connections between BIBFRAME model elements and other relevant vocabulary terms, I expect many of these relationships to be "is Refinement Of" ones. ;)

At this point, i'd be remiss in not mentioning the vocabulary is in development, draft, subject to change, etc.

In the meantime, my hope is though this effort we will also collectively advance the discussion of namespace persistence to help ensure weather we map to terms (or mix / match these in various community profiles) the terms in question will continue to exist though out the course of BIBFRAME. There are many examples of stated persistence policies for vocabularies [0][1][2][3].  But I think far more could be done (a simple set of machine readable 'living will' templates might be an example of such a step [4]) to help ensure social and organizational backups. 

Again, identifier persistence is not a technology issue but rather an organizational, policy, and community one. A value in BIBFRAME namespace(s) will be proportionate to the community that invests in them as well as the organization commitment to these namespaces and terms. 

--
Eric Miller
President, Zepheira "The Art of Data"
http://zepheira.com/ tel:+1.617.395.0229


[0] W3C URI Persistence Policy
- http://www.w3.org/Consortium/Persistence.html

[1] Namespace Policy for the Dublin Core Metadata Initiative (DCMI)
- http://dublincore.org/documents/dcmi-namespace/

[2] DCMI Generic Namespace Policy for RDF Vocabularies
- http://dublincore.org/documents/2011/05/02/dcmi-namespace-generic/

[3] Agreement between DCMI and the FOAF Project
- http://dublincore.org/documents/dcmi-foaf/

[4] I think a simple set of machine readable templates may serve as a very useful means for defining a "living will" for namespaces. Something akin to CC templates that contains...

1) The owner
2) The namespace URI(s)
3) A policy concerning classes of changes that are allowed
4) Designator on institution committed to taking over namespace in the event a current party is (for whatever reason) no longer able to do so.

might be a useful step in formalizing various informal policies that would aid in stakeholder discussions.

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

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