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  February 2012

BIBFRAME February 2012

Subject:

Re: The German National Library's response

From:

"Huwig,Steve" <[log in to unmask]>

Reply-To:

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

Date:

Mon, 6 Feb 2012 10:34:01 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (44 lines)

> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Karen Coyle
> Sent: Saturday, February 04, 2012 11:51 AM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] The German National Library's response


> I think that the biggest gap right now is to formulate best practices
> for the creation of URIs for the resources being described. That was
> also a recommendation in the W3C LLD report. We have to assume that
> bibliographic data will often be shared but could also be created
> independently in different libraries. It would probably be a good idea
> to have members of the library community using similar patterns for
> resource identifiers even though they may mint those identifiers
> independently. I also assume that most folks who will be creating
> identifiers would like to have a set of best practices to lean on
> rather than creating their own.

While it's generally more helpful to have readable URIs than to have
machine-generated ones, I think that effort expended to standardize URI
construction won't be very effective. Naming and organizational
conventions in one culture or system will likely not translate well to
different cultures or systems.

In my opinion, the most intellectual effort in this area should go into
defining a bibliographic record media type, or a family of media types,
or a framework for creating and using such media types. The idea is that
if the automated systems have unambiguous ways to process these media
types, then the users can expend as much or as little effort as they
need on naming and organization.

Naturally, the media type will use URIs and hyperlinking prolifically,
but in the end computers don't really care what the URIs look like as
long as they can be resolved. In fact, specifying URIs to be opaque in
the data model will be very helpful, as then we can be sure that the
transmission formats and system implementations won't need to rely on
potentially ambiguous or contentious naming and organization schemes.

More on URI opacity: http://www.w3.org/TR/webarch/#uri-opacity

Thanks,
Steven Huwig

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

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