Difference between revisions of "Minutes from February 17, 2009"
(New page: minutes syd, lisa, kevin, melanie, rich relationship (policy-wise) between the TEI Header and MARC Melanie and Kevin were working on describing AACR2 (Anglo American Cataloging Rules: ...) |
|||
| Line 7: | Line 7: | ||
Melanie and Kevin were working on describing AACR2 (Anglo American Cataloging Rules: 2nd edition) practice. | Melanie and Kevin were working on describing AACR2 (Anglo American Cataloging Rules: 2nd edition) practice. | ||
| − | A couple of paragraphs of introduction in the TEI Header and all of these paragraphs need to be revised | + | A couple of paragraphs of introduction in the TEI Header and all of these paragraphs need to be revised. Needs a new set of eyes. A big re-write (lisa volunteers) and then forward to the BPG once it's cleaned up. |
| + | |||
| + | '''Identifiers that point to OCLC & other identifiers''' | ||
| + | |||
| + | type attribute -- DECISION: do not use teiHeader @type to note what description standard is being used to determine values (that is, drop AACR2, ISBD(ER), etc.) | ||
| + | |||
| + | recording what description standard you're using. what value is there in recording this in a machine read-able format? it's very important for human to read? if you were processing a large group of documents, then it would be easier to group the like docs together. | ||
| + | |||
| + | can we create a paragraph (prose) in encodingDesc? | ||
| + | |||
| + | How to link to outside stuff (MODS, database records)? discussion again of the @tpe | ||
| + | |||
| + | What does level@ mean in this titleStmt in the teiHeader? | ||
| + | -example of Moby Dick; | ||
| + | -TEI guidelines say "required when applicable" | ||
| + | |||
| + | why use level for the title element? | ||
| + | -when mentioned in prose, | ||
| + | -when used in citations | ||
| + | |||
| + | DECISION: we don't think level is useful inside the TEI Header title elements | ||
| + | |||
| + | DISCUSSION: it should be clear whether this document is prescriptive. (Lisa handle in the introduction) (all elements and values and attributes listed in the section or not) | ||
Revision as of 20:39, 17 February 2009
minutes
syd, lisa, kevin, melanie, rich
relationship (policy-wise) between the TEI Header and MARC
Melanie and Kevin were working on describing AACR2 (Anglo American Cataloging Rules: 2nd edition) practice.
A couple of paragraphs of introduction in the TEI Header and all of these paragraphs need to be revised. Needs a new set of eyes. A big re-write (lisa volunteers) and then forward to the BPG once it's cleaned up.
Identifiers that point to OCLC & other identifiers
type attribute -- DECISION: do not use teiHeader @type to note what description standard is being used to determine values (that is, drop AACR2, ISBD(ER), etc.)
recording what description standard you're using. what value is there in recording this in a machine read-able format? it's very important for human to read? if you were processing a large group of documents, then it would be easier to group the like docs together.
can we create a paragraph (prose) in encodingDesc?
How to link to outside stuff (MODS, database records)? discussion again of the @tpe
What does level@ mean in this titleStmt in the teiHeader? -example of Moby Dick; -TEI guidelines say "required when applicable"
why use level for the title element? -when mentioned in prose, -when used in citations
DECISION: we don't think level is useful inside the TEI Header title elements
DISCUSSION: it should be clear whether this document is prescriptive. (Lisa handle in the introduction) (all elements and values and attributes listed in the section or not)
