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

BIBFRAME May 2013

Subject:

Re: Experimenting with BIBFRAME?

From:

"Ford, Kevin" <[log in to unmask]>

Reply-To:

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

Date:

Tue, 14 May 2013 18:03:50 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Dear Stuart,

I suspect what follows will be mostly unsatisfying.  The short is: on the whole, there's a lot of work to be done to address the type of general relations/specifity you are asking about.  In large part this is because your examples bring us very close to the "aggregates" issue.

I want to try to answer some of your questions, but I want to start with the last one, because it is so easy.  As for the following answers, they are hugely dependent on my understanding the question in the first place, and I felt those were a little unclear at times.

> (e) why does the definition from page 10 of the report not appear
> on http://bibframe.org/vocab/Instance.html Has the definition changed?
-- It's not different.  In fact, the definition at bibframe.org is virtually a word-for-word copy from the document.  It is, however, truncated to only the absolute essence at bibframe.org.  As we continue to update the vocabulary, we'll likely add more complete and encompassing definitions.

> (a) what is the status in the bibframe model
> of http://archive.ifla.org/VII/s13/frbr/frbr_current3.htm ?
-- The conceptual notion of the "Final report" would be a BIBFRAME Work (with IFLA as the creator).  This page - http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm - which is basically the landing page for the *entire* report would be an Instance of that Work.  However, the page you direct to in your question is not the same as the link I provided.  Your link is to a distinct chapter of that Work.  One option for the model would be to create a BIBFRAME Work resource for the chapter, which, being a BIBFRAME Work, would have an Instance (represented by your link).  There would be a defined relationship between the BIBFRAME Work for the entire report to the BIBFRAME Work for Chapter 3.  We've been experimenting with this idea.  

> (b) what is the status in the bibframe model
> of http://archive.ifla.org/VII/s13/frbr/fig3-1.jpg ?
-- Personally, I think this could be more granular a level of cataloging than we'll be feasible for most (time and money), but it could be treated in the same fashion.  The image could be a BIBFRAME Work (with its own Instance) and be associated with a Work resource of the chapter it is from. 

> (c) shouldn't the HTML Instance be defined as
> the http://bibframe.org/vocab/unionOf all the HTML pages that make up
> the HTML version of the report plus all their page dependencies (css,
> images, media files, etc)?
-- unionOf, though lacking a definition at bibframe.org, comes from a pre-defined relationship in MARC used mainly (if not exclusively) for serials.  It is too early to tell whether it has such a narrow use in the future, but it is meant to capture the notion that "This Work is the product of a merger of these two other Works."  I believe what you are trying to do is something completely different.  And, FWIW, the attempt to sensibly record how all the parts of an HTML document logically fit together is not something we're focused on.

Cordially,
Kevin


> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Stuart Yeates
> Sent: Saturday, May 11, 2013 7:31 PM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] Experimenting with BIBFRAME?
> 
> OK, I'll bite
> 
> I'm currently working to encode some of the texts I'm responsible for
> on the http://nzetc.victoria.ac.nz/ site. These are digitised
> historical texts published as sets of webpages. I'm currently
> struggling with the Work / Instance relationship, the issue I'm
> struggling with is actually duplicated exactly in the Primer
> at: http://www.loc.gov/bibframe/pdf/marcld-report-11-21-2012.pdf I'll
> go with the primer example, since it's better known.
> 
> An Instance is defined on page 10 as:
> 
> "BIBFRAME Instances reﬂect an individual, material embodiment of a
> BIBFRAME Work that can be physical or digital in nature. A BIBFRAME
> Instance exists as a Web based control point that includes properties
> speciﬁc to the materialization as well as contextual relationships to
> appropriate BIBFRAME Authorities related to the publication, production,
> distribution of the material resource. Each BIBFRAME Instance is an
> instance of one and only one BIBFRAME Work."
> 
> The figure on page 19 has three instances, a phyical, a PDF and an HTML,
> the HTML being identified
> as http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm
> 
> The conceptualisation issue I have seems to be expressable via the
> questions:
> 
> (a) what is the status in the bibframe model
> of http://archive.ifla.org/VII/s13/frbr/frbr_current3.htm ?
> 
> (b) what is the status in the bibframe model
> of http://archive.ifla.org/VII/s13/frbr/fig3-1.jpg ?
> 
> (c) shouldn't the HTML Instance be defined as
> the http://bibframe.org/vocab/unionOf all the HTML pages that make up
> the HTML version of the report plus all their page dependencies (css,
> images, media files, etc)?
> 
> (d) if an instance corresponds to only one Work, in the case of
> composite Works which are subsequently split into HTML along the lines
> of the original Works, do the HTML pages correspond to the original or
> composite Work?
> 
> (e) why does the definition from page 10 of the report not appear
> on http://bibframe.org/vocab/Instance.html Has the definition changed?
> 
> cheers
> stuart

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

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
https://listserv.loc.gov/cgi-bin/wa?A2=ind1305&L=BIBFRAME&D=0&P=108561
listserv.loc.gov
CC-MAIN-2023-06
57274
application/http; msgtype=response
sha1:4FOB5QYI47M762PYWNFN7FT3VSO7FJP2
<urn:uuid:004a9fba-ce6b-44c1-b80c-cdce413ade90>
2023-02-06T03:32:27Z
140.147.239.86
text/html
sha1:YQ2WLQFEEWERJRFNLBEEV4M6LVI23FGI
<urn:uuid:59c0e569-eda0-4aca-8014-0c0c84b933af>
https://listserv.loc.gov/cgi-bin/wa?A2=ind1305&L=BIBFRAME&D=0&P=108561
response
<urn:uuid:7248d606-8c53-4360-8371-2219ffbe02a1>
isPartOf: CC-MAIN-2023-06
publisher: Common Crawl
description: Wide crawl of the web for January/February 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-96
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/