Difference between revisions of "Minutes from January 27, 2009"
Jump to navigation
Jump to search
m (tweaks to formatting; respond to KH questions) |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | [[category: Meetings]] | ||
Attending: Syd Bauman (notes), Kevin Hawkins (chair), Chris Powell, Melanie Schlosser, Natasha Smith, Rich Wisneski, Perry Willett (notes) | Attending: Syd Bauman (notes), Kevin Hawkins (chair), Chris Powell, Melanie Schlosser, Natasha Smith, Rich Wisneski, Perry Willett (notes) | ||
Line 4: | Line 5: | ||
** see e-mail sent 2009-01-25 by KH for more details | ** see e-mail sent 2009-01-25 by KH for more details | ||
** everyone should read and response (deadline?) | ** everyone should read and response (deadline?) | ||
− | ** The BPG recommends including series title in <sourceDesc> but doesn't mention any other series information. Should we recommend other info like ISSN or series editor? | + | ** The BPG recommends including series title in <sourceDesc> but doesn't mention any other series information. Should we recommend other info like ISSN or series editor? We decided that these would be optional elements. KH said he would make changes to reflect this. |
* Levels | * Levels | ||
− | ** Level 1: CP: thinks | + | ** Level 1: CP: thinks <tt><ab></tt> is fine. |
** Level 2: RW: nothing to report | ** Level 2: RW: nothing to report | ||
** Level 3: NS: needs a P5 example | ** Level 3: NS: needs a P5 example | ||
− | *** | + | *** PW and CP said this case was envisioned for conversion from HTML at Virginia, so they might have an example. CP said there's still a need for Level 3 as evidenced by the recent post to TEI-L from Martin Mueller asking about <tt><lb></tt>s. |
− | ** Level 4: Linda Cantara no longer working on this, but Matt Gibson is | + | ** Level 4: Linda Cantara no longer working on this, but Matt Gibson is supposed to be. Need to convert example to P5. SB can do this. |
** Level 5: same is w/ L4 | ** Level 5: same is w/ L4 | ||
− | *** we need to add an example or two, although don't need to go into full detail | + | *** we need to add an example or two, although don't need to go into full detail. KH suggested just taking one of the P4 examples and adding some semantic, linguistic, etc. tags. without giving any particular guidance on that. |
* Filenaming: | * Filenaming: | ||
** agreed to point to or incorporate IUDLP guidelines | ** agreed to point to or incorporate IUDLP guidelines | ||
− | ** agreed to 8-dot-3 health warning | + | ** agreed to 8-dot-3 health warning <span style="color: red">[KH: I thought we agreed to warning against using extensions longer than 3 but not on giving any recommendation on the filename before the dot aside from what's in IUDLP.]</span> <span style="color: olive">[SB: My notes have exactly as listed here.]</span> |
− | ** question on ".tei" vs ".xml" extension: agreed to use *.xml extension | + | ** question on ".tei" vs ".xml" extension: agreed to use *.xml extension <span style="color: red">[KH: I thought we agreed to tell people to be internally consistent but otherwise to use what they want.]</span> <span style="color: olive">[SB: I dunno]</span> |
** agreed that internal consistency is more important than following a particular set of restrictions [I'm going to suggest this become a general recommendation--SB] | ** agreed that internal consistency is more important than following a particular set of restrictions [I'm going to suggest this become a general recommendation--SB] | ||
− | * | + | * <tt><ab></tt> vs. <tt><p></tt>: |
− | ** in the pseudo-paras of Level 1 and Level 2 we agreed to | + | ** in the pseudo-paras of Level 1 and Level 2 we agreed to <tt><ab></tt> |
* Numbered/unnumbered divs: we agreed that there is no consensus on this issue, and we shouldn't make a recommendation for one over the other. Instead, we should: | * Numbered/unnumbered divs: we agreed that there is no consensus on this issue, and we shouldn't make a recommendation for one over the other. Instead, we should: | ||
Line 28: | Line 29: | ||
** describe the reasoning behind choosing one | ** describe the reasoning behind choosing one | ||
** describe process of converting one to the other (and provide tools?) | ** describe process of converting one to the other (and provide tools?) | ||
− | ** recommend a place in the header to record the decision | + | ** recommend a place in the header to record the decision (probably <tt><encodingDecl</tt>) |
− | ** schema should enforce consistency within | + | ** schema should enforce consistency within whole file (<tt><front></tt>, <tt><body</tt>, and <tt><back</tt> elements) |
− | * | + | * <tt><pb></tt>s |
− | ** leave recommendation as is | + | ** leave recommendation as is (always within <tt><div></tt>s) |
* meeting at DLF Spring Forum in Raleigh NC (May 4-6) | * meeting at DLF Spring Forum in Raleigh NC (May 4-6) | ||
− | ** KH will check | + | ** KH will check on status of getting a meeting room |
** propose a paper/panel about it? | ** propose a paper/panel about it? | ||
− | * People should remove comments from BPG if they feel the issue has been resolved. KH will | + | * People should remove comments from BPG if they feel the issue has been resolved. KH will make any edits not done by others before our next meeting. Next we need to get examples and then do the ODDs. |
Latest revision as of 06:41, 10 February 2009
Attending: Syd Bauman (notes), Kevin Hawkins (chair), Chris Powell, Melanie Schlosser, Natasha Smith, Rich Wisneski, Perry Willett (notes)
- Header:
- see e-mail sent 2009-01-25 by KH for more details
- everyone should read and response (deadline?)
- The BPG recommends including series title in <sourceDesc> but doesn't mention any other series information. Should we recommend other info like ISSN or series editor? We decided that these would be optional elements. KH said he would make changes to reflect this.
- Levels
- Level 1: CP: thinks <ab> is fine.
- Level 2: RW: nothing to report
- Level 3: NS: needs a P5 example
- PW and CP said this case was envisioned for conversion from HTML at Virginia, so they might have an example. CP said there's still a need for Level 3 as evidenced by the recent post to TEI-L from Martin Mueller asking about <lb>s.
- Level 4: Linda Cantara no longer working on this, but Matt Gibson is supposed to be. Need to convert example to P5. SB can do this.
- Level 5: same is w/ L4
- we need to add an example or two, although don't need to go into full detail. KH suggested just taking one of the P4 examples and adding some semantic, linguistic, etc. tags. without giving any particular guidance on that.
- Filenaming:
- agreed to point to or incorporate IUDLP guidelines
- agreed to 8-dot-3 health warning [KH: I thought we agreed to warning against using extensions longer than 3 but not on giving any recommendation on the filename before the dot aside from what's in IUDLP.] [SB: My notes have exactly as listed here.]
- question on ".tei" vs ".xml" extension: agreed to use *.xml extension [KH: I thought we agreed to tell people to be internally consistent but otherwise to use what they want.] [SB: I dunno]
- agreed that internal consistency is more important than following a particular set of restrictions [I'm going to suggest this become a general recommendation--SB]
- <ab> vs. <p>:
- in the pseudo-paras of Level 1 and Level 2 we agreed to <ab>
- Numbered/unnumbered divs: we agreed that there is no consensus on this issue, and we shouldn't make a recommendation for one over the other. Instead, we should:
- encourage consistency within texts and collections
- describe the reasoning behind choosing one
- describe process of converting one to the other (and provide tools?)
- recommend a place in the header to record the decision (probably <encodingDecl)
- schema should enforce consistency within whole file (<front>, <body, and <back elements)
- <pb>s
- leave recommendation as is (always within <div>s)
- meeting at DLF Spring Forum in Raleigh NC (May 4-6)
- KH will check on status of getting a meeting room
- propose a paper/panel about it?
- People should remove comments from BPG if they feel the issue has been resolved. KH will make any edits not done by others before our next meeting. Next we need to get examples and then do the ODDs.