TEIWiki - User contributions [en]

June 6, 2016

2016-06-09T17:26:03Z

Peter Gorman: Created page with "June 6, 2016 =Attendees= * Kevin S. Hawkins (University of North Texas Libraries) * Syd Bauman (Northeastern University Libraries) * Peter Gorman (University of Wisconsin–Mad..."

June 6, 2016

=Attendees=

* Kevin S. Hawkins (University of North Texas Libraries)
* Syd Bauman (Northeastern University Libraries)
* Peter Gorman (University of Wisconsin–Madison Libraries) (recorder)

=Ticket Triage=

* Bauman noticed that the build process for the ODD files is broken, because it relies on resources that no longer exist. Bauman will open a new Git Issue for it. [done]

===Issue 3===

* Mostly complete, but Gorman will finish the remaining tasks, mainly updating the examples throughout the document.

===Issue 5===

* Bauman noted that there are actually 4 options: @key, @seeRef (though not available for all elements), tag URIs (RFC 4151), or private URI/prefixDef. Hawkins added @xml:base. They can be used in combination, as well: a short private URI can be created that expands to a tag URI.

* Bauman observed that tag URIs have advantage of being externally defined, and hence may be useful in other contexts, while private URI/prefixDef (http://wiki.tei-c.org/index.php/Prefix_Definition_Proposal) is specific to TEI.

* Recommendation: encoders should use tag URI instead of @key, but may use private URI/prefixDef if it better suits a project's needs, or if other URI schemes prove to be too cumbersome.

* Hawkins will update the ticket [done]

===Issue 8===

* Recommendation: do not change the discussion ofextent> in BPTL. Issue withdrawn.

===Issue 15===

* Gorman and Bauman thought that <distinct> would be useful for texts at level 4. Even though it adds to an already large tagset, it it usefully distinct from existing elements.

* Recommendation: add <distinct> to BPTL level 4. Assigned to Bauman.

===Issue 18===

* Group discussed which of the two approaches outlines in the ticket would be the lesser evil. Bauman noted that option "A" is not valid TEI. Option B does not improve the upgrade path from Level 1 to 2 or 2 to 3, and may in fact create work in restructuring block-level elements (i.e., fprm pages to paragraphs).

* Recommendation: do not change existing guidelines.

===Issue 24===

* Since event tagging is not provided for in TEI, this Working Group cannot express this proposal as a constraint of TEI.

* Recommendation: propose this to the TEI Council as a feature request.

* Hawkins will close the Issue.

===Issue 25===

* The group was uncertain what specific action is being requested; is it about adding to the table of MARC/teiHeader mappings? If there are elements in the body that would enhance a MARC record, would they have to be expressed in a new table? Could we even make feasible suggestions (e.g., algorithmically adding <name>s as MARC 6xx or 7xx fields) that would be compatible with RDA?

* It may be possible to extract a table of contents from a document's <div> structure and <heads>, e.g., to create a MARC 505 field. That would not be a recommendation for the teiHeader per se, unless the suggestion is to replicate ToC information in the teiHeader - but then the body and teiHeader could fall out of sync.

* Hawkins will add a comment to the ticket asking for clarification of this issue. [done]

Workgroup to revise the Best Practices for TEI in Libraries

2016-06-09T17:25:25Z

Peter Gorman: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* <strike>Andrew Rouner (andrew.rouner@gmail.com)</strike>

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

Workgroup to revise the Best Practices for TEI in Libraries

2016-03-07T14:00:39Z

Peter Gorman: /* Members */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* March 7, 2016

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]