Differences between versions dated 2010-04-08 16:35:55 and 2010-04-09 02:58:31
| Deletions are marked like this. | Additions are marked like this. |
| Line 58: | Line 58: |
| Bill: for "conversational" FRBR has lots of precedent: we want to describe a work and one particular manifestation's whereness | Bill: regarding who/what/when/where applied to a part-physical/part-digital thing/work/expression, suggest looking at FRBR for precedent: we want to describe a work and one particular manifestation's whereness |
| Line 60: | Line 60: |
| Charles: see VRA core | John: pedagogic problem when the metaphor breaks around the anchoring story |
| Line 62: | Line 62: |
| Jane: print vs born-digital are very different |
Charles: see VRA core for application to different object types Jane: print vs born-digital are fundamentally different |
KAP Task Group conference call 8 April 2010
Agenda:
-
Review and discuss new tools and possible effect of tools on our group's work.
-
"conversational metadata" (think: conversational Italian).
-
This is a new word I've been groping for in discussions with Adrian and others at CDL. It might represent a clarification of the "anchoring story", which currently requires choosing and describing an "anchoring expression". I'm wondering if this is an easier entree into simple metadata that permits one to describe the concept of the work in very lay terms rather than describing one particular expression of the work. The rigor that this would preserve would not be about faithfulness to an existing expression, but to roles identified in who/what/when/whereness that my "mom" would understand.
More on the new software below. The tools are bundled within a well-documented and tested open-source Perl module called File::ANVL (a typical name of many Perl modules), at
As alluded to in the DCMI status report for our group, it permits conversion of ANVL/ERC (short or long form) records to XML, Turtle, and JSON record formats. It does not include a web user interface, but is well-suited as infrastructure for such interfaces. Direct access to the highest (command-line) technical documentation is at
Separately, an application of Kernel being deployed at the CDL's UC Curation Center is Namaste tags, also available open-source with documentation at
The tools are designed to run under Unix and Windows.
Notes:
Adrian: tool documentation very technical, needs an overview and non-tech context
John: an AP is a technical document, and this serves a similar function
Bill: would be useful in ANVL doc to show full examples of conversions
John: full examples in a companion doc vs in the tool documentation?
Adrian: I can help choosing examples
All: draft AP doc Feb 20 2008 on wiki a good faith effort; given changes in Abstract Model perhaps AP work can be put on hold while tools are evaluated
Bill: regarding who/what/when/where applied to a part-physical/part-digital thing/work/expression, suggest looking at FRBR for precedent: we want to describe a work and one particular manifestation's whereness
John: pedagogic problem when the metaphor breaks around the anchoring story
Charles: see VRA core for application to different object types
Jane: print vs born-digital are fundamentally different
Bill: do it via guidelines for different object types
-
next call May 13
Attending:
-
Charles Blair, Jane Huang, Bill Moen, Adrian Turner, John Kunze