TEIWiki - User contributions [en]

TEI-Council-FAQ

2024-10-18T17:49:12Z

Syd: add new Pending status

So you have some questions about how the [[Council|TEI Technical Council]] works? This page has been set up to answer questions that new council members (or other curious parties) may have.

== Overview ==

=== How does the Council do its work? ===

By every means possible. These include monthly remote meetings, email, widely circulated discussion documents, and public debate in other contexts such as TEI-L and GitHub issues. The Council meets face to face twice a year (usually one of those meetings concurrent with the TEI Annual Meeting), and many more times than that virtually. Sub-groups of Council will often form around particularly large or complex issues and may meet separately to deal with them.

=== And what work does it do? ===

You should probably review the recent official work of the Council by reading the last few sets of minutes: http://www.tei-c.org/Council/ has an index page which links to them all (when we remember to update it). The minutes record topics discussed and responsibilities allocated at the Council level. Of course many Council members are also active in subgroups (formal or informal) of the Council or SIGs, which may be documented elsewhere as well.

Generally, things in Council work like this:

# A bug report or feature request is reported by anyone at [https://github.com/TEIC/ GitHub] for the [https://github.com/TEIC/TEI/issues Guidelines] or [https://github.com/TEIC/Stylesheets/issues Stylesheets].
# Sometimes others notice the ticket and comment on it.
# Sometimes a Council member may make an executive decision on the ticket. If it's a corrigible error or bug, we can just fix it in the appropriate ODD file(s) (also in GitHub). If it is not a real issue, sometimes the ticket will just be closed. If you do not have developer access on GitHub you'll ask to be added to the Council team there. Otherwise, it's discussed either by email on the Council mailing list or at a Council meeting (conference call or in-person meeting). Comments are recorded in the ticket reflecting the decision reached, and changes are made in GitHub by a member of the Council sometime thereafter.
# The change shows up on tei-c.org after the next TEI "release", which happens about two or three times a year.

However, Council does sometimes consider lengthy proposals circulated to Council outside of GitHub and vote on them as packages, with the changes grouped together in a sensible way so they can be considered in smaller packages, or with the changes listed individually.

=== And what is its scope? ===

The Council's primary responsibility is to act as technical watchdog for the intellectual content of the TEI Guidelines. That is to say: it has the final say in just about every aspect of the TEI encoding scheme -- what elements exist in it, what they are called, how they should be used.

=== How do I join the TEI Council mailing list? ===

We have had the practice on the Council so far that elected members get added immediately to the list (and to the telecon, if there is one), with every right to participate, while outgoing members stay on until the end of their term. To join or discuss any problems using the list contact the [mailto:tei-council-owner@lists.tei-c.org TEI Council mailing list owner], currently this is Luis Meneses (Victoria). There is also a joint Board/Council mailing list to which you should be added as well.

=== Why are some people on the Council email list or attending Council meetings even though they are not on the list of elected members? ===

In addition to the members of the Council, the chair of the TEI Technical Council may invite others not elected to the Council to meetings (e.g. to speak to a particular issue). Historically the Council often invited a representative of the Board to the Council mailing list and meetings. The TEI-C Webmaster (currently Luis Meneses) are also on the mailing lists.

=== What are the various job roles on the TEI Council? ===

==== TEI Technical Council Member ====
A TEI Technical Council Member is expected to participate in all aspects of Council work. This means that they should learn how the TEI infrastructure is organised and [http://www.tei-c.org/Activities/Council/Working/tcw20.xml how to edit the TEI Guidelines], asking on the Council list any questions they might have. They will be expected to come to face-to-face ("f2f") meetings (often two per year) and participate in a couple other teleconferences per year. They will be assigned (or take) feature requests/bugs on [https://github.com/TEIC the TEI Consortium's GitHub site], for which they will be in charge of encouraging discussion, reporting on the issue to Council, and eventually implementing (or ensuring implementation) of the resulting decision. A TEI Technical Council Member is expected to participate in the maintenance and development of the TEI Guidelines and related outputs. Some elected TEI Council members focus more on particular aspects of the infrastructure or stylesheets as part of the contribution to the Council. Council members should always act to represent what they believe are the opinions and best interest of the community that has elected them.

==== TEI Technical Council Chair ====
The TEI Technical Council Chair's role is to administrate and facilitate the work of the TEI Technical Council. If all of the Council are the elected servants of the community, then the Council Chair is the servant of the servants of the TEI (''Servus servorum TEI''). The duties of the Technical Council Chair include (in no particular order):
* ensuring the delivery and maintenance of the Guidelines
* arranging for Council members to actively participate in Council activities
* arranging and chairing the face-to-face meetings (in conjunction with the local organiser)
* arranging and chairing the teleconferences
* creating agendas for those meetings, and ensuring minutes are written and posted of them
* assigning tickets in [http://github.com/TEIC/ the TEIC Github organization]
* acting as SIG coordinator
* liaising for and reporting on Council activities at all Board meetings
* reflecting Council wishes in Board discussions
* acting as a public point of contact and responding to technical enquiries (messages to council@tei-c.org are forwarded to the Council Chair)
* announcing new releases of the Guidelines on the TEI-L mailing list
* ensuring the smooth running of the TEI Technical Council

The TEI Technical Council Chair is also a member of the Council, so has all the duties and obligations of being a council member as well.

==== Release Technician ====
The TEI Guidelines release process (see [http://www.tei-c.org/Activities/Council/Working/tcw22.xml tcw22: Building a TEI Release]) involves a single individual responsible for 'pushing the button' and completing the steps required to make a TEI Guidelines release live. This is not a standing position; instead, the responsibility rotates for every release in order to demystify the release process and spread the expertise beyond Oxford staff. Although we have documented the work in quite a detailed manner, it is a non-trivial process and involves a fair degree of work. A release technician is usually required to set aside a whole day for the release process since history teaches us that often the entire process needs to be re-run to correct last-minute errors.

==== TEI-C Webmaster and Assistant Webmaster ====

The TEI-C Webmaster and Assistant Webmaster are not officially part of the Council but may be added to the mailing lists at the discretion of the Council Chair. They are responsible for the smooth running of the TEI-C Website.

=== How is the TEI Technical Council Chair elected? ===

The [http://www.tei-c.org/About/bylaws.xml#body.1_div.3_div.3 Bylaws of the TEI-C] say that:
<blockquote>
The Chair of the Technical Council shall be elected by the voting Members of the TEI-C Technical Council from its membership and shall serve as the chief technical officer of the Consortium. If no Technical Council Member is able or willing to assume the chair, the Technical Council may request the Board of Directors to second one of its elected members to the role, or it may nominate a non-elected individual.
</blockquote>
This leaves it intentionally vague as to the precise process the TEI Technical Council will follow. For now there is vague consensus that they will do something like the following. Note that timeframes below are not intended to be rigid or precise, but rather to be suggestive.
# The new Technical Council Members will be added to the tei-council (and tei-board-council) mailing lists shortly after the members' meeting. Up until around the last last Friday in November those who are Council members for next year will consider whether they want to run to be Chair of the TEI Technical Council. The current Chair will facilitate this process by answering any questions about the post. Before that date those intending to stand should send a statement of some sort to the Council mailing list detailing why they think the council members should vote for them.
# On or around the first weekday of December if only one person is running then the Chair will announce this to the tei-council mailing list as an acclamation (and after a short period for objections, to the Board and TEI-L). If multiple people are running, then the Council Chair will appoint a "returning officer" who is not a member of the incoming Council (i.e., not a voter and thus at least a somewhat disinterested party). The returning officer will set up an electronic voting system with the names of the candidates. This should be a private election with no one able to determine who has voted for whom. E.g. if using opavote.org this should have the following settings:
## Results only shown at end
## Method: "Plurality/FPTP/SNTV" for 2 candidates, "Instant Runoff Voting" for 3 or more
## a single winner
## Ballot type: "choose one" for 2 candidates, "ranked enhanced" for 3 or more
## candidate order shuffled
# The returning officer should ensure the election runs for at least 4 days, preferably in early December, after announcing it on the tei-council mailing list (and distributing ballots depending on the system).
# The results will be announced publicly on the tei-council mailing list, and Council members given a brief chance to raise any objections with the election before the current Chair informs the Board and announces it more publicly on TEI-L.
# The new Chair assumes the role on 1 January. The current chair steps down on 31 December. The outgoing and incoming chairs should co-ordinate activities between the election and 1 January so as to ensure a smooth transition. (Remembering that the current Chair might be departing off council at the end of that year.) These dates and timescales can of course shift and are not meant to be set in stone.

== Terminology ==

=== What is a "corrigible error"? ===

This is a term that comes up in Council discussions and refers to an error or inconsistency in the Guidelines that can be fixed without requiring a deprecation period.

=== What was the War on Free-text-bearing Attribute Values? ===

The move from SGML to XML included (some would say necessitated) The War on Free-text-bearing Attribute Values, also known as the War on Free-text-bearing Attributes or the War on Attributes for short. This war was an effort to disallow free text in the value of any attribute recommended by the ''Guidelines''. There were two main reasons for this.

First, XML does not have SDATA entities, and thus has no built-in mechanism for representing a character that is not available in Unicode. The obvious mechanism to represent a character outside of Unicode in XML is to use an element. In TEI, this is the <tt><g></tt> element. However, an element cannot be inside an attribute value. Thus any free text which ''might'' include a character outside of Unicode could not be properly expressed in an attribute value — it would have to be element content so it could include an element itself. (This was also the reason behind macro.xtext, which in general should be used instead of <tt>textNode</tt> in TEI content models.)

Secondly, it was observed, XML’s internal mechanism to specify language (<tt>@xml:lang</tt>) does not differentiate between an element’s attributes and its content. However, it is quite reasonable to believe (at least, in DH) that an encoding would need to specify the natural language of any free text. One way around this problem would have been to avoid <tt>@xml:lang</tt> and instead develop a TEI-specific system for specification of language that did not have this limitation. Another was to avoid allowing free text in an attribute value, such that all free text would be in element content, which element could bear an <tt>@xml:lang</tt>. TEI chose the latter.

=== What is the "Birnbaum doctrine"? ===

As expressed in [http://www.tei-c.org/Activities/Council/Working/tcw09.xml TCW09: Backward Compatibility and the Maintenance of the Text Encoding Initiative Guidelines], we should avoid breaking backward compatibility and only do so after serious consideration. It does not mean that we cannot break backwards compatibility, just that we've agreed a set of steps to take when we do so. Our deprecation policy supersedes some of this.

=== In what ways will Council break backwards compatibility? ===

For an egregious error, we might actually change a content model immediately. More often, we will survey the community on TEI-L before doing so, and we might [[Practices no longer recommended or now deprecated|deprecate]].

=== What is the "Durand Conundrum"? ===

The "Durand Conundrum" was suggested by David G. Durand concerning the TEI's decision to use the [[ODD | TEI ODD]] meta-schema language rather than just one of the existing schema languages. Given that we decided to use our own language, why use RelaxNG as part of that language for describing content models? Generally, the consensus is that [[ODD | TEI ODD]] gives us greater power and flexibility than any individual schema language can do in that we can model things that those schema languages are currently unable to cope with. TEI ODD gives the ability for a single document to produce both documentation and schema since these are inherently interlinked. It also keeps the TEI honest, in requiring it to use its own system to document schemas. [[ODD | TEI ODD]] does currently have some problems, a few of which are detailed at [[ODD-dev]] and successive revisions of TEI ODD are intended to solve some of these. Increasingly [[ODD#Future_plans:_.22Pure_ODD.22|the work on Pure ODD elements for content models and datatypes]] has cut the gordian knot of this problem.

=== What does "no magic" mean? ===

'Magic' in the sense sometimes used in Council discussion refers to pre-existing or special knowledge required to process something. For example, it was only by 'magic' that a TEI ODD processor would know to add attributes from the att.global attribute class to elements until this was changed to make all element specifications have to explicitly claim membership in this class if they wanted the global attributes. Knowing to add them was 'magic', and in general it is better if any requirements or understood knowledge is explicitly documented. While some 'magic' of understood conventions or processing will always remain in complex technical systems, the Council strives to at very least enable the possibility of documenting the underlying rules when it discovers them. James Cummings has been a fervent proponent of the removal of any understood 'magic' rules from the TEI.

=== What is a non-deterministic content model? ===

If you have a content model for <a>:

<pre>
b*, c?, b*
</pre>

and you have a document with:

<pre>
<a>
<b/>
</a>
</pre>

then a parser can't tell whether the <b/> matches the first b* or the second b* in the content model. Thus, the content model itself is called “non-deterministic”. DTDs and W3C XML Schemas reject non-deterministic content models. Thus, if we were to create one in the TEI, validation with DTD and XSD would fail due to errors ''in the schema'', regardless of whether the instance document has an occurence that is non-deterministic or not.

=== What are Janus elements? ===

These are pairs of elements that are in a sense two sides of the same coin, such as orig and reg, corr and sic, abbr and expan.

=== What does it mean to say that elements tessellate? ===

This means that all textual content is included in exactly one instance of an element. For example, once you start using divs (numbered or unnumbered), all text thereafter must be inside of one of the divs: you can't start using p elements that are not wrapped in a div.

In the Guidelines this is sometimes referred to as end-to-end segmentation.

== Meetings ==

=== Where are the minutes of previous meetings? ===

Minutes are [http://www.tei-c.org/Activities/Council/Meetings/index.xml archived on the TEI website]. Interim states of minutes may at times live in this wiki, Google Docs, or elsewhere.

=== How are the Council meetings held? ===

The Council usually makes use of Google Meet/Hangouts for their meetings. The meeting link will be in the agenda and/or sent out on the Council list before the meeting.

=== What funding is available for Council Activities? And how do I get reimbursed? ===

The TEI funds the participation of the council members in the meetings.

If the council has a meeting, then the council members' travel, hotel, etc. will be reimbursed with proper receipts. The TEI reimburses all reasonable expenses in keeping with standard practice at most universities and granting agencies. We cover meals, travel, lodging, and other common daily travel expenses. Airfare should be economy class and direct return, unless otherwise arranged with the Treasurer prior to your trip. If you have questions about reimbursement procedures, including what is reimbursable, please email Hugh Cayless, the TEI treasurer, at philomousos AT gmail.com.

Use the TEI Travel expense form available here: https://tei-c.org/tei_travel_form/ '''Expense forms should be submitted within 1 month of the end of the meeting.'''

== How we get work done ==

=== I have something to say about a GitHub Feature Request or Bug: Should I comment on the issue or the TEI Council mailing list? ===

There is no hard-and-fast policy on this. The mailing list is a better place for ongoing discussions where people are arguing back and forth during decision making. The GitHub tracker is the appropriate place to record opinions, positions, and decisions for posterity, especially if such would help a) whoever is implementing the decisions recorded in the ticket, b) anyone revisiting this decision later to retrace the thinking. The [http://lists.tei-c.org/pipermail/tei-council/ TEI Council mailing list archives] are public, so if substantial discussion has taken place there (or indeed on TEI-L), this can also be linked to from the ticket.

=== When is discussion on an element or topic "closed" and how do I know? ===

Any topic can be revisited at any point, even in the published guidelines, through posting a feature request on GitHub. Council-specific issues should be raised on the council mailing list, after having reviewed any previous discussion on the topic in the [http://lists.tei-c.org/pipermail/tei-council/ tei-council mailing list archives].

=== How can I find out about every time a ticket is created or commented on? ===

Each repository has a "watch" control, which is to be found on the top right or the repo's GitHub page, below the navigation bar. This control lets you manage notifications in various ways.

=== How are tickets assigned in GitHub? ===
All members of Council are made part of the Council Team on the GitHub TEIC Organisation and meant to take an active role in the development and maintenance of the TEI Guidelines. This means that they have write access to the TEI Guidelines Github Repository, and tickets can be assigned to them in the ticket trackers. They can also update and modify tickets. This means that Council members are free to 'take' tickets which they wish to oversee. Other Council members can also 'give' tickets to each other if they think someone particularly suited to overseeing a particular ticket. (However, usually they should have the Council member's permission to do so.) On a regular basis the Council Chair will assign tickets to Council members, if a ticket gets assigned to them that they don't want to do they should tell the Chair and/or ask other Council members to swap.

=== What do the issue labels mean? ===

* '<span style="color:red; font-weight:bold;">Status: Blocked</span>' means that the issue cannot be progressed because it requires either that another issue be completed first or that more information is needed from the reporter or a third party.

* '<span style="color:orange; font-weight:bold;">Status: Needs Discussion</span>' means that the issue has not been talked about enough yet to resolve it. New issues nearly always go into this status first. When Council has face-to-face meetings, these are usually the issues we target first.

* '<span style="color: #5319E7; font-weight:bold;">Status: Pending</span>' means that the issue is pending some work. Often this means that some work is to be done (typically in a branch named after the issue) and then discussed by Council..

* '<span style="color:green; font-weight:bold;">Status: Go</span>' means that the ticket has been discussed, there is general consensus on what the correct thing to do is, and it has been assigned for someone to ensure its implementation.

* Other labels should be self-explanatory, and are sometimes created as needed to group tickets for various purposes.

=== How does a TEI release happen? ===

The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw22.xml

== Working in GitHub ==

=== How do I edit the TEI Guidelines? ===

Editing the TEI Guidelines is a complex process and the Council has produced a document http://www.tei-c.org/Activities/Council/Working/tcw20.xml covering the logical and physical layout of the Guidelines, stylistic notes, how to make a change to the Guidelines (it requires [[TEI-Council-FAQ#How_do_I_use_GitHub.3F|using subversion]], building a release, and a reference section of useful information). If any information you need isn't in this document, ask on the Council list and get someone to update it!

=== How can I find out about every time a change is made in the TEI GitHub repository? ===
# Go to https://github.com/TEIC/
# Make sure you are logged in and
# go into each repository you are interested in and 'watch' them.

=== How do I use GitHub? ===
The TEI stores its working files in repositories in the [https://github.com/TEIC TEIC GitHub Organization]. See the [http://www.tei-c.org/guidelines/p5/using-the-tei-github-repository/ instructions]. Write access is reserved for those who are on the TEI Council or TEI Contributors teams. Any Council member should be able to add you to the Council team.

=== What should I put in a GitHub commit message? ===

It is beneficial to all those looking at the TEI GitHub repository if commit messages are clear and detailed. This is especially true when trying to revert changes made by yourself or others to solve problems. A good commit message will include:
* a subject line less than 72 characters long (which may be the whole message if no more is needed)
* an explanation to a useful level of detail about what you did
* a mention of why this is being done
* the GitHub issue numbers (or urls) that relate to the change if applicable
* an explanation of whether this change is completing the work described or one step towards doing so.

== TEI website ==

=== I want to add a document to add meeting minutes, reports, or working papers to the TEI-C website. How do I do that? ===

The TEI has a longstanding naming convention for files that consists of:

# a short alphabetical abbreviation for a committee (such as "tc" for "Technical Council")
# a one-letter abbreviation for minutes ("m"), reports ("r"), or working papers ("w")
# a two-digit number for the document with a committee series, numbered sequentially (e.g., "tcw01" is the first working paper from the Technical Council, "tcm05" is the fifth minutes from the Technical Council, etc.)

These documents currently reside in the [https://github.com/TEIC/Documentation Documentation] repo on GitHub.

=== How do I get access to the Google Analytics Data for www.tei-c.org? ===

Email the TEI-C webmaster: web@tei-c.org.

== Miscellaneous ==

=== Why do some elements have @type and others do not? ===

The TEI has avoided adding @type globally to elements because its availability is thought to invite tag or attribute abuse. In order for a request to add @type to an element to be considered for prolonged discussion and argument the TEI Technical Council has a standing principle that an element should be both repeatable and have obvious different classifications that apply to it. If such a request is approved then the preferred method is to make the element a member of the att.typed class (because if you can have @type, you can also have sub-types and thus need @subtype). If a closed or suggested value list, or different description is needed, this should then be provided as a local modification to the attributes inherited from att.typed.

== I have a question! ==

Then add it just above this one or email someone on the council or the council list reminding them of the existence of this wiki page when you ask your question.

[[Category:Council]]

TEI-Council-FAQ

2024-10-18T17:27:43Z

Syd: entirely re-write, as my recollection of the War on Attributes does not involve concerns of abuse mitigated by datatypes at all.

So you have some questions about how the [[Council|TEI Technical Council]] works? This page has been set up to answer questions that new council members (or other curious parties) may have.

== Overview ==

=== How does the Council do its work? ===

By every means possible. These include monthly remote meetings, email, widely circulated discussion documents, and public debate in other contexts such as TEI-L and GitHub issues. The Council meets face to face twice a year (usually one of those meetings concurrent with the TEI Annual Meeting), and many more times than that virtually. Sub-groups of Council will often form around particularly large or complex issues and may meet separately to deal with them.

=== And what work does it do? ===

You should probably review the recent official work of the Council by reading the last few sets of minutes: http://www.tei-c.org/Council/ has an index page which links to them all (when we remember to update it). The minutes record topics discussed and responsibilities allocated at the Council level. Of course many Council members are also active in subgroups (formal or informal) of the Council or SIGs, which may be documented elsewhere as well.

Generally, things in Council work like this:

# A bug report or feature request is reported by anyone at [https://github.com/TEIC/ GitHub] for the [https://github.com/TEIC/TEI/issues Guidelines] or [https://github.com/TEIC/Stylesheets/issues Stylesheets].
# Sometimes others notice the ticket and comment on it.
# Sometimes a Council member may make an executive decision on the ticket. If it's a corrigible error or bug, we can just fix it in the appropriate ODD file(s) (also in GitHub). If it is not a real issue, sometimes the ticket will just be closed. If you do not have developer access on GitHub you'll ask to be added to the Council team there. Otherwise, it's discussed either by email on the Council mailing list or at a Council meeting (conference call or in-person meeting). Comments are recorded in the ticket reflecting the decision reached, and changes are made in GitHub by a member of the Council sometime thereafter.
# The change shows up on tei-c.org after the next TEI "release", which happens about two or three times a year.

However, Council does sometimes consider lengthy proposals circulated to Council outside of GitHub and vote on them as packages, with the changes grouped together in a sensible way so they can be considered in smaller packages, or with the changes listed individually.

=== And what is its scope? ===

The Council's primary responsibility is to act as technical watchdog for the intellectual content of the TEI Guidelines. That is to say: it has the final say in just about every aspect of the TEI encoding scheme -- what elements exist in it, what they are called, how they should be used.

=== How do I join the TEI Council mailing list? ===

We have had the practice on the Council so far that elected members get added immediately to the list (and to the telecon, if there is one), with every right to participate, while outgoing members stay on until the end of their term. To join or discuss any problems using the list contact the [mailto:tei-council-owner@lists.tei-c.org TEI Council mailing list owner], currently this is Luis Meneses (Victoria). There is also a joint Board/Council mailing list to which you should be added as well.

=== Why are some people on the Council email list or attending Council meetings even though they are not on the list of elected members? ===

In addition to the members of the Council, the chair of the TEI Technical Council may invite others not elected to the Council to meetings (e.g. to speak to a particular issue). Historically the Council often invited a representative of the Board to the Council mailing list and meetings. The TEI-C Webmaster (currently Luis Meneses) are also on the mailing lists.

=== What are the various job roles on the TEI Council? ===

==== TEI Technical Council Member ====
A TEI Technical Council Member is expected to participate in all aspects of Council work. This means that they should learn how the TEI infrastructure is organised and [http://www.tei-c.org/Activities/Council/Working/tcw20.xml how to edit the TEI Guidelines], asking on the Council list any questions they might have. They will be expected to come to face-to-face ("f2f") meetings (often two per year) and participate in a couple other teleconferences per year. They will be assigned (or take) feature requests/bugs on [https://github.com/TEIC the TEI Consortium's GitHub site], for which they will be in charge of encouraging discussion, reporting on the issue to Council, and eventually implementing (or ensuring implementation) of the resulting decision. A TEI Technical Council Member is expected to participate in the maintenance and development of the TEI Guidelines and related outputs. Some elected TEI Council members focus more on particular aspects of the infrastructure or stylesheets as part of the contribution to the Council. Council members should always act to represent what they believe are the opinions and best interest of the community that has elected them.

==== TEI Technical Council Chair ====
The TEI Technical Council Chair's role is to administrate and facilitate the work of the TEI Technical Council. If all of the Council are the elected servants of the community, then the Council Chair is the servant of the servants of the TEI (''Servus servorum TEI''). The duties of the Technical Council Chair include (in no particular order):
* ensuring the delivery and maintenance of the Guidelines
* arranging for Council members to actively participate in Council activities
* arranging and chairing the face-to-face meetings (in conjunction with the local organiser)
* arranging and chairing the teleconferences
* creating agendas for those meetings, and ensuring minutes are written and posted of them
* assigning tickets in [http://github.com/TEIC/ the TEIC Github organization]
* acting as SIG coordinator
* liaising for and reporting on Council activities at all Board meetings
* reflecting Council wishes in Board discussions
* acting as a public point of contact and responding to technical enquiries (messages to council@tei-c.org are forwarded to the Council Chair)
* announcing new releases of the Guidelines on the TEI-L mailing list
* ensuring the smooth running of the TEI Technical Council

The TEI Technical Council Chair is also a member of the Council, so has all the duties and obligations of being a council member as well.

==== Release Technician ====
The TEI Guidelines release process (see [http://www.tei-c.org/Activities/Council/Working/tcw22.xml tcw22: Building a TEI Release]) involves a single individual responsible for 'pushing the button' and completing the steps required to make a TEI Guidelines release live. This is not a standing position; instead, the responsibility rotates for every release in order to demystify the release process and spread the expertise beyond Oxford staff. Although we have documented the work in quite a detailed manner, it is a non-trivial process and involves a fair degree of work. A release technician is usually required to set aside a whole day for the release process since history teaches us that often the entire process needs to be re-run to correct last-minute errors.

==== TEI-C Webmaster and Assistant Webmaster ====

The TEI-C Webmaster and Assistant Webmaster are not officially part of the Council but may be added to the mailing lists at the discretion of the Council Chair. They are responsible for the smooth running of the TEI-C Website.

=== How is the TEI Technical Council Chair elected? ===

The [http://www.tei-c.org/About/bylaws.xml#body.1_div.3_div.3 Bylaws of the TEI-C] say that:
<blockquote>
The Chair of the Technical Council shall be elected by the voting Members of the TEI-C Technical Council from its membership and shall serve as the chief technical officer of the Consortium. If no Technical Council Member is able or willing to assume the chair, the Technical Council may request the Board of Directors to second one of its elected members to the role, or it may nominate a non-elected individual.
</blockquote>
This leaves it intentionally vague as to the precise process the TEI Technical Council will follow. For now there is vague consensus that they will do something like the following. Note that timeframes below are not intended to be rigid or precise, but rather to be suggestive.
# The new Technical Council Members will be added to the tei-council (and tei-board-council) mailing lists shortly after the members' meeting. Up until around the last last Friday in November those who are Council members for next year will consider whether they want to run to be Chair of the TEI Technical Council. The current Chair will facilitate this process by answering any questions about the post. Before that date those intending to stand should send a statement of some sort to the Council mailing list detailing why they think the council members should vote for them.
# On or around the first weekday of December if only one person is running then the Chair will announce this to the tei-council mailing list as an acclamation (and after a short period for objections, to the Board and TEI-L). If multiple people are running, then the Council Chair will appoint a "returning officer" who is not a member of the incoming Council (i.e., not a voter and thus at least a somewhat disinterested party). The returning officer will set up an electronic voting system with the names of the candidates. This should be a private election with no one able to determine who has voted for whom. E.g. if using opavote.org this should have the following settings:
## Results only shown at end
## Method: "Plurality/FPTP/SNTV" for 2 candidates, "Instant Runoff Voting" for 3 or more
## a single winner
## Ballot type: "choose one" for 2 candidates, "ranked enhanced" for 3 or more
## candidate order shuffled
# The returning officer should ensure the election runs for at least 4 days, preferably in early December, after announcing it on the tei-council mailing list (and distributing ballots depending on the system).
# The results will be announced publicly on the tei-council mailing list, and Council members given a brief chance to raise any objections with the election before the current Chair informs the Board and announces it more publicly on TEI-L.
# The new Chair assumes the role on 1 January. The current chair steps down on 31 December. The outgoing and incoming chairs should co-ordinate activities between the election and 1 January so as to ensure a smooth transition. (Remembering that the current Chair might be departing off council at the end of that year.) These dates and timescales can of course shift and are not meant to be set in stone.

== Terminology ==

=== What is a "corrigible error"? ===

This is a term that comes up in Council discussions and refers to an error or inconsistency in the Guidelines that can be fixed without requiring a deprecation period.

=== What was the War on Free-text-bearing Attribute Values? ===

The move from SGML to XML included (some would say necessitated) The War on Free-text-bearing Attribute Values, also known as the War on Free-text-bearing Attributes or the War on Attributes for short. This war was an effort to disallow free text in the value of any attribute recommended by the ''Guidelines''. There were two main reasons for this.

First, XML does not have SDATA entities, and thus has no built-in mechanism for representing a character that is not available in Unicode. The obvious mechanism to represent a character outside of Unicode in XML is to use an element. In TEI, this is the <tt><g></tt> element. However, an element cannot be inside an attribute value. Thus any free text which ''might'' include a character outside of Unicode could not be properly expressed in an attribute value — it would have to be element content so it could include an element itself. (This was also the reason behind macro.xtext, which in general should be used instead of <tt>textNode</tt> in TEI content models.)

Secondly, it was observed, XML’s internal mechanism to specify language (<tt>@xml:lang</tt>) does not differentiate between an element’s attributes and its content. However, it is quite reasonable to believe (at least, in DH) that an encoding would need to specify the natural language of any free text. One way around this problem would have been to avoid <tt>@xml:lang</tt> and instead develop a TEI-specific system for specification of language that did not have this limitation. Another was to avoid allowing free text in an attribute value, such that all free text would be in element content, which element could bear an <tt>@xml:lang</tt>. TEI chose the latter.

=== What is the "Birnbaum doctrine"? ===

As expressed in [http://www.tei-c.org/Activities/Council/Working/tcw09.xml TCW09: Backward Compatibility and the Maintenance of the Text Encoding Initiative Guidelines], we should avoid breaking backward compatibility and only do so after serious consideration. It does not mean that we cannot break backwards compatibility, just that we've agreed a set of steps to take when we do so. Our deprecation policy supersedes some of this.

=== In what ways will Council break backwards compatibility? ===

For an egregious error, we might actually change a content model immediately. More often, we will survey the community on TEI-L before doing so, and we might [[Practices no longer recommended or now deprecated|deprecate]].

=== What is the "Durand Conundrum"? ===

The "Durand Conundrum" was suggested by David G. Durand concerning the TEI's decision to use the [[ODD | TEI ODD]] meta-schema language rather than just one of the existing schema languages. Given that we decided to use our own language, why use RelaxNG as part of that language for describing content models? Generally, the consensus is that [[ODD | TEI ODD]] gives us greater power and flexibility than any individual schema language can do in that we can model things that those schema languages are currently unable to cope with. TEI ODD gives the ability for a single document to produce both documentation and schema since these are inherently interlinked. It also keeps the TEI honest, in requiring it to use its own system to document schemas. [[ODD | TEI ODD]] does currently have some problems, a few of which are detailed at [[ODD-dev]] and successive revisions of TEI ODD are intended to solve some of these. Increasingly [[ODD#Future_plans:_.22Pure_ODD.22|the work on Pure ODD elements for content models and datatypes]] has cut the gordian knot of this problem.

=== What does "no magic" mean? ===

'Magic' in the sense sometimes used in Council discussion refers to pre-existing or special knowledge required to process something. For example, it was only by 'magic' that a TEI ODD processor would know to add attributes from the att.global attribute class to elements until this was changed to make all element specifications have to explicitly claim membership in this class if they wanted the global attributes. Knowing to add them was 'magic', and in general it is better if any requirements or understood knowledge is explicitly documented. While some 'magic' of understood conventions or processing will always remain in complex technical systems, the Council strives to at very least enable the possibility of documenting the underlying rules when it discovers them. James Cummings has been a fervent proponent of the removal of any understood 'magic' rules from the TEI.

=== What is a non-deterministic content model? ===

If you have a content model for <a>:

<pre>
b*, c?, b*
</pre>

and you have a document with:

<pre>
<a>
<b/>
</a>
</pre>

then a parser can't tell whether the <b/> matches the first b* or the second b* in the content model. Thus, the content model itself is called “non-deterministic”. DTDs and W3C XML Schemas reject non-deterministic content models. Thus, if we were to create one in the TEI, validation with DTD and XSD would fail due to errors ''in the schema'', regardless of whether the instance document has an occurence that is non-deterministic or not.

=== What are Janus elements? ===

These are pairs of elements that are in a sense two sides of the same coin, such as orig and reg, corr and sic, abbr and expan.

=== What does it mean to say that elements tessellate? ===

This means that all textual content is included in exactly one instance of an element. For example, once you start using divs (numbered or unnumbered), all text thereafter must be inside of one of the divs: you can't start using p elements that are not wrapped in a div.

In the Guidelines this is sometimes referred to as end-to-end segmentation.

== Meetings ==

=== Where are the minutes of previous meetings? ===

Minutes are [http://www.tei-c.org/Activities/Council/Meetings/index.xml archived on the TEI website]. Interim states of minutes may at times live in this wiki, Google Docs, or elsewhere.

=== How are the Council meetings held? ===

The Council usually makes use of Google Meet/Hangouts for their meetings. The meeting link will be in the agenda and/or sent out on the Council list before the meeting.

=== What funding is available for Council Activities? And how do I get reimbursed? ===

The TEI funds the participation of the council members in the meetings.

If the council has a meeting, then the council members' travel, hotel, etc. will be reimbursed with proper receipts. The TEI reimburses all reasonable expenses in keeping with standard practice at most universities and granting agencies. We cover meals, travel, lodging, and other common daily travel expenses. Airfare should be economy class and direct return, unless otherwise arranged with the Treasurer prior to your trip. If you have questions about reimbursement procedures, including what is reimbursable, please email Hugh Cayless, the TEI treasurer, at philomousos AT gmail.com.

Use the TEI Travel expense form available here: https://tei-c.org/tei_travel_form/ '''Expense forms should be submitted within 1 month of the end of the meeting.'''

== How we get work done ==

=== I have something to say about a GitHub Feature Request or Bug: Should I comment on the issue or the TEI Council mailing list? ===

There is no hard-and-fast policy on this. The mailing list is a better place for ongoing discussions where people are arguing back and forth during decision making. The GitHub tracker is the appropriate place to record opinions, positions, and decisions for posterity, especially if such would help a) whoever is implementing the decisions recorded in the ticket, b) anyone revisiting this decision later to retrace the thinking. The [http://lists.tei-c.org/pipermail/tei-council/ TEI Council mailing list archives] are public, so if substantial discussion has taken place there (or indeed on TEI-L), this can also be linked to from the ticket.

=== When is discussion on an element or topic "closed" and how do I know? ===

Any topic can be revisited at any point, even in the published guidelines, through posting a feature request on GitHub. Council-specific issues should be raised on the council mailing list, after having reviewed any previous discussion on the topic in the [http://lists.tei-c.org/pipermail/tei-council/ tei-council mailing list archives].

=== How can I find out about every time a ticket is created or commented on? ===

Each repository has a "watch" control, which is to be found on the top right or the repo's GitHub page, below the navigation bar. This control lets you manage notifications in various ways.

=== How are tickets assigned in GitHub? ===
All members of Council are made part of the Council Team on the GitHub TEIC Organisation and meant to take an active role in the development and maintenance of the TEI Guidelines. This means that they have write access to the TEI Guidelines Github Repository, and tickets can be assigned to them in the ticket trackers. They can also update and modify tickets. This means that Council members are free to 'take' tickets which they wish to oversee. Other Council members can also 'give' tickets to each other if they think someone particularly suited to overseeing a particular ticket. (However, usually they should have the Council member's permission to do so.) On a regular basis the Council Chair will assign tickets to Council members, if a ticket gets assigned to them that they don't want to do they should tell the Chair and/or ask other Council members to swap.

=== What do the issue labels mean? ===

* '<span style="color:red; font-weight:bold;">Status: Blocked</span>' means that the issue cannot be progressed because it requires either that another issue be completed first or that more information is needed from the reporter or a third party.

* '<span style="color:orange; font-weight:bold;">Status: Needs Discussion</span>' means that the issue has not been talked about enough yet to resolve it. New issues nearly always go into this status first. When Council has face-to-face meetings, these are usually the issues we target first.

* '<span style="color:green; font-weight:bold;">Status: Go</span>' means that the ticket has been discussed, there is general consensus on what the correct thing to do is, and it has been assigned for someone to ensure its implementation.

* Other labels should be self-explanatory, and are sometimes created as needed to group tickets for various purposes.

=== How does a TEI release happen? ===

The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw22.xml

== Working in GitHub ==

=== How do I edit the TEI Guidelines? ===

Editing the TEI Guidelines is a complex process and the Council has produced a document http://www.tei-c.org/Activities/Council/Working/tcw20.xml covering the logical and physical layout of the Guidelines, stylistic notes, how to make a change to the Guidelines (it requires [[TEI-Council-FAQ#How_do_I_use_GitHub.3F|using subversion]], building a release, and a reference section of useful information). If any information you need isn't in this document, ask on the Council list and get someone to update it!

=== How can I find out about every time a change is made in the TEI GitHub repository? ===
# Go to https://github.com/TEIC/
# Make sure you are logged in and
# go into each repository you are interested in and 'watch' them.

=== How do I use GitHub? ===
The TEI stores its working files in repositories in the [https://github.com/TEIC TEIC GitHub Organization]. See the [http://www.tei-c.org/guidelines/p5/using-the-tei-github-repository/ instructions]. Write access is reserved for those who are on the TEI Council or TEI Contributors teams. Any Council member should be able to add you to the Council team.

=== What should I put in a GitHub commit message? ===

It is beneficial to all those looking at the TEI GitHub repository if commit messages are clear and detailed. This is especially true when trying to revert changes made by yourself or others to solve problems. A good commit message will include:
* a subject line less than 72 characters long (which may be the whole message if no more is needed)
* an explanation to a useful level of detail about what you did
* a mention of why this is being done
* the GitHub issue numbers (or urls) that relate to the change if applicable
* an explanation of whether this change is completing the work described or one step towards doing so.

== TEI website ==

=== I want to add a document to add meeting minutes, reports, or working papers to the TEI-C website. How do I do that? ===

The TEI has a longstanding naming convention for files that consists of:

# a short alphabetical abbreviation for a committee (such as "tc" for "Technical Council")
# a one-letter abbreviation for minutes ("m"), reports ("r"), or working papers ("w")
# a two-digit number for the document with a committee series, numbered sequentially (e.g., "tcw01" is the first working paper from the Technical Council, "tcm05" is the fifth minutes from the Technical Council, etc.)

These documents currently reside in the [https://github.com/TEIC/Documentation Documentation] repo on GitHub.

=== How do I get access to the Google Analytics Data for www.tei-c.org? ===

Email the TEI-C webmaster: web@tei-c.org.

== Miscellaneous ==

=== Why do some elements have @type and others do not? ===

The TEI has avoided adding @type globally to elements because its availability is thought to invite tag or attribute abuse. In order for a request to add @type to an element to be considered for prolonged discussion and argument the TEI Technical Council has a standing principle that an element should be both repeatable and have obvious different classifications that apply to it. If such a request is approved then the preferred method is to make the element a member of the att.typed class (because if you can have @type, you can also have sub-types and thus need @subtype). If a closed or suggested value list, or different description is needed, this should then be provided as a local modification to the attributes inherited from att.typed.

== I have a question! ==

Then add it just above this one or email someone on the council or the council list reminding them of the existence of this wiki page when you ask your question.

[[Category:Council]]

New ODD processing

2021-11-01T15:52:58Z

Syd:

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Eventually to reside in TEI/TEIC/ repo, but development will be on a fork of said repo (this will allow us to frequently merge in changes from TEIC/TEI/, but to stay out of everyone’s way)
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* We agree we would prefer to rely on XSLT 3 maps as opposed to XSLT 1 keys, re-visiting this decision if maps turn out to be problematic (i.e., too slow)
* In order to make running XSpec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well
* Processing of a customization ODD (whether initial or chained) is to generate an XSLT program from it that gets run against P5(subset)

=== plans ===
Not ''necessarily'' in this order, but it is a reasonable one.
# Nail down the rules for PureODD
# Nail down the subset of TEI that we plan to process (by tangling into RELAX NG and weaving into XHTML 5) by creating a new ODD, or by modifying p5odds.odd.
# Agree upon and document XSLT coding conventions. Keep this in a live document to be updated PRN.
# Re-write generation of p5subset, likely relying heavily on existing code

[[Category:New ODD Processing]]

New ODD processing

2021-10-30T17:54:31Z

Syd: /* plans */

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Eventually to reside in TEI/TEIC/ repo, but development will be on a fork of said repo (this will allow us to frequently merge in changes from TEIC/TEI/, but to stay out of everyone’s way)
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* In order to make running XSpec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well
* Processing of a customization ODD (whether initial or chained) is to generate an XSLT program from it that gets run against P5(subset)

=== plans ===
Not ''necessarily'' in this order, but it is a reasonable one.
# Nail down the rules for PureODD
# Nail down the subset of TEI that we plan to process (by tangling into RELAX NG and weaving into XHTML 5) by creating a new ODD, or by modifying p5odds.odd.
# Agree upon and document XSLT coding conventions. Keep this in a live document to be updated PRN.
# Re-write generation of p5subset, likely relying heavily on existing code

[[Category:New ODD Processing]]

New ODD processing

2021-08-27T16:34:55Z

Syd: /* goals */

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Eventually to reside in TEI/TEIC/ repo, but development will be on a fork of said repo (this will allow us to frequently merge in changes from TEIC/TEI/, but to stay out of everyone’s way)
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* In order to make running XSpec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well
* Processing of a customization ODD (whether initial or chained) is to generate an XSLT program from it that gets run against P5(subset)

=== plans ===
* Do want to re-write generation of p5subset, but we may rely heavily on existing code
* Step 0: nail down the rules for PureODD

[[Category:New ODD Processing]]

New ODD processing

2021-08-27T16:18:17Z

Syd: /* goals */

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Resides in TEI/TEIC/ repo
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* In order to make running XSpec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well
* Processing of a customization ODD (whether initial or chained) is to generate an XSLT program from it that gets run against P5(subset)

=== plans ===
* Do want to re-write generation of p5subset, but we may rely heavily on existing code
* Step 0: nail down the rules for PureODD

[[Category:New ODD Processing]]

New ODD processing

2021-08-27T16:12:33Z

Syd:

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Resides in TEI/TEIC/ repo
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* In order to make running XSPec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well
* Processing of a customization ODD (whether initial or chained) is to generate an XSLT program from it that gets run against P5(subset)

=== plans ===
* Do want to re-write generation of p5subset, but we may rely heavily on existing code
* Step 0: nail down the rules for PureODD

[[Category:New ODD Processing]]

New ODD processing

2021-08-27T16:10:10Z

Syd:

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new PureODD processor.

=== goals ===

We are planning a re-write of current Stylesheets aimed solely at converting ODD to the Guidelines, schemas, and customization ODDs into schemas and customized output.
Thoughts, in no particular order:
* Written in XSLT 3, only
* Resides in TEI/TEIC/ repo
* Driven by <tt>ant</tt>, with the hope, but not requirement, that it will run in Windows (requirement that it runs in oXygen)
* Probably best to build an oXygen plug-in as we go (or at least as soon as there is a transform that works)
* No support for DTDs
* Support for Schematron (ISO or the new community Schematron, but not both) via putting rules into RELAX NG, then extracting to separate .sch file from there
* Plan to use HTML5, rather than a bastardized TEI_Lite, as intermediate stage
* Well documented (using xd: elements and comments — at least partially enforced by Schematron), using consistent naming conventions, typed variables, etc.
* Probably a good idea to have a single “coding conventions” document that discusses these issues, and perhaps some Schematron to enforce them.
* SB thinks we should lean away from iterations and “loops”, preferring apply-templates; MH less strong on this point
* MH prefers functions over named templates; SB less strong on this point
* In order to make running XSPec easier, functions and named templates should be in separate library files
* We want to support chained ODDs right from the start
* Generate a test suite (including of chaining) as we go
* We are still debating whether to support PureODD only, or RELAX NG inside <content> as well.

=== plans ===
* Do want to re-write generation of p5subset, but we may rely heavily on existing code
* Step 0: nail down the rules for PureODD

[[Category:New ODD Processing]]

New ODD processing

2021-08-27T15:40:23Z

Syd: Created page with "This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new ODD processor. Category:New ODD Processing"

This page is where Syd Bauman, Martin Holmes, and others are keeping notes on their plans for building a new ODD processor.

[[Category:New ODD Processing]]

Travel Reimbursement Procedures for Council and Board Members

2018-03-06T21:53:41Z

Syd: /* An example */ correx typo

=Reimbursement Policies and Procedures=

* [http://www.tei-c.org/Admin/TEI_travel_form.pdf TEI-C Travel Reimbursement Form]

----

The TEI Consortium (TEI-C) is a volunteer-run organization that represents a community that continues to grow in numbers and geographic representation. In order to function smoothly and continue its outreach, the TEI-C compensates individuals for travel for TEI-related business. For example, the TEI-C will reimburse keynotes or other invited speakers to annual conferences and Council and Board members for face-to-face meetings. Travel reimbursement requests outside of the norm are at the discretion of the TEI-C Board of Directors.

The TEI-C will reimburse Board-approved travel for '''reasonable expenses''', which includes economy airfare, conference-designated lodging (or cheaper!), and '''75% of the per diem''' designated by the U.S. Department of State [Domestic https://www.gsa.gov/travel/plan-book/per-diem-rates] and [Foreign https://aoprals.state.gov/web920/per_diem.asp] Per Diem Rates. Expenses incurred beyond what is reasonable will be evaluated for additional compensation on a case by case basis.

The TEI-C appreciates travel expenses covered by an individual's institution as part of the institutions's overall commitment to the TEI. Likewise, the TEI-C appreciates individuals who offset or cover in-full their own travel expenses for TEI-related business. We encourage an individual's ability to subsidize or cover completely the costs associated with TEI-C-related business travel.

In broad terms, its reimbursement policies are in keeping with those common practice in the U.S. University and Public Sector. Questions about these policies or concerning expenses not covered here should be directed to the Treasurer. While exceptions and clarifications are possible, these should normally be requested before the expense is incurred.

'''Receipts for all travel-related transactions with the exceptions of food-related receipts must be submitted for reimbursement.'''

Specific guidelines for allowable expenses are described below.

==Transportation to TEI-C Events and Activities==

Airfare should be by the cheapest direct route and economy class or equivalent. Ground transportation should be by cheapest direct route and economy/second class (if applicable) or equivalent. Transportation involving detours, stop-overs, or travel to additional destinations may be eligible for full or partial reimbursement. Individuals considering such travel should make arrangements with the Treasurer in advance.

The TEI-C will reimburse expenses related to traveling to/from an airport including airport parking and transportation to/from airports. We ask that you find the most economical form of long-term airport parking as well as economical transportation to/from airports, which may include sharing a taxi with colleagues. The TEI-C will also reimburse transportation expenses from lodging to meeting locations (over $20). Most in-town commuting will be covered by the "Incidental Expenses" portion of the per diem (see below). We ask that you find the most economical form of in-town commuting, which may include multi-day transit passes or taxi-sharing.

==Meals and Incidental Expenses (Per Diem)==

The TEI reimburses eligible individuals for meals and incidental expenses on a per diem basis. These per diem rates usually are calculated from U.S. Government rates using the following formula:

===Travel outside the U.S.===
For travel outside the continental U.S., the Meals and Incidentals per diem is equal to 75% of the [https://aoprals.state.gov/web920/per_diem.asp relevant U.S. State Department rate].

===Travel within the U.S ===

For travel withing the continental U.S., the Meals and Incidentals per diem is equal to the [https://www.gsa.gov/travel/plan-book/per-diem-rates relevant U.S. General Service Administration rate] rounded up to the nearest $10.

To ease reporting, per diem claim for meals and incidentals are calculated separately. The allowance for incidentals is 20% of the total TEI per diem; the allowance for meals is 80% of the total TEI per diem. The Board reserves the right to set its per diem rates using a different formula provided advance notice is given to the traveller.

===Eligible Per Diem Expenses===

The per diem rates are intended to cover actual meals and incidental daily living expenses (excluding lodging) for eligible individuals while they are travelling on TEI business. Per diems should not be claimed for expenses that are paid for by somebody else, eligible for reimbursement from other sources, or that occur before or after the travel takes place. '''No receipts are required for expenses claimed as part of a per diem.'''

The following are some examples of expenses covered by the Meals and Incidental per diem. The list is not intended to be exhaustive. If in doubt, please contact the Treasurer.

====Meals====
The per diem is intended to cover all meals paid for by individuals on their own behalf. No receipts are required in such cases. Reimbursement for group meals organised in advance by the TEI or local hosts or for costs incurred in paying for meals of guests of the TEI should be requested separately and require receipts. Individuals participating (but not paying for) such meals should not also claim the equivalent meal allowance. Informal groups dining together should ask for separate checks or otherwise settle the bill amongst themselves before claiming their per diems as individuals. Individuals will not normally be reimbursed for group meals not arranged in advance.

====Incidental Expenses====
The per diem is also intended to cover incidental and minor expenses such as tips, in-town taxi and public transit fares (under $20), and the like. Reimbursement for ground transportation above $20 should be requested separately (with receipts).

==Calculating your reimbursement==

Individuals calculate their per diem allowances on the basis of the number of mornings, afternoons, and evenings they were away from home while engaged on TEI business:

* Incidental per diem Claim: an allowance for every morning, afternoon, and/or evening you were away from home while engaged on TEI business. No receipts are required to claim this allowance. If only part of the day was spent away from home on TEI business please do not claim for those parts when you were at home. For example, if you arrive home from a meeting in time for dinner, you should claim an incidentals per diem that day for only the morning and afternoon.

* Meals per diem Claim: an allowance for every morning, afternoon, and evening meal that was not paid for by somebody else. No receipts are required to claim this allowance. If you attended banquet or similarly formal meal arranged and paid for somebody else, you should not also request a per diem allowance for the same meal. If you share a restaurant meal with some colleagues more informally, you should settle the bill amongst yourselves (or ask for separate cheques) and request your individual per diem allowance. The TEI no longer reimburses individuals for group meals without prior notice.

You can calculate your per diem allowance using the following tables. In these tables, ‘rate’ refers to the maximum per diem for the relevant type of expense as determined by the TEI. If an official rate has not been published, you should use the formulas discussed above. Otherwise, use the published rate.

===Incidental Allowances===

Claim incidental expenses for each morning, afternoon, and evening you were engaged on TEI business away from home.

{| class="wikitable"
|-
! Part of day
! Number of eligible periods
! Rate
! Total allowance
|-
| Morning
| __ ⨉
| [5% of total TEI per diem]
| = __
|-
| Afternoon
| __ ⨉
| [7% of total TEI per diem]
| = __
|-
| Evening
| __ ⨉
| [8% of total TEI per diem]
| = __
|-
| Total Incidental Allowance
| __
|
|
|}

===Meals===

Claim a meal allowance for each meal not purchased for you by somebody else or reimbursable from other sources while you were away from home on TEI business:

{| class="wikitable"
|-
! Meal Period
! Number of eligible meals
! Rate
! Total allowance
|-
| Breakfast (morning)
| __ ⨉
| [20% of total TEI per diem]
| = __
|-
| Lunch (afternoon)
| __ ⨉
| [28% of total TEI per diem]
| = __
|-
| Dinner (evening)
| __ ⨉
| [32% of total TEI per diem]
| = __
|-
| Total Meals Allowance
| __
|
|
|}

====An example====

A Council member attends a three day Council meeting in Singapore from April 1-3. She leaves home on March 31st in the afternoon and returns home from the meeting just before midnight on April 4. While at the conference she attends a previously arranged dinner with the entire council on April 3 and banquet hosted by the meeting's local hosts on April 1.

The U.S. State Department meals and incidental rate for Singapore that year is $110 USD. The TEI-C therefore sets its total per diem rate at $82.50 USD/day (75% of $110 USD) and publishes the following breakdown:

{| class="wikitable"
|-
! Period of Day
! Incidental Allowance
! Meals Allowance
|-
| Morning
| $3.85
| $15.40
|-
| Afternoon
| $5.39
| $21.56
|-
| Evening
| $6.16
| $26.95
|}

In asking for reinbursement for incidentals, the Council member claims a per diem allowance for every morning, afternoon, and evening she was away from home on TEI business: in this case four mornings (from April 1-4), five afternoons (March 31-April 4), and five evenings (March 31-April4). She claims four mornings, because she did not leave home until the afternoon of March 31st. She claims five afternoons and evenings because she was travelling on TEI business from the afternoon of March 31st until well into the evening of April 4.

{| class="wikitable"
|-
! Period of Day
! Number of eligible periods
! Rate
! Total allowance
|-
| Morning
| 4 x
| $3.85 =
| $15.40
|-
| Afternoon
| 5 x
| $5.39 =
| $26.95
|-
| Evening
| 5 x
| $6.16 =
| $30.80
|-
|
|
| Total Incidental Allowance:
| $73.15
|}

In asking for reimbursement for meals, the Council member claims a per diem allowance for meals while she was away from home on TEI business, excepting meals paid for by others or reimbursed from other sources. In this case that means she claims for four breakfasts (April 1-4) and five lunches (March 31-April 4), but, since two of her evening meals were paid for, only three dinners (March 31, April 2, and April 4).

{| class="wikitable"
|-
! Meal Period
! Number of eligible meals
! Rate
! Total allowance
|-
| Breakfast (morning)
| 4 x
| $15.40 =
| $61.60
|-
| Lunch (afternoon)
| 5 x
| $21.56 =
| $107.80
|-
| Dinner (evening)
| 3 x
| $26.95 =
| $80.85
|-
|
|
| Total Meals Allowance:
| $250.25
|}

===Lodging===

The TEI-C will reimburse eligible individuals for reasonable actual hotel and lodging costs for stays necessitated by TEI meetings. In addition to board for a single individual, these costs may include internet access but not entertainment, newspapers, the use of a mini-bar, or meals (meals are reimbursed on a per diem basis). No other charges are permitted without prior arrangement. Such claims must be accompanied by receipts.

In reimbursing for such costs the TEI-C will '''pay for a maximum of one additional night before and/or after the event or activity'''. Individuals may exceed this maximum of the additional night(s) can be justified as a way of reducing the overall cost of the trip (e.g., when a Saturday overnight reduces the airfare more than the cost of the added hotel stay). Individuals considering such an arrangement should contact the Treasurer before booking their stay whenever possible.

Individuals sharing a room with friends or family not paticipating in TEI-C business should make separate arrangements with the Treasurer if the additional occupant results in extra costs being levied by the hotel. There is no need to make separate arrangements if the hotel in question charges by the room rather than number of occupants.

==Reimbursement procedure==

In order to be reimbursed a traveler should fill out a [http://www.tei-c.org/Admin/TEI_travel_form.pdf TEI-C Travel Reimbursement Form] and send it to the treasurer at the address indicated on the form '''within 1 month of travel'''. Hotel, airfare, and other significant transportation related receipts should be sent with the form. Receipts for meals and incidentals should not be included.

[[Category:Board]]

Render2selector.xslt

2017-08-24T19:40:12Z

Syd:

= Warning =

'''This page is vestigal'''. The ''new home'' for these programs is in the [https://github.com/NEU-DSG/wwp-public-code-share/tree/master/data_curation/TEI_P5_2.8.0_to_2.9.1_default_rendition WWP code sharing repository]

= Introduction =
Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no need to have two of them, the reason for separation is purely pedagogical. The first stylesheet exists to show how easy this conversion can be in the simple case. For a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace this is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

== Caveats ==

1. The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

2. The first version will delete any existing <tt>@selector</tt> attributes, so '''do not''' run it on files that already use the new mechanism.

3. The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Render2selector.xslt

2017-05-26T20:21:06Z

Syd:

= Note: =

This page is vestigal. The new home for these programs is in the [https://github.com/NEU-DSG/wwp-public-code-share/tree/master/data_curation/TEI_P5_2.8.0_to_2.9.1_default_rendition WWP code sharing repository]

= Introduction =
Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no need to have two of them, the reason for separation is purely pedagogical. The first stylesheet exists to show how easy this conversion can be in the simple case. For a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace this is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

== WARNINGS ==

1. The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

2. The first version will delete any existing <tt>@selector</tt> attributes, so '''do not''' run it on files that already use the new mechanism.

3. The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Render2selector.xslt

2017-05-23T15:28:31Z

Syd: improve wording in the prose introduction

Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no need to have two of them, the reason for separation is purely pedagogical. The first stylesheet exists to show how easy this conversion can be in the simple case. For a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace this is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

== WARNINGS ==

1. The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

2. The first version will delete any existing <tt>@selector</tt> attributes, so '''do not''' run it on files that already use the new mechanism.

3. The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Render2selector.xslt

2017-04-26T22:47:34Z

Syd: copyleft DSG, not just WWP

Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no use reason to have two of them, the reason for separation is purely pedagogical. Doing this conversion on a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

== WARNINGS ==

1. The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

2. The first version will delete any existing <tt>@selector</tt> attributes, so '''do not''' run it on files that already use the new mechanism.

3. The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Render2selector.xslt

2017-04-26T22:40:01Z

Syd: added another caveat

Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no use reason to have two of them, the reason for separation is purely pedagogical. Doing this conversion on a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

== WARNINGS ==

1. The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

2. The first version will delete any existing <tt>@selector</tt> attributes, so '''do not''' run it on files that already use the new mechanism.

3. The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Render2selector.xslt

2017-04-26T22:35:22Z

Syd: initial creation

Some time ago the TEI-C created a new mechanism for indicating default rendition. It (the new <tt>@selector</tt> mechanism) became available in 2.9.1, and the old (<tt>@render</tt>) mechanism will be withdrawn in the next release (probably 3.2.0 in a month or so).

Here are two routines for converting from the old to the new. There is no use reason to have two of them, the reason for separation is purely pedagogical. Doing this conversion on a simple TEI file that has a single <tt><TEI></tt> element and only has default renditions for elements in the TEI namespace is ''really easy''. It only takes 2 templates (in addition to the identity transform): 1 to add <tt>@selector</tt> to <tt><rendition></tt> and another to delete <tt>namespace</tt>.

Doing this for the general case, in which there may be multiple <tt><TEI></tt> elements, each with multiple <tt><namespace></tt> elements (from various namespaces), which namespaces may or may not also be in scope turns out to be ''very hard'' (IMHO), and even then I had to concede the point that there may be a prefix definition used somewhere in the file that we can’t find.

So I have left the simple version in for those who want to puzzle through what it does and how it does it. I have left the second, more complicated version in for general use, and for XSLT programmers to puzzle through and improve.

WARNING: The first version deletes <tt><namespace></tt> without checking to see if there is useful information in there or not. The more complex version is smarter about this. If you do not have any prose, but just counts and counts-with-ID in your <tt><namespace></tt>, you can easily re-generate it using [[Generate_tagsDecl_P5.xslt]]. If you actually have useful content in any of your <tt><tagUsage></tt> elements, '''do not''' use the first version.

NB: The second version tries to take into account that an <tt>@xml:id</tt> or <tt>@gi</tt> may have whitespace around the value; the first version does not.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0" version="2.0">

<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>

<xsl:template match="namespace"/>

<xsl:template match="rendition">
<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:variable name="id" select="concat('#', normalize-space( @xml:id ) )"/>
<xsl:value-of select="string-join( ../namespace/tagUsage[@render eq $id]/@gi, ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

----------
above: simple version, easy to read

below: works on more complex files
----------

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="#all"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xpath-default-namespace="http://www.tei-c.org/ns/1.0"
xmlns="http://www.tei-c.org/ns/1.0"
version="2.0">



<xsl:key name="namespace_elements" match="/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>
<xsl:key name="namespace_elements" match="/teiCorpus/TEI/teiHeader/encodingDesc/tagsDecl/namespace" use="true()"/>


<xsl:variable name="NSs" as="element()+">
<xsl:variable name="me" select="key('namespace_elements', true() )[1]"/>
<xsl:for-each select="in-scope-prefixes($me)">
<sch:ns prefix="{.}" uri="{namespace-uri-for-prefix(.,$me)}"/>
</xsl:for-each>
</xsl:variable>


<xsl:template match="node()">
<xsl:if test="not(ancestor::*)">
<xsl:text>&#x0A;</xsl:text>
</xsl:if>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*">
<xsl:copy/>
</xsl:template>


<xsl:template match="namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]"/>

<xsl:template match="text()[ preceding-sibling::*[1][self::namespace[not(tagUage/@occurs | tagUsage/@withId | tagUsage/text()[not(normalize-space(.) eq '')])]]]"/>


<xsl:template match="rendition[@xml:id][not(@selector)]">

<xsl:variable name="idrf" select="concat('#', normalize-space(@xml:id))"/>

<xsl:variable name="TEI_gis" as="item()*"
select="key('namespace_elements', true() )[normalize-space(@name) eq 'http://www.tei-c.org/ns/1.0']/tagUsage[normalize-space(@render) eq $idrf]/@gi/normalize-space()"/>

<xsl:variable name="other_gis" as="item()*">
<xsl:for-each select="key('namespace_elements', true() )[normalize-space(@name) ne 'http://www.tei-c.org/ns/1.0']">
<xsl:variable name="nsuri" select="normalize-space(@name)"/>
<xsl:for-each select="tagUsage[normalize-space(@render) eq $idrf]">

<xsl:variable name="prefix">
<xsl:choose>
<xsl:when test="($NSs)[@uri eq $nsuri]">

<xsl:value-of select="($NSs)[@uri eq $nsuri][1]/@prefix"/>
</xsl:when>
<xsl:otherwise>
<xsl:variable name="temp_prefix" select="concat('ns', parent::namespace/count( preceding::namespace ) )"/>
<xsl:message>Warning: using prefix '<xsl:value-of
select="$temp_prefix"/>' for namespace URI <xsl:value-of
select="$nsuri"/></xsl:message>
<xsl:value-of select="$temp_prefix"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>

<xsl:value-of select="concat( $prefix, '|', normalize-space( @gi ) )"/>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>

<xsl:copy>
<xsl:apply-templates select="@*"/>

<xsl:attribute name="selector">
<xsl:value-of select="string-join( distinct-values( ( $TEI_gis, $other_gis ) ), ', ')"/>
</xsl:attribute>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="rendition[@selector]">
<xsl:message>This <rendition> (#<xsl:value-of
select="
if (@xml:id) then
@xml:id
else
count(preceding::rendition) + 1"
/>) already has a @selector, so I'm not going to mess with it.
(Are you sure you should be running render2selector on this file?)</xsl:message>
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>

[[Category:XSLT]]

Recommended Practices

2017-03-10T18:50:59Z

Syd:

[[Category:SIG:Scholarly Publishing]]
==Introduction==

''This is an interesting document, but who are its authors, and for whom are its recommendations made? And is there an ODD associated with it?'' --[[User:LouBurnard|LouBurnard]] 09:36, 3 March 2011 (EST)

: As in the page history, it was written by [[User:Reedkm|Reedkm]], who I happen to know to be Kenneth Reed, formerly the convenor of the SIG on Scholarly Publishing. He meant it as the basis for a Customization to be developed by the SIG, as mentioned in a message to the SIG's email list. I'm unsure of whether an ODD exists in any form. ([[User:Kshawkin|Kshawkin]] 17:51, 11 September 2012 (EDT))

This document describes the specifications for the encoding of textual matter in accordance with the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]

We will be using the following modules as part of our schema:

* core
* header
* textstructure
* figures
* linking
* analysis
* tagdocs
* namesdates
* textcrit
* verse
* transcr

This is a working document and as such assumes that further explication will be added as the need arises. Not every element nor attribute has been covered in this document, and the TEI online documentation should be able to assist in clarification. When in doubt, the authors of this document will provide updates to ensure best practices.

== Unicode Characters ==
XML documents following these recommended practices should be stored in UTF-8 format. All non-ASCII characters should either be stored using the appropriate Unicode character or a hexadecimal entity reference to the character. Entity references are especially useful in cases of ambiguity, where a character is easily confused with another when viewed in the font in use in the XML editor.

Do not use decimal entity references or mnemonic entity references. The only allowed mnemonic entity references are the five reserved XML entities:

quot (double quotation mark)

amp (ampersand)

apos (apostrophe)

lt (less-than sign)

gt (greater-than sign)

= TEI Structure =
The structure of a XML document based on the TEI schema is as follows:

<pre>
<TEI>
<teiHeader>
[ TEI Header information ]
</teiHeader>
<text>
<front>
[ front matter ... ]
</front>
<body>
[ body of text ... ]
</body>
<back>
[ back matter ... ]
</back>
</text>
</TEI>
</pre>

== <tt><TEI></tt>: Root element ==
The root element is <tt><TEI></tt> with the namespace declaration and the xml:id of the particular book. The xml:id is format has the uncp prefix, then the book ISBN, and then the book suffix to show that it is the complete title. Please refer to section 4.2 for further discussion on xml:id.

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="uncp-9780807845295-book">
</pre>

= <tt><teiHeader></tt> =
The header element has four distinct parts:

<pre>
<fileDesc>
<encodingDesc>
<profileDesc>
<revisionDesc> </pre>

== <tt><fileDesc></tt> ==
The <tt><fileDesc></tt> element is mandatory. It contains a full bibliographic description of the ﬁle with the following elements, as well as the book abstract and keywords.

<tt><titleStmt></tt> groups information about the title of a work and those responsible for its intellectual content. This is further broken down into the following elements:

<tt><title></tt> with attributes for main and subtitle

<tt><author></tt> includes the following elements:

<pre>
<name xml:id="surnamePlusInitialForename">
<forename type="given">
<forename type="middle">
<surname>
</pre>

<tt><reg></tt> regularized author name: surname, forename type="given", forename type="middle".

<tt><editionStmt></tt> groups information relating to one edition of a text. This can include the following elements:

<pre>
<edition>
<date>
<respStmt>
</pre>

<tt><extent></tt> describes the approximate size of the electronic text as stored on some carrier medium, speciﬁed in any convenient units.

<tt><publicationStmt></tt> groups information concerning the publication or distribution of an electronic or other text.

<pre>
<publisher>
<distributor>
<pubPlace>
<address>
<idno>
</pre>

<tt><seriesStmt></tt> groups information about the series, if any, to which a publication belongs.

<tt><notesStmt></tt> collects together the book abstract and keywords.

<tt><sourceDesc></tt> supplies a bibliographic description of the copy text(s) from which an electronic text was derived or generated.

=== <tt><fileDesc></tt> Example ===
<pre>
<fileDesc>
<titleStmt>
<title type="main">A Stone of Hope</title>
<title type="sub">Prophetic Religion and The Death of Jim Crow</title>
<author xml:id="chappelld">
<name><forename type="given">David</forename>
<forename type="middle">L.</forename>
<surname>Chappell</surname>
</name>
<reg>Chappell, David L.</reg>
</author>
<respStmt>
<resp>Text encoder:</resp>
<name type="corporate">cM</name>
</respStmt>
</titleStmt>
<extent>1.4 MB</extent>
<publicationStmt>
<publisher>The University of North Carolina Press</publisher>
<pubPlace>Chapel Hill, NC</pubPlace>
<date>2004</date>
<idno type="ISBN">9780807828199</idno>
<idno type="DOI">10.5149/uncp/9780807828199</idno>
<availability xml:id="notCleared" status="restricted">
<p>This image has not been cleared for online publication.</p>
</availability>
</publicationStmt>
<sourceDesc>
<biblFull>
<titleStmt>
<title type="main">A Stone of Hope</title>
<title type="sub">Prophetic Religion and The Death of Jim Crow</title>
<author>
<ptr target="#chappelld"/></author>
</titleStmt>
<extent>360 pp., 6.125 x 9.25, 24 illus., appends., notes, bibl., index</extent>
<publicationStmt>
<publisher>The University of North Carolina Press</publisher>
<pubPlace>Chapel Hill, NC</pubPlace>
<date>2004</date>
<idno type="ISBN">9780807828199</idno>
</publicationStmt>
<notesStmt>
<note type="abstract">
<p>In this new assessment of the civil rights movement, David Chappell argues that its success was not due to the triumph of liberal ideas after decades of gradual progress, but to the tradition of prophetic religion that brought the vitality of a religious revival to the integrationist cause. Although segregationists outvoted and outgunned black integrationists, the segregationists lost, Chappell concludes, largely because they did not have a religious commitment to their cause and because they did not have support in their white southern religious denominations.</p>
</note>
</notesStmt>
</biblFull>
</sourceDesc>
</fileDesc>
</pre>

== <tt><encodingDesc></tt> ==
Documents the relationship between an electronic text and the source(s) from which it was derived.

=== <tt><encodingDesc></tt> Example ===
<pre>
<encodingDesc>
<projectDesc>
<p>The electronic edition is part of the <emph>Long Civil Rights Movement</emph> digitization project, a collaboration between UNC-Chapel Hill and the University of North Carolina Press.</p>
</projectDesc>
<editorialDecl>
<p>The text has been encoded using the recommendations for TEI P5.</p>
<p>Any hyphens occurring in line breaks have been removed, and the trailing part of a word has been joined to the preceding line.</p>
<p>All special characters have been transcribed as Unicode characters, except for the five reserved XML entities.</p>
<p>Indentation in lines has not been preserved.</p>
</editorialDecl>
<classDecl>
<taxonomy>
<bibl>
<title>Library of Congress Cataloging-in-Publication Data</title>
</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
</pre>

== <tt><profileDesc></tt> ==
Provides a detailed description of non-bibliographic aspects of the text, speciﬁcally the languages and sublanguages used, the situation in which it was produced, the participants and their setting. Keywords will be listed in this section as well.

=== <tt><profileDesc></tt> Example ===
<pre>
<profileDesc>
<langUsage>
<language ident="a" xml:lang="eng">English</language>
<language ident="a" xml:lang="lat">Latin</language>
</langUsage>
<textClass>
<classCode scheme="http://purl.org/eprint/type">Book</classCode>
<keywords scheme="LCSH">
<list type="simple">
<item>African Americans--Civil rights--History--20th century.</item>
<item>African Americans--Segregation--History--20th century.</item>
<item>Civil rights movements--United States--History--20th century.</item>
<item>Civil rights workers--Religious life--United States--History--20th century.</item>
<item>Civil rights--United States--Religious aspects--Christianity--History--20th century.</item>
<item>Christianity and politics--United States--History--20th century.</item>
<item>Church and social problems--United States--History--20th century.</item>
<item>United States--Race relations.</item>
<item>United States--Church history--20th century.</item>
</list>
</keywords>
<keywords scheme="UNCP">
<list type="simple">
<item>civil rights movement</item>
<item>prejudice</item>
<item>Martin Luther King Jr.</item>
<item>Fannie Lou Hamer</item>
<item>segregation</item>
<item>Protestantism</item>
<item>Jim Crow</item>
<item>revivalism</item>
<item>African American</item>
</list>
</keywords>
</textClass>
</profileDesc>
</pre>

== <tt><revisionDesc></tt> ==
Summarizes the revision history for a document.

=== <tt><revisionDesc></tt> Example ===
<pre>
<revisionDesc>
<change>
<date>2009-12-09</date>
<name>codeMantra</name>
</change>
<change>
<date>2010-01-04</date>
<name>Kenneth Reed</name>
<affiliation>The University of North Carolina Press</affiliation>
</change>
</revisionDesc>
</pre>

= <tt><text></tt> =
The <tt><teiHeader></tt> is followed directly by the mandatory <tt><text></tt> element, which contains the textual matter being encoded. The <tt><text></tt> element is broken down into three subelements: <tt><front></tt> for frontmatter, <tt><body></tt> for the main body of the work, and <tt><back></tt> for backmatter. Only the <tt><body></tt> element is required. Additionally, groups of discrete texts can be packaged together in one document using the <tt><group></tt> element as a parent for the separate <tt><text></tt> elements.

== <tt><div></tt> ==
The <tt><front></tt>, <tt><body></tt>, and <tt><back></tt> elements all use the nested <tt><div></tt> structure to organize primary sections as well as child sections. The <tt><div></tt> elements are identified by a unique xml:id, and also have an n attribute to aid in reference.

A type attribute is also used to describe the kind of division. Type includes the following values:

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Value'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Description'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| copyright
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| copyright information

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dedication
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dedication

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| series
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| series page

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| contents
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| table of contents

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| frontispiece
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| frontispiece

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| acknowledgments
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| acknowledgments

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| contributors
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| list of contributors

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| illustrations
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| list of illustrations

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| preface
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| preface

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| foreword
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| foreword

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| introduction
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| frontmatter or body introduction

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| prologue
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| prologue

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| epigraph
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| epigraph

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| volume
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| volume

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| epilogue
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| epilogue

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| conclusion
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| conclusion

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| coda
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| coda

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| afterword
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| afterword

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| appendix
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| appendix

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnotes
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnote section

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| footnotes
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| footnotes section

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| abbreviations
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| list of abbreviations

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| glossary
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| glossary

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibliography
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibliography

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| colophon
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| colophon

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| illustrations
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| illustrations

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| maps
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| maps

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| ahead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| ahead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bhead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dhead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| fmhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| frontmatter head

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bmhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| backmatter head

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| article
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| reference article

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| other
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| other

|}
The examples for <tt><div></tt> elements can be found in other relevant sections.

== xml:id Attribute ==
In addition to the the root element, the xml:id shall be used on all <tt><div></tt> elements, including <tt><titlePage></tt>, all <tt><pb></tt> elements, all <tt><figure></tt> elements, all <tt><table></tt> elements, and all <tt><note></tt> elements. The form is different than the root element, and should reflect the element type or name. Examples follow:

<pre>
<pb xml:id="pgi" n="i"/>

<div xml:id="contents" type="contents">

<div xml:id="c2" n="2" type="chapter">

<table xml:id="table1" n="1">

<figure xml:id="fig3" n="3">

<note xml:id="note1.3-34" n="34" type="endnote">
</pre>

For unnumbered sections, such as frontmatter <tt><div></tt>s, the xml:id will be the descriptive name of the section. For numerated sections, the xml:id will start with either an abbreviated form of the descriptive name, or with the complete name. Examples are detailed in the table below.

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Element or Section'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Suffix'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| title
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| copyright
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| copyright

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dedication
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dedication

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| acknowledgments
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| ack

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| preface
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| preface

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| introduction
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| intro

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| illustrations
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| illus

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| maps
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| maps

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| volume
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| volume

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| appendix
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| appendix

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnotes
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnotes

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| glossary
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| glossary

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibliography
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bib

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| colophon
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| colophon

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Enumerated elements'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''suffix'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| p1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| c1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnote
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| n1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| footnote
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| fn1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| indexItem1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibliography
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibItem1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| figure
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| fig1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| table
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| table1

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| article
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| article1

|}

== n Attribute ==
In addition to the xml:id attribute, the n attribute should be used to add further information on specific elements. The elements requiring the n attribute generally are those that have the xml:id attribute and have more than one of its kind. These include <tt><pb></tt>, chapter <tt><div></tt>, <tt><table></tt>, <tt><figure></tt>, <tt><note></tt>. Other <tt><div></tt> sections that have multiple instances, such as appendices, should be encoded as well. See the xml:id example for clarification.

== <tt><pb></tt> ==
It is important to maintain correct pagination so that the encoded version directly matches the print version. The empty <tt><pb></tt> element is used to mark the beginning of each physical page of the print document (including the frontmatter, first page, and blank pages). The <tt><pb></tt> element should be placed at the beginning of each physical page, and should be inside <tt><div></tt> elements. Never place a <tt><pb></tt> outside of a <tt><div></tt> element. If a page break occurs in the middle of a smaller element (e.g., <tt><p></tt>), it can be encoded there. There are two mandatory attributes required: xml:id, which has the same structure as other xml:id attributes, with uncp as the prefix, the ISBN as the root, and the page number, beginning with a ''pg'' as the suffix; n as the number of the page, which is the actual page number.

=== <tt><pb></tt> Examples ===
<pre>
<div type="contents" xml:id="contents">
<pb xml:id="pgvii" n="vii"/>
<head type="chapterTitle">Contents</head>
<p>at the Office at the University of California, Berkeley, gave me the <pb id="pg22" n="22"/>acknowledgments chance to share my ideas for this project in their speaker series. At the Berkeley talk, Martin Meeker,. . . </p>
</pre>

== <tt><fw></tt>: Running Heads ==
Running heads should be encoded using the forme work <tt><fw></tt> element, with verso and recto as the type attribute values. For sections and chapters where there is one verso and one recto running head, the information should be captured once, immediately after the first <tt><pb></tt> of the <tt><div></tt>. For sections and chapters where the running heads change depending on the context of the page—encyclopedias, end note sections, etc—then the data will be captured immediately following the <tt><pb></tt> for each new running head.

=== <tt><fw></tt> Example ===
<pre>
<pb xml:id="pg15" n="15"/>
<fw type="verso">H. Leon Prather Sr.</fw>
<fw type="recto">We Have Taken a City</fw>
</pre>

== <tt><ref></tt> ==
All references internal to a particular document as well as external references will be encoded using the <tt><ref></tt> element. Attributes for this element include id, target, type, and corresp. Id will use a unique identifier coupled with the ISBN of the book. Target will reference the id of the relevant element. Type includes the following values:

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Value'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Type of Reference'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| citeref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bibliographic citation reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| figref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| figure reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| footref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| footnote reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| noteref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| endnote reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| pageref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| page number reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| divref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| section or div reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| tableref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| table reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| displayref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| equation or other displayed material reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| boxmatterref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| boxed matter reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| uriref
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| URI reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| tablenote
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| table note reference

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| indexItem
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| index entry

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| other
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| other

|}

All internal references to sections, chapters, or other major division found in the text should be encoded to provide links.

=== pageref Example ===
<pre>
<ref target="#pg1" type="pageref">1</ref>
</pre>

=== uriref Example ===
<pre>
<p>. . . Law 106–380 created the Veterans History Project in 2000. For more information on the project, see [<ref target="http://www.loc.gov/vets/" type="uriref">http://www.loc.gov/vets/</ref>] (August 2, 2006).</p>
</pre>

=== divref Example ===
<pre>
<p>You can read more about this in <ref type="divref" target="#c2">Chapter 2</ref>.</p>
</pre>

== <tt><figure></tt> and <tt><graphic></tt> ==
Figures are encoded using a combination of <tt><figure></tt> and <tt><graphic></tt> elements. Generally speaking, <tt><graphic></tt> is used by itself to indicate the location of an inline graphic, illustration, or figure. When textual matter such as a figure number of caption is available, the compound element <tt><figure></tt> will be used, together with <tt><graphic></tt> which refers to the image file and elements such as <tt><head></tt> for figure number and <tt><p></tt> for figure caption. <tt><figDesc></tt> is used for alternate text describing the figure when the image is not used or seen.

=== <tt><figure></tt> Example ===
<pre>
<figure xml:id="fig3" n="3"><graphic url="figures/fig03.png" decls="#notCleared"/>
<figDesc>Billingsville School, Grier Heights neighborhood, Charlotte, 1951. (Courtesy of the <emph>Charlotte Observer)</emph></figDesc>
</figure>
</pre>

=== <tt><graphic></tt> Example ===
<pre>
<p>. . . and then you can see in this image <graphic url="figures/inline-image.png"/> the characteristics of . . .</p>
</pre>

== <tt><milestone></tt> ==
The <tt><milestone></tt> element should be used to indicate space or section breaks that are part of the typeset book, but otherwise not marked by a subhead. The unit attribute is used to indicate the type of break, and the n attribute can be used to indicate ornaments or other symbols.

=== <tt><milestone></tt> Example ===
<pre>
<milestone unit="line" n="***"/>
</pre>

== <tt><date></tt> ==
Dates should be encoded using the <tt><date></tt> element.

=== <tt><date></tt> Example ===
<pre>
<date>1865–1898</date>
<date>January 2, 1955</date>
<date>1998</date>
</pre>

= <tt><front></tt> =
The front element contains the typical frontmatter elements, including half title, title, copyright, dedication, contents, acknowledgments.

== <tt><titlePage></tt> ==
Includes the formal title page as well as half titles, indicated by the attribute type.

=== <tt><titlePage></tt> Example ===
<pre>
<titlePage type="fulltitle">
<pb xml:id="pgiii" n="iii"/>
<docTitle>
<titlePart type="main">Reading, Writing, & Race</titlePart>
<titlePart type="sub">The Desegregation of the Charlotte Schools</titlePart>
</docTitle>
<byline>
<docAuthor>Davison M. Douglas</docAuthor>
</byline>
<docImprint>
<publisher>THE UNIVERSITY OF NORTH CAROLINA PRESS</publisher>
<pubPlace>Chapel Hill & London</pubPlace>
</docImprint>
</titlePage>
</pre>

== Frontmatter Elements ==
Frontmatter elements will be contained within <tt><div></tt> elements, with a type attribute indicating the name. <tt><head></tt> will be used when the frontmatter name is displayed on the print page. Various elements will be used to indicate children elements on the page, including <tt><l></tt> when line breaks are important, <tt><list></tt> elements for items like table of contents, and <tt><p></tt> for paragraph based text. Please see section 6.6 on lists as well as section 4.3 on linking for more information on those topics.

=== <tt><div></tt> Example: Copyright ===
<pre>
<div type="copyright">
<pb xml:id="pgiv" n="iv"/>
<lg>
<l>© <date>2007</date> The University of North Carolina Press</l>
<l>All rights reserved</l>
<l>Set in Scala, The Sans, and Campaign types by</l>
<l>Keystone Typesetting, Inc.</l>
<l>Manufactured in the United States of America</l>
<l>This book was published with the assistance of</l>
<l>the Thornton H. Brooks Fund of the University of</l>
<l>North Carolina Press.</l>
</lg>
</div>
</pre>

=== <tt><div></tt> Example: Dedication ===
<pre>
<div type="dedication">
<pb xml:id="pgv" n="v"/>
<lg>
<l><hi rend="italic">To my parents</hi></l>
<l>J<hi rend="sc">ohn</hi> M<hi rend="sc">unroe</hi> D<hi rend="sc">ouglas</hi></l>
<l>&</l>
<l>M<hi rend="sc">arjorie</hi> L<hi rend="sc">utz</hi> D<hi rend="sc">ouglas</hi></l>
<l><hi rend="italic">who taught me the value of education</hi></l>
</lg>
<pb xml:id="pgvi" n="vi"/></div>
</pre>

=== <tt><div></tt> Example: Contents ===
<pre>
<div xml:id="contents" type="contents">
<pb xml:id="pgvii" n="vii"/>
<head type="chapterTitle">Contents</head>
<list type="simple">
<item>Acknowledgments, <ref target="#pgxi" type="pageref">xi</ref></item>
<item>Introduction, <ref target="#pg1" type="pageref">1</ref></item>
<item><hi rend="italic">Chapter</hi> 1 Challenging Separate and Unequal Education in North Carolina before <hi rend="italic">Brown</hi>, <ref target="#pg6" type="pageref">6</ref></item>. . .<item>Epilogue, <ref target="#pg245" type="pageref">245</ref></item>
<item>Notes, <ref target="#pg255" type="pageref">255</ref></item>
<item>Bibliography, <ref target="#pg325" type="pageref">325</ref></item>
<item>Index, <ref target="#pg343" type="pageref">343</ref></item>
</list>
<pb xml:id="pgviii" n="viii"/></div>
</pre>

=== <tt><div></tt> Example: Halftitle ===
<pre>
<div type="halftitle">
<pb xml:id="pgi" n="i"/>
<head type="halftitle">Reading, Writing, & Race</head>
<pb xml:id="pgii" n="ii"/>
</div>
</pre>

= <tt><body></tt> =
The <tt><body></tt> of the document contains the main text of the work, including any introductory or concluding chapters or sections.

== <tt><div></tt> ==
<tt><div></tt> elements are used for each major section and subsection of the work, including parts, chapters, and subheads. The type attribute is used to identify the sections and is mandatory. Other mandatory attributes include xml:id and n.

== <tt><head></tt> ==
Every chapter is contained within <tt><div></tt> elements, and generally includes a chapter number and chapter title. These will be encoded using the <tt><head></tt> element. Other chapter level <tt><head></tt> elements include subtitles and chapter authors in <tt><byline></tt> elements.

The head elements will always have a type, as noted in this table:

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Head Type Value'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Reference'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapterNumber
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapterTitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapterSubtitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chapter subtitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| partNumber
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| partTitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| partSubtitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part subtitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| seriesTitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| series title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| seriesEditor
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| series editor

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| ahead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| ahead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bhead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| dhead

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| fmhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| frontmatter head

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| bmhead
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| backmatter head

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| halftitle

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| entryName.A
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| article head

|}
If a chapter author is listed, the <tt><byline></tt> element will be used to encode this, as well as <tt><name></tt> for each author.

For reference works, all <tt><head></tt> elements will be encoded using the type above, with the suffix incrementing for multi-level heads. For instance, the first head will be entryName.A. The second head would be entryName.B. See section 6.9 below.

=== <tt><div></tt> and <tt><head></tt> Example: Chapter ===
<pre>
<body>
<pb xml:id="pg1" n="1"/>
<div xml:id="c1" n="1" type="chapter">
<head type="chapterNumber">3</head>
<head type="chapterTitle">Chapter Title</head>
<head type="chapterSubtitle">Chapter subtitle</head>
<byline>
<name>John Smith</name>
</byline>
<p>The men and women who served in the military during World War II have become known as “the greatest generation.” Although there are exceptions, the majority of these veterans have been exceedingly humble about the sacrifices that they made in service to the United States. When asked why they served, almost every one of them answers: “I was just doing my duty.”<ref type="noteref" n="1" target="#n1" rend="superscript">1</ref>.</p>
<quote>
<p>Extracted text.</p>
</quote>
</pre>

=== <tt><head></tt> Example: A head and B head ===
<pre>
<div xml:id="a3.1" type="ahead" n="3.1">
<head type="ahead">Ahead</head>
<p>Text.</p>
<div xml:id="b3.1.1" type="bhead" n="3.1.1">
<head type="bhead">Bhead</head>
<p>Text.</p>
</pre>

== <tt><epigraph></tt> ==
Epigraphs should be encoded using the <tt><epigraph></tt> element, an any point in the data: at the start of a part, chapter, section, or other major division. When the epigraph is attributed, <tt><cit></tt> should be used to associate the <tt><quote></tt> with the <tt><bibl></tt>. For multi-paragraph quotes, <tt><p></tt>s should be used; for poems <tt><lg></tt> can be used with <tt><l></tt> for individual lines.

For unattributed quotes, there is no need for <tt><cit></tt>. The <tt><quote></tt> element will still be used, whether with <tt><p></tt>s or with <tt><lg></tt>s, but as there is no attribution <tt><bibl></tt> is unnecessary.

=== <tt><epigraph></tt> Examples ===
<pre>
<epigraph>
<cit>
<quote>
<lg>
<l>On Santiago's bloody field</l>
<l>Where Spanish hosts were made to yield</l>
<l>The Negro like a phalanx great</l>
<l>Fought hard to save the ship of state</l>
<l>And Wilmington with her disgrace</l>
<l>Stares Santiago in the face</l>
<l>And shows her heartless feelings clear</l>
<l>For those who fought without a fear.</l>
</lg>
</quote>
<bibl>—<author>F. B. Coffin</author>, <title>"Santiago de Wilmington</title>," <date>1899</date></bibl>
</cit>
</epigraph>
</pre>

<pre>
<epigraph>
<cit>
<quote>
<p>No man, no race will preserve its rights that fears to die to maintain them. Nor will the world regard him as worthy of freedom who will not give his life if necessary in its defense.</p>
<p>The greatness of every man and of every race, in its last analysis, is to be measured by indifference to death.</p>
</quote>
<bibl>—Editorial in <title>The Herald</title> (<pubPlace>Brunswick Georgia</pubPlace>), <date>1898</date></bibl>
</cit>
</epigraph>
</pre>

== <tt><lg></tt> ==
Poems, lyrics, and other verse passages in text should have <tt><lg></tt> with a type of “verse” and <tt><l></tt> for individual lines.

=== <tt><lg></tt> Verse Example ===
<pre>
<lg type="verse">
<l>Freedom, freedom, freedom’s coming, and it won’t be long</l>
<l>Freedom, freedom, freedom’s coming, and it won’t be long.</l>
</lg>
</pre>

== Extracts ==
Extracted material should be encoded using the <tt><quote></tt> element, with <tt><p></tt> elements for paragraphs within the extract.

=== Extract Example ===
<pre>
<quote>
<p>He appeared to be vain of its beauty as he tossed it carelessly off his forehead, or suffered it to fall heavily and half conceal his eyes. These were twinkly and slippery, and nearly always half shut, for he laughed much, and then they partly closed of themselves, and at other times he had a way of watching from under his dropped lids. He was a wellshaped man, but it was hardly to be discovered as he lolled in his seat, or from the insufferably lazy manner of his walking. When he spoke, however, he stood erect, using forcible and graceful gestures.</p>
</quote>
</pre>

== Dialogues ==
Dialogues and other text that is primarily speech should be encoded using the <tt><sp></tt>, <tt><speaker></tt>, and <tt><said></tt> elements. Dialogues without headings can rely on just these elements. If a heading referring to the dialogue precedes the dialogue then the dialogue should be encoded in a <tt><div></tt> element.

If the optional who attribute is used to identify speakers, the value of who must refer to the

=== Dialogue Example ===
<pre>
<div xml:id="d1.1" type="ahead" n="1.1">
<head type="ahead">Interview with Rufus A. Lewis, by Donald T. Ferron</head>
<p>Date: Friday, January 20, 1956</p>
<p>Time: 11:00 <hi rend="smallcaps">a.m.</hi> to 2:15 <hi rend="smallcaps">p.m.</hi></p>
<p>Place: Respondent's home, 801 Bolivar Street, Montgomery, Alabama</p>
<sp>
<speaker>
[Ferron]:
</speaker>
<said>
[. . .] What is your relation to the Montgomery Improvement Association?
</said>
</sp>
<sp>
<speaker>
[Lewis]:
</speaker>
<said>I belong to the executive committee as a result of being co-chairman of the transportation committee. The executive committee is composed of the transportation committee, the committee for strategy, committee for public relations, and the finance committee.</said>
</sp>
<sp>
<speaker>
[Ferron]:
</speaker>
<said>Who is the other chairman?</said>
</sp>
</pre>

== <tt><list></tt> ==
The <tt><list></tt> element is used for lists, and has four specific attributes: ordered, bulleted, gloss, simple. The item element is used for each new item in a list. Ordered lists will have a number in the content, while a simple list will not. A bulleted list will have the bullet character in the content as well.

A gloss is a list of terms, and will use <tt><label></tt> to identify the term being defined. <tt><item></tt> will follow with the definition.

=== <tt><list></tt> Examples ===
<pre>
<list type="ordered">
<item>1. Papers through 1959</item>
<item>2. Papers, 1960–84</item>
<item>3. Papers, 1985–2000</item>
<item>4. Men of Annapolis Papers</item>
<item>5. Papers on Women</item>
</list>
</pre>

<pre>
<list type="bulleted">
<item>· Papers through 1959</item>
<item>· Papers, 1960–84</item>
<item>· Papers, 1985–2000</item>
<item>· Men of Annapolis Papers</item>
<item>· Papers on Women</item>
</list>
</pre>

<pre>
<list type="gloss">
<label>DTD</label>
<item>Document Type Definition-the set of rules that specifies how the SGML or XML grammar will be applied in a particular document instance.</item>
<label>XML</label>
<item>eXtensible Markup Language, a simplified subset of SGML (q.v.), developed by the World Wide Web Consortium.For a gentle introduction to XML, see <ref type="uriref" target="http://www.tei-c.org/P4X/SG.html">http://www.tei-c.org/P4X/SG.html</ref></item>
</list>
</pre>

== <tt><table></tt> ==
Tables will be contained by the <tt><table></tt> element, and should follow the TEI Guidelines, using <tt><row></tt> and <tt><cell></tt> for table structure. Table <tt><cell></tt>s have roles of “label” for headings and “data” for data. More can be found at
[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTTAB1 http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTTAB1].

Table heads should be encoded using a <tt><head></tt> element with the type of tableHead.

Table footnotes and source elements shall be encoded using <tt><note></tt> and <tt><p></tt> elements. There are two types of notes: one with a reference in the table body, and one without. The first should have a type of tablenote, and the second a type of source.

=== <tt><table></tt> Example ===
<pre>
<table xml:id="table1.1" n="1.1">
<head type="tableHead">TABLE 1. South Carolina Expenditures on Pupils and Teacher Salaries</head>
<row>
<cell role="label">Year</cell>
<cell role="label">Average per Pupil Spent<ref type="noteref" n="1" target="#note-tn1" rend="superscript">*</ref></cell>
<cell role="label">Average Teacher Salary</cell>
<cell role="label">Differential</cell>
</row>
<row>
<cell role="data">1920–21</cell>
<cell role="data">White: $39.26<lb/>Black: $4.84</cell>
<cell role="data">White: $773.33<lb/>Black: $225.47</cell>
<cell role="data">State spends 8.1 times more per white pupil; white teachers earn 3.4 times more</cell>
</row>
<note type="source"> <p>Sources: All figures from the <hi rend="italic">Annual Report of the State Superintendent of Education of the State of South Carolina</hi>.</p></note>
<note xml:id="note-tn1" n="*" type="tablenote"><p>All per-pupil expenditures are according to enrollment, with the exception of 1942–43.</p></note>
</table>
</pre>

== Reference Articles ==
Articles in reference works should be encoded using <tt><div></tt> and <tt><head></tt> elements for structure. All other elements should be encoded similarly to monographs: paragraphs using <tt><p></tt>, attributions using <tt><byline></tt>, bibliographic references using <tt><bibl></tt>, etc.

For reference articles where the entry terms run in to the descriptive paragraph, either with or without punctuation, the term or phrase should be repeated in a <tt><head></tt> element, as in the second example below.

=== Reference <tt><div></tt> and <tt><head></tt> Examples ===
<pre>
<div type="article" xml:id="article1" n="1">
<head type="entryName.A">Southern Zigzag Salamander</head>
<head type="entryName.B">Plethodon ventralis</head>
<p>64 to 111 mm (2.5 to 4.5 in.) This small salamander has a reddish orange to reddish brown stripe down the brown back and tail with wavy or zigzag edges at least on its anterior half. The belly is heavily mottled with black, white, and reddish orange. Many individuals in our area have no stripe, and both color phases have a variable amount of red pigment on the back, sides, and belly. Red-backed Salamanders have a straight-edged reddish dorsal stripe and a salt-and-pepper belly (if ventral reddish orange pigment is present, it is confined to the area between the front limbs).</p>
</div>
</pre>

<pre>
<div type="article" xml:id="article22" n="22">
<head type="entryName.A">Museum of the Cape Fear</head>
<p><hi rend="bold">Museum of the Cape Fear</hi> in Fayettville is the third regional...</p>
<p>References: <bibl><author>Angela Fracaro</author>, <title level="a">"A Fast Start at Looking Back,"</title> <title level="j">The State</title> <biblScope type="vol">57</biblScope> (<date>June 1989</date>)</bibl>; <bibl><author>Karen Rosalinde Zimmer</author>, <title level="u">"An Audience Development Plan for the Museum of the Cape Fear in Fayetteville"</title> (M.A. thesis, <pubPlace>UNC-Chapel Hill</pubPlace>, <date>1989</date>)</bibl>.</p>
<byline>Angelyn H. Patteson</byline>
</div>
</pre>

= <tt><back></tt> =
The <tt><back></tt> element includes all the backmatter material present in the book, including appendices, bibliography, and index. The sections are made up of <tt><div></tt> elements with the type indicating the section name: e.g., bibliography, index, etc.

== Backmatter <tt><div></tt> Sections ==
Sections other than the bibliography and index will be encoded in the same manner as the frontmatter sections, using <tt><div></tt>.

=== <tt><div></tt> Example: Acknowledgments ===
<pre>
<div type="acknowledgments" xml:id="ack">
<pb xml:id="pg287" n="287"/>
<head type="chapterTitle">Acknowledgments</head>
<p>This book has been an unusually. . . </pre>

== <tt><div></tt> Endnotes ==
Endnotes and footnotes should be captured in a backmatter <tt><div></tt>

=== <tt><div></tt> Example: Endnotes ===
<pre>
<div xml:id="endnotes" type="endnotes">
<pb xml:id="pg255" n="255"/>
<head type="chapterTitle">Notes</head>
</pre>
<div xml:id="anotes1.2" type="ahead" n="1.2">
<head type="ahead">CHAPTER ONE</head>
<note xml:id="note1.2-1" n="1" type="endnote"><num>1</num> <p><hi rend="italic">Brown v. Board of Education,</hi> 347 U.S. 483 (1954).</p></note>
<note xml:id="note1.2-2" n="2" type="endnote"><num>2</num> <p><hi rend="italic">Laws of North Carolina</hi> (1838–39), chap. 8, sec. 3, p. 13; North Carolina Advisory Committee, <hi rend="italic">Equal Protection of the Laws,</hi> p. 99.</p></note>
</pre>

== <tt><div></tt> Bibliography ==
Please see the documentation at [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI] for complete guidance on encoding bibliographic citations and references. There are three levels for encoding: <tt><bibl></tt> as the most basic level, <tt><biblStruct></tt> as more structured, and <tt><biblFull></tt> as the fully-structured ciation, having all the components of a TEI file description and as seen in the TEI header. <tt><listBibl></tt> can be used when encoding a list of citations, as in a bibliography.

Citations using the <tt><bibl></tt> element are loosely structured, with the major elements being encoded with elements such as <tt><author></tt>, <tt><editor></tt>, <tt><title></tt>, <tt><pubPlace></tt>, <tt><publisher></tt>, and <tt><biblScope></tt>.

Because of the flexibility of <tt><bibl></tt>, the majority of bibliographic references should be encoded using this element. Only use <tt><biblStruct></tt> when the citation is too complex to be encoded using <tt><bibl></tt>.

Use the attribute level to indicate the bibliographic level for a title: whether it identifies an article, book, journal, series, or unpublished material. The values are in the following table.

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Title Level Value'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Type of Title'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| a
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| (analytic) analytic title (article, poem, or other item published as part of a larger item)

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| m
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| (monographic) monographic title (book, collection, or other item published as a distinct item, including single volumes of multi-volume works)

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| j
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| (journal) journal title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| s
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| (series) series title

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| u
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| (unpublished) title of unpublished material (including theses and dissertations unless published by a commercial press)

|}
<tt><biblScope></tt> will be used for chapter, issue, volume, and part numbers, as well as for page ranges. Use the attribute type to indicate which item is encoded. The values are in the following table.

{| style="border-spacing:0;"
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''biblScope Type Value'''
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Description'''

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| vol
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| the element contains a volume number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| issue
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| the element contains a issue number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| part
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| the element contains a part number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| chap
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| the element contains a chapter number

|-
| style="border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0069in solid #000000;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| pp
| style="border:0.0069in solid #000000;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| the element contains a page range

|}
All bibliographic items should have unique IDs.

=== <tt><div></tt> Example: Bibliography ===
<pre>
<div type="bibliography" xml:id="bib">
<head type="chapterTitle">Bibliography</head>
<listBibl>
<bibl xml:id="bibItem1"> <editor>Bohannon, Paul</editor>, and <editor>George Dalton</editor>, eds. <title level="m">Markets in Africa</title>. [<pubPlace>Evanston, Ill.</pubPlace>]: <publisher>Northwestern University Press</publisher>, <date>1962</date>.</bibl>
<bibl xml:id="bibItem111"> <author>Lockert B. Mason</author>, <title level="a">”Babies Hospital, 1920–1978”</title>, <title level="j">North Carolina Medical Journal</title> <biblScope type="issue">45</biblScope>
<date>January 1984</date>): <biblScope type="pp">65–81</biblScope>. </bibl>
</listBibl>
</pre>

== <tt><div></tt> Index ==
The index will consist of a primary <tt><list></tt> element, with each entry encoded using the <tt><item></tt> element. All index entries will have unique IDs, to facilitate linking, especially when one entry refers to another.

Sub-entries will be in an additional <tt><list></tt> element within the initial <tt><item></tt>, as will further levels.

Page references will be tagged with <tt><ref></tt>, as will “see also” references to other index entries.

=== <tt><div></tt> Example: Index ===
<pre>
<div type="index" xml:id="index">
<pb xml:id="pg292" n="292"/>
<head type="chapterTitle">Index</head>
<list>
<item xml:id="indexItem1">Abolition, <ref target="#pg44" type="pageref">44</ref>, <reftarget="#pg47" type="pageref">47</ref>, <ref target="#pg48" type="pageref">48</ref>;
<list>
<item xml:id="indexItem2">and Northern whites, <ref target="#pg45" type="pageref">45</ref>, <ref target="#pg100" type="pageref">100</ref>, <ref target="#pg102" type="pageref">102</ref>;
</item>
<item xml:id="indexItem3">in Ohio, <ref target="#pg48" type="pageref">48</ref>, <ref target="#pg68" type="pageref">68</ref> (n. 23). <hi rend="italic">See also</hi> <ref type="indexItem" target="indexItem735">Underground Railroad</ref>
</item>
</list>
</item>
<item xml:id="indexItem735">Underground Railroad, <ref target="#pg47" type="pageref">47</ref>, <ref target="#pg48" type="pageref">48</ref>, <ref target="#pg49" type="pageref">49</ref>. <hi rend="italic">See also</hi>
<ref type="indexItem" target="indexItem1"></ref>Abolition</item>
</pre>

Workgroup to revise the Best Practices for TEI in Libraries

2017-02-20T15:17:51Z

Syd: /* 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 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)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== 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.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]

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

BP revision ticket triage

2017-01-15T15:05:52Z

Syd: /* hard implementation */

== Probably not controversial ==

=== easy implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 issue 6: revisit encoding of ISBNs] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 issue 20: revised "display examples" for levels 3 and 4] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/21 issue 21: reconsider rend="keep-hyphen"] – Elli has completed but asked Kevin to review.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/43 issue 43: header section: note about complete customizations] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/45 issue 45: controlled vocabulary for @type on divs?] – Elli is working on this.

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 issue 3: rewrite section on @rend and @rendition to account for @style] – Kevin will take this over.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/5 issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 issue 8: consider adding <width> and <height> as children of <extent>] – After reflection, Kevin has withdrawn this.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct] – Kevin will implement.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/2 issue 2: update the tie to a specific version of P5] – Syd will return to this now that the Council has released a new version of P5 – and [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/37 issue 37: ODDs are invalid] – Syd will complete.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/7 issue 7: give guidance on incorporating outside metadata into a header] – Kevin will propose a solution.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/9 issue 9: intertwingled content in <editorialDecl>] – Schema done, prose needs work
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/13 issue 13: update to take into account RDA] – Kevin has recruited a cataloger colleague to help.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27 issue 27: Coordinated OCR in BPTL] – postponed indefinitely ("dormant")
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/38 issue 38: build process broken] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/47 issue 47: Some comments on the Header (comparison of BPTL against P5)] – Elli will investigate, consulting with Syd as necessary

== Could be controversial ==

=== easy implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/36 issue 36: specify how to encode sigla] – Elli will review Kevin's proposed solution.

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] – Kevin will implement.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] – Elli will implement.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/31 issue 31: ambiguity over use of <lb/>, <cb/>, and <pb/> in Level 4] – Elli has completed but asked Kevin to review.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/10 issue 10: indicating interviewers and interviewees] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/11 issue 11: encoding <pb>s within <note>s] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/12 issue 12: bibliographies and other lists of works cited]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/16 issue 16: give guidance on encoding serials and composite documents]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/26 issue 26: Add (or update) examples to show use of modern authorities]

== Postpone ==

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 issue 19: pb@xml:id and METS]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/23 issue 23: relation of BP to TEI Simple (explaining the difference between the BPTL, TEI Simple, and TEI Lite)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/28 issue 28: update to take into account BIBFRAME]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/44 issue 44: proofreading auto-generated HTML] – assigned to James for the future
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/46 issue 46: BPTL Level 4 and Simple (attempting to reconcile the two)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/50 issue 50: update BPTL ODDs to use Pure ODD syntax]

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

BP revision ticket triage

2017-01-15T15:04:29Z

Syd: /* easy implementation */ ticked one off

== Probably not controversial ==

=== easy implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 issue 6: revisit encoding of ISBNs] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 issue 20: revised "display examples" for levels 3 and 4] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/21 issue 21: reconsider rend="keep-hyphen"] – Elli has completed but asked Kevin to review.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/43 issue 43: header section: note about complete customizations] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/45 issue 45: controlled vocabulary for @type on divs?] – Elli is working on this.

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 issue 3: rewrite section on @rend and @rendition to account for @style] – Kevin will take this over.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/5 issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 issue 8: consider adding <width> and <height> as children of <extent>] – After reflection, Kevin has withdrawn this.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct] – Kevin will implement.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/2 issue 2: update the tie to a specific version of P5] – Syd will return to this now that the Council has released a new version of P5 – and [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/37 issue 37: ODDs are invalid] – Syd will complete.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/7 issue 7: give guidance on incorporating outside metadata into a header] – Kevin will propose a solution.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/9 issue 9: intertwingled content in <editorialDecl>] – Syd needs to check whether he's already completed this.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/13 issue 13: update to take into account RDA] – Kevin has recruited a cataloger colleague to help.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27 issue 27: Coordinated OCR in BPTL] – postponed indefinitely ("dormant")
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/38 issue 38: build process broken] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/47 issue 47: Some comments on the Header (comparison of BPTL against P5)] – Elli will investigate, consulting with Syd as necessary

== Could be controversial ==

=== easy implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/36 issue 36: specify how to encode sigla] – Elli will review Kevin's proposed solution.

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] – Kevin will implement.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] – Elli will implement.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/31 issue 31: ambiguity over use of <lb/>, <cb/>, and <pb/> in Level 4] – Elli has completed but asked Kevin to review.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/10 issue 10: indicating interviewers and interviewees] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/11 issue 11: encoding <pb>s within <note>s] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/12 issue 12: bibliographies and other lists of works cited]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/16 issue 16: give guidance on encoding serials and composite documents]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/26 issue 26: Add (or update) examples to show use of modern authorities]

== Postpone ==

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 issue 19: pb@xml:id and METS]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/23 issue 23: relation of BP to TEI Simple (explaining the difference between the BPTL, TEI Simple, and TEI Lite)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/28 issue 28: update to take into account BIBFRAME]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/44 issue 44: proofreading auto-generated HTML] – assigned to James for the future
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/46 issue 46: BPTL Level 4 and Simple (attempting to reconcile the two)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/50 issue 50: update BPTL ODDs to use Pure ODD syntax]

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

Mapping ODD processing

2016-11-18T16:13:00Z

Syd:

This page is intended to help us map out and document the various processing steps that are applied to ODD files, both in the current Stylesheets and in a future alternative ODD processor. The main goal is to document the steps in generating TEI schemas from a TEI customization ODD file. However, processing P5 itself is part of that process. And although not our primary goal, we hope to also provide documentation for generating custom documentation from a TEI customization ODD file.

An ''italicized'' name in column A (NAME) indicates a step that is performed for ''building P5'', but not necessarily for generating a customization.

The '''bold''' stylesheet name in column F (XSLT FILES) is the one that is called; the others are the ones that the called one imports or includes.
{| class="wikitable"
|-
! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS
|-
| ''Generate P5'' || guidelines-[lang].xml || p5.xml (TEI) || Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. || There must be a repodate.xml file containing an XML representation of the git repo state. || [TEI]/Utilities/expand.xsl || *Spec elements occur in specGrp and in div.
|-
| ''Generate [P5] Subset'' || p5.xml (generated above) || p5subset.xml (TEI); p5subsetDoctored.xml (TEI) || Create a special cut-down version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || Utilities/subset.xsl; Utilities/dtdMagic.xsl (for Doctored) || Why are all the div/head elements included? Why is a schemaSpec not created? Is it the case that schemaSpec always and only represents a customization of an existing source, which must eventually chain back to p5subset? If so, ODD is not a generic language; it depends on P5. This also generates the beautiful p5subsetDoctored.xml, which is a hack for DTD production.
|-
| ''Generate JSON from p5subset'' || p5subset.xml || p5subset.json || D || E || F || G
|-
| Merge ODD customization with P5 source (SR calls this oddexpand) || ODD customization; p5subset || file.processedodd || The macrodef oddexpan is called, and that calls odd2odd.xsl with params || p5subset[Doctored].xml; ODD customization || Stylesheets/odds/odd2odd.xsl || The Doctored version of the subset should be used if creating DTDs; this happens in the P5 build, but not in the Stylesheets.
|-
| ODD chaining || An ODD customization (#2) whose @source points to another customization (#1) || file.processedodd || #1 undergoes merging with p5subset.xml, then #2 undergoes merging with the result of that. || Both ODDs and p5subset[Doctored].xml || [See above] || Wrinkle: either #1 or #2 might have components that point out to another source, which would then be imported. See Lou's tutorial [https://teic.github.io/TCW/howtoChain.html]
|-
| Generate RELAX NG from processed ODD || file.processedodd (output of rows above) || file.rng || Straight conversion, albeit complicated || || '''odds/odd2relax.xsl'''; odds/teiodds.xsl; odds/classatts.xsl; common/functions.xsl; common/i18n.xsl; common/common_param.xsl || The output is used to generate rnc and xsd using trang.
|-
| Extract Schematron || file.processedodd || file.sch || Generate a Schematron file with all rules correctly contextualized. || || odds/extract-isosch,xsl || Obsolete stuff with "sch" exists alongside iso-sch; former should be removed and latter renamed to "sch".
|-
| Generate DTD from ODD || B || C || D || E || F || G
|-
| A || B || C || D || E || F || G
|}

Mapping ODD processing

2016-11-15T19:35:49Z

Syd:

This page is intended to help us map out and document the various processing steps that are applied to ODD files, both in the current Stylesheets and in a future alternative ODD processor. The main goal is to document the steps in generating TEI schemas from a TEI customization ODD file. However, processing P5 itself is part of that process. And although not our primary goal, we hope to also provide documentation for generating custom documentation from a TEI customization ODD file.

An ''italicized'' name in column A (NAME) indicates a step that is performed for ''building P5'', but not necessarily for generating a customization.

The '''bold''' stylesheet name in column F (XSLT FILES) is the one that is called; the others are the ones that the called one imports or includes.
{| class="wikitable"
|-
! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS
|-
| ''Generate P5'' || guidelines-[lang].xml || p5.xml (TEI) || Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. || There must be a repodate.xml file containing an XML representation of the git repo state. || [TEI]/Utilities/expand.xsl || *Spec elements occur in specGrp and in div.
|-
| ''Generate [P5] Subset'' || p5.xml (generated above) || p5subset.xml (TEI); p5subsetDoctored.xml (TEI) || Create a special cut-down version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || Utilities/subset.xsl; Utilities/dtdMagic.xsl (for Doctored) || Why are all the div/head elements included? Why is a schemaSpec not created? Is it the case that schemaSpec always and only represents a customization of an existing source, which must eventually chain back to p5subset? If so, ODD is not a generic language; it depends on P5. This also generates the beautiful p5subsetDoctored.xml, which is a hack for DTD production.
|-
| ''Generate JSON from p5subset'' || p5subset.xml || p5subset.json || D || E || F || G
|-
| Merge ODD customization with P5 source (SR calls this oddexpand) || ODD customization; p5subset || file.processedodd || The macrodef oddexpan is called, and that calls odd2odd.xsl with params || p5subset[Doctored].xml; ODD customization || Stylesheets/odds/odd2odd.xsl || The Doctored version of the subset should be used if creating DTDs; this happens in the P5 build, but not in the Stylesheets.
|-
| ODD chaining || An ODD customization (#2) whose @source points to another customization (#1) || file.processedodd || #1 undergoes merging with p5subset.xml, then #2 undergoes merging with the result of that. || Both ODDs and p5subset[Doctored].xml || [See above] || Wrinkle: either #1 or #2 might have components that point out to another source, which would then be imported. See Lou's tutorial [https://teic.github.io/TCW/howtoChain.html]
|-
| Generate RelaxNG from processed ODD || file.processedodd (output of rows above) || file.rng || Straight conversion, albeit complicated || || '''odds/odd2relax.xsl'''; odds/teiodds.xsl; odds/classatts.xsl; common/functions.xsl; common/i18n.xsl; common/common_param.xsl || The output is used to generate rnc and xsd using trang.
|-
| Extract Schematron || file.processedodd || file.sch || Generate a Schematron file with all rules correctly contextualized. || || odds/extract-isosch,xsl || Obsolete stuff with "sch" exists alongside iso-sch; former should be removed and latter renamed to "sch".
|-
| Generate DTD from ODD || B || C || D || E || F || G
|-
| A || B || C || D || E || F || G
|}

Mapping ODD processing

2016-11-15T17:06:44Z

Syd:

This page is intended to help us map out and document the various processing steps that are applied to ODD files, both in the current Stylesheets and in a future alternative ODD processor.

An italicized name in column A (NAME) indicates a step that is performed for ''building P5'', but not necessarily for generating a customization.

The bold stylesheet name in column F (XSLT FILES) is the one that is called; the others are the ones that the called one imports.

{| class="wikitable"
|-
! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS
|-
| ''Generate P5'' || guidelines-[lang].xml || p5.xml (TEI) || Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. || There must be a repodate.xml file containing an XML representation of the git repo state. || [TEI]/Utilities/expand.xsl || *Spec elements occur in specGrp and in div.
|-
| ''Generate [P5] Subset'' || p5.xml (generated above) || p5subset.xml (TEI); p5subsetDoctored.xml (TEI) || Create a special cut-down version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || Utilities/subset.xsl; Utilities/dtdMagic.xsl (for Doctored) || Why are all the div/head elements included? Why is a schemaSpec not created? Is it the case that schemaSpec always and only represents a customization of an existing source, which must eventually chain back to p5subset? If so, ODD is not a generic language; it depends on P5. This also generates the ugly p5subsetDoctored.xml, which is a hack for DTD production.
|-
| Merge ODD customization with P5 source (SR calls this oddexpand) || ODD customization; p5subset || file.processedodd || The macrodef oddexpan is called, and that calls odd2odd.xsl with params || p5subset[Doctored].xml; ODD customization || Stylesheets/odds/odd2odd.xsl || The Doctored version of the subset should be used if creating DTDs; this happens in the P5 build, but not in the Stylesheets.
|-
| ODD chaining || An ODD customization (#2) whose @source points to another customization (#1) || file.processedodd || #1 undergoes merging with p5subset.xml, then #2 undergoes merging with the result of that. || Both ODDs and p5subset[Doctored].xml || [See above] ||
|-
| Generate RelaxNG from processed ODD || file.processedodd (output of rows above) || file.rng || Straight conversion, albeit complicated || || '''odds/odd2relax.xsl'''; odds/teiodds.xsl; odds/classatts.xsl; common/functions.xsl; common/i18n.xsl; common/common_param.xsl || The output is used to generate rnc and xsd using trang.
|-
| Extract Schematron || file.processedodd || file.sch || Generate a Schematron file with all rules correctly contextualized. || || odds/extract-isosch,xsl || Obsolete stuff with "sch" exists alongside iso-sch; former should be removed and latter renamed to "sch".
|-
| Generate DTD from ODD || B || C || D || E || F || G
|-
| A || B || C || D || E || F || G
|}

Mapping ODD processing

2016-11-15T17:02:15Z

Syd:

This page is intended to help us map out and document the various processing steps that are applied to ODD files, both in the current Stylesheets and in a future alternative ODD processor.

An italicized name in column 1 indicates a step that is performed for ''building P5'', but not necessarily for generating a customization.

{| class="wikitable"
|-
! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS
|-
| ''Generate P5'' || guidelines-[lang].xml || p5.xml (TEI) || Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. || There must be a repodate.xml file containing an XML representation of the git repo state. || [TEI]/Utilities/expand.xsl || *Spec elements occur in specGrp and in div.
|-
| ''Generate [P5] Subset'' || p5.xml (generated above) || p5subset.xml (TEI); p5subsetDoctored.xml (TEI) || Create a special cut-down version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || Utilities/subset.xsl; Utilities/dtdMagic.xsl (for Doctored) || Why are all the div/head elements included? Why is a schemaSpec not created? Is it the case that schemaSpec always and only represents a customization of an existing source, which must eventually chain back to p5subset? If so, ODD is not a generic language; it depends on P5. This also generates the ugly p5subsetDoctored.xml, which is a hack for DTD production.
|-
| Merge ODD customization with P5 source (SR calls this oddexpand) || ODD customization; p5subset || file.processedodd || The macrodef oddexpan is called, and that calls odd2odd.xsl with params || p5subset[Doctored].xml; ODD customization || Stylesheets/odds/odd2odd.xsl || The Doctored version of the subset should be used if creating DTDs; this happens in the P5 build, but not in the Stylesheets.
|-
| ODD chaining || An ODD customization (#2) whose @source points to another customization (#1) || file.processedodd || #1 undergoes merging with p5subset.xml, then #2 undergoes merging with the result of that. || Both ODDs and p5subset[Doctored].xml || [See above] ||
|-
| Generate RelaxNG from processed ODD || file.processedodd (output of rows above) || file.rng || Straight conversion, albeit complicated || || '''odds/odd2relax.xsl'''; odds/teiodds.xsl; odds/classatts.xsl; common/functions.xsl; common/i18n.xsl; common/common_param.xsl || The output is used to generate rnc and xsd using trang.
|-
| Extract Schematron || file.processedodd || file.sch || Generate a Schematron file with all rules correctly contextualized. || || odds/extract-isosch,xsl || Obsolete stuff with "sch" exists alongside iso-sch; former should be removed and latter renamed to "sch".
|-
| Generate DTD from ODD || B || C || D || E || F || G
|-
| A || B || C || D || E || F || G
|}

Rahtz Prize for TEI Ingenuity

2016-09-13T02:19:10Z

Syd: /* Important Info and Dates */

==About the Rahtz Prize==

The TEI Consortium has created the Rahtz Prize for TEI Ingenuity in memory of [https://en.wikipedia.org/wiki/Sebastian_Rahtz Sebastian Rahtz] (13 February 1955 – 15 March 2016). The award
is intended to honour Sebastian’s major technical and philosophical contributions to the TEI, and to encourage TEI innovation by the TEI community.

Sebastian was responsible for the design and implementation of a great deal of the TEI's technical infrastructure. Within the TEI community he was best known for the creation and maintenance of the XSLT Stylesheets that underlie much TEI conversion work, customization, and schema generation. As a member of both the TEI's Technical Council and its Board, he helped shape the direction of the Consortium.

The Rahtz Prize for TEI Ingenuity is awarded to an individual or team judged to have made a significant contribution to the [http://www.tei-c.org/About/mission.xml TEI-C's mission] in particular by
means of technical innovation. Many members of the TEI Community are engaged in exploring new
ways of implementing and expanding the coverage of the TEI system. It is hoped that this Prize will not only recognize excellent work already completed, but also encourage new projects and fresh approaches.

==Important Info and Dates ==

While the Board of Directors may alter these details in any given year, the expected timeline and award is as follows.

* 1 April: Nominations Due
* 1 June: Submissions Due
* 15 September: Winner Selected
* Annual Business Meeting: Winner Announced
* $1,000 USD will be awarded to one individual or team per year

==Nomination Process==

The TEI community will be encouraged to nominate prospective candidates for the Rahtz Prize by early Spring. The call for nominations will include a form that should be completed for each candidate, indicating basic information about the candidate(s) and their project. Nominations are due 1 April by midnight Hawaii/Aleutian Standard Time (HAST).

The nominations will be reviewed by members of the Awards Panel.

Self-nominations TBD.

==Submission Rules and Guidelines==

Nominees for the Rahtz Prize will be contacted by members of the Awards Panel by 15 April and encouraged to submit an application for review. The applications are due by 1 June in order to be considered in time for granting awards at the upcoming TEI-C Conference and Members' Meeting.

Along with contact information, nominees will be asked to submit a 500-1,500 summary describing the project/initiative. This summary should reflect the [http://www.tei-c.org/About/mission.xml TEI-C's mission] and the criteria as outlined below.

===Eligibility===
* Individuals or teams are eligible to apply. Membership to the TEI-Consortium is not a requirement.
* If awarded, the individuals/teams are eligible to submit another application three (3) years after the granted award.

==Review Process and Criteria==

Submissions will be reviewed by an Awards Panel comprising the Chair of the TEI-C Board of Directors, the Chair of the TEI-C Technical Council, and one invited, long-time and active member of the TEI Community. No member of the Panel may serve more than three consecutive years. Membership of the Panel will be agreed upon jointly by the Board and the Council by 1 April.

Nominations should demonstrate that the person or team nominated has made an outstanding contribution to one or more of the following:

* innovative development of the TEI Guidelines
* creation of TEI-aware tools and technologies that further dissemination, adoption, and engaged use of the TEI Guidelines
* expansive and inclusive TEI training and outreach opportunities
* informed development and cultivation of particular TEI practitioner communities

The Awards Panel is not required to make an award in every year.

==Terms==
The recipient(s) will receive a cash award of $1,000 USD, or a round number of about the same value in the currency in which the prize is to be awarded. The final selection is made by the Awards Panel and announced as part of the Business Meeting, which occurs as part of the annual TEI-C Conference and Members' Meeting. The disbursement of the cash award is arranged through the TEI-C Treasurer.

[[Category:Board]]

Unique-witnesses-within-app

2016-01-10T19:39:54Z

Syd: initial creation of clever but insufficient test for duplicate witness references in an <app>

In general, a given witness should only be referred to once within an
<code><app></code> (either on the <code>@wit</code> of
<code><rdg></code> or of <code><lem></code>).

This snippet of ODD code may be included in the
<code><elementSpec></code> for <tt>app</tt> to test the collection
of pointers to witnesses within a given <code><app></code> for
duplicates.

This test is insufficient for a variety of reasons. First,
the ''TEI Guidelines'' explicit permit the specification of witnesses (on
<code>@wit</code>) for one reading to be omitted. (See
[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html#TCAPPS 12.2.3 The Parallel Segmentation Method].)

Second, this code only tests the string value of a given pointer, not
what it points at. Thus the value of <code>@xml:base</code> is not
taken into account, and the values <code>"witnesses.xml#A"</code>
& <code>"./witnesses.xml#A"</code> will incorrectly be considered
as different. Similarly, this code will consider it OK when two
<code>@wit</code> pointers point two two different
<code>witness</code> elements that list the same MSS. (Arguably bad
encoding, but not technically incorrect.)

This also means that a repeated pointer to a witness (also bad
encoding, but not technically incorrect) will be flagged as an error.

And, perhaps most importantly, it means that this test does not check
that the pointers on <code>@wit</code> actually point to
<code>witness</code>es, as opposed to, say, <code>person</code>s.

<pre><nowiki><constraintSpec ident="unique-witness-within-app" scheme="isoschematron">
<constraint>
<sch:let name="wits" value="tokenize( normalize-space( string-join( .//@wit,' ') ),' ')"/>
<sch:let name="witless" value="distinct-values( $wits )"/>
<sch:report test="count( $wits ) ne count( $witless )">Duplicate witness within 'app'</sch:report>
</constraint>
</constraintSpec></nowiki></pre>

[[Category:Customization]]

[[Category:Schematron]]

Xmlid uniqueness.sch

2015-10-15T02:43:55Z

Syd: Simpler XPath to select @xml:id attrs; bug fix: double-escape '<'

It is often convenient to validate XML documents against RELAX NG schemas ''without'' using the “DTD Compatability” feature of RELAX NG. (Particularly when
using certain wildcard patterns, as this feature can cause a “conflicting ID-types for attribute "id" from namespace "http://www.w3.org/XML/1998/namespace" of element …” error. Personally, I think getting notified of the conflict is good, but it should be a warning, not an error.) However, when DTD Compatability is turned off, the RELAX NG validator no longer tests that the values of your ID attributes (which, in TEI, means your <tt>@xml:id</tt> attributes) are unique across all IDs in your document.

Here are three slightly different ways to test for unique <tt>@xml:id</tt> attributes in ISO Schematron.

BTW, in oXygen this feature can be turned on and off in <tt>Options > Preferences… > XML > XML Parser > RELAX NG</tt> pane by checking or unchecking the <tt>Check ID/IDREF</tt> box. The easy way to get to it is to filter for the string “IDREF”, which does not appear in any other preference panes. At least this works in oXygen 17.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"
xmlns:sqf="http://www.schematron-quickfix.com/validator/process">

<sch:p>This Schematron schema contains three different ways of doing
exactly the same thing: checking that each and every @xml:id
attribute in the input has a unique value.</sch:p>
<sch:p>I do not know which of these three methods, or some other, is
“best”, and I’m not sure there is any way to know. While #2 has the
shortest XPath, I think #3 is easier to understand. But if you think
#1 or #2 is easier to understand, by all means use it.</sch:p>
<sch:p>Note that none of these rules check that the value of @xml:id
is a valid identifier, or even that it is present. They only check
for uniqueness.</sch:p>
<sch:p>Written 2015-10-02 by Syd Bauman. Copyleft.</sch:p>

<sch:pattern>
<sch:rule context="@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test=" ../ancestor::*/@xml:id[ normalize-space(.) eq $myID ]
|
../preceding::*/@xml:id[ normalize-space(.) eq $myID ]
">#1 The @xml:id "<sch:value-of select="."
/>" on &lt;<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

<sch:pattern>
<sch:rule context="@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test="//*[ current()/.. >> .]/@xml:id[ normalize-space(.) eq $myID ]
">#2 The @xml:id "<sch:value-of select="."
/>" on &lt;<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

<sch:pattern>
<sch:rule context="@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test="../(ancestor::*|preceding::*)/@xml:id[ normalize-space(.) eq $myID ]
">#3 The @xml:id "<sch:value-of select="."
/>" on &lt;<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

</sch:schema>
</nowiki></pre>

[[Category:Schematron]]

Xmlid uniqueness.sch

2015-10-02T22:56:28Z

Syd: added page

It is often convenient to validate XML documents against RELAX NG schemas ''without'' using the “DTD Compatability” feature of RELAX NG. (Particularly when
using certain wildcard patterns, as this feature can cause a “conflicting ID-types for attribute "id" from namespace "http://www.w3.org/XML/1998/namespace" of element …” error. Personally, I think getting notified of the conflict is good, but it should be a warning, not an error.) However, when DTD Compatability is turned off, the RELAX NG validator no longer tests that the values of your ID attributes (which, in TEI, means your <tt>@xml:id</tt> attributes) are unique across all IDs in your document.

Here are three slightly different ways to test for unique <tt>@xml:id</tt> attributes in ISO Schematron.

BTW, in oXygen this feature can be turned on and off in <tt>Options > Preferences… > XML > XML Parser > RELAX NG</tt> pane by checking or unchecking the <tt>Check ID/IDREF</tt> box. The easy way to get to it is to filter for the string “IDREF”, which does not appear in any other preference panes. At least this works in oXygen 17.

<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"
xmlns:sqf="http://www.schematron-quickfix.com/validator/process">

<sch:p>This Schematron schema contains three different ways of doing
exactly the same thing: checking that each and every @xml:id
attribute in the input has a unique value.</sch:p>
<sch:p>I do not know which of these three methods, or some other, is
“best”, and I’m not sure there is any way to know. While #2 has the
shortest XPath, I think #3 is easier to understand. But if you think
#1 or #2 is easier to understand, by all means use it.</sch:p>
<sch:p>Note that none of these rules check that the value of @xml:id
is a valid identifier, or even that it is present. They only check
for uniqueness.</sch:p>
<sch:p>Written 2015-10-02 by Syd Bauman. Copyleft.</sch:p>

<sch:pattern>
<sch:rule context="//@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test=" ../ancestor::*/@xml:id[ normalize-space(.) eq $myID ]
|
../preceding::*/@xml:id[ normalize-space(.) eq $myID ]
">#1 The @xml:id "<sch:value-of select="."
/>" on <<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

<sch:pattern>
<sch:rule context="//@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test="//*[ current()/.. >> .]/@xml:id[ normalize-space(.) eq $myID ]
">#2 The @xml:id "<sch:value-of select="."
/>" on <<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

<sch:pattern>
<sch:rule context="//@xml:id">
<sch:let name="myID" value="normalize-space(.)"/>
<sch:report test="../(ancestor::*|preceding::*)/@xml:id[ normalize-space(.) eq $myID ]
">#3 The @xml:id "<sch:value-of select="."
/>" on <<sch:value-of select="name(..)"
/>> duplicates an @xml:id found earlier in the document</sch:report>
</sch:rule>
</sch:pattern>

</sch:schema>
</nowiki></pre>

[[Category:Schematron]]

Category:Schematron

2015-10-02T22:25:16Z

Syd: bug fix of what looks like a copy-and-paste error

This page collects together any pages relating to Schematron for TEI resources.

All of the code snippets posted here are freely available for public use. They are offered as is, and we make no guarantees about their usefulness or effectiveness. Please feel free to experiment with them. If you make any useful revisions, please post the modified version here.
----
'''To contribute a rule, please create a new page within this category and post your code.'''
<p>
'''To create a new page and post your code, you should:'''
* Log in (Create a user account for this WIKI if you have not done so.)
* Add a new page.
** To do this, add the name of the new page to the URL in your browser's address bar after index.php/
** For example, if you wish to create a new page called "MyNewSchematron.sch", just edit the URL in your web browser's address bar to look like this: '''<nowiki>http://www.tei-c.org/wiki/index.php/MyNewSchematron.sch</nowiki>'''
* Assuming no one else has made a page with the name you chose, you will be brought to a blank page. Click the edit button and do the following:
** Provide some accompanying explanation at the top of the page
** Cut and paste your code into the window.
** Wrap any code in <nowiki><pre><nowiki> .... </nowiki></pre></nowiki> tags
** Add the text <nowiki>[[Category:Schematron]]</nowiki> to the bottom of the page. This is important. It ensures that your page will show up on the Schematron page.
** Click "Save Page" when you are finished. Your page should show up on this page in the list of Schematron rules. You can go back and edit at any time.
* '''Note:''' We strongly suggest providing a Summary, and information about Required Input, Expected Output, and Known Restrictions or Problems before the code itself.
</p>

[[Category:Code]]
[[Category:Testing and QA tools]]

Talk:Set when-iso to today

2015-10-02T22:22:36Z

Syd: Created page with "The XPath functions <code>current-dateTime()</code> and <code>current-date()</code> return W3C dateTime and date, respectively. Why would one want to put these W3C temporal expre..."

The XPath functions <code>current-dateTime()</code> and <code>current-date()</code> return W3C dateTime and date, respectively. Why would one want to put these W3C temporal expressions on a <tt>@when-iso</tt> attribute as opposed to a <tt>@when</tt> attribute?

Janus.xslt

2014-12-25T17:08:35Z

Syd: fix obvious (and severe) bugs, thanks to Keith Handley

This stylesheet converts the so-called "janus" elements into proper P5 <choice>s. That is all.
<pre><nowiki><?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">















<xsl:import href="Copy-All.xsl"/>

<xsl:output method="xml" encoding="UTF-8" cdata-section-elements="eg"/>

<xsl:template match="abbr[@expan]">
<xsl:element name="choice">
<xsl:element name="abbr">
<xsl:apply-templates select="./@*[local-name()!='expan']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="expan">
<xsl:value-of select="@expan"/>
</xsl:element>
</xsl:element>
</xsl:template>

<xsl:template match="expan[@abbr]">
<xsl:element name="choice">
<xsl:element name="expan">
<xsl:apply-templates select="./@*[local-name()!='abbr']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="abbr">
<xsl:value-of select="@abbr"/>
</xsl:element>
</xsl:element>
</xsl:template>

<xsl:template match="sic[@corr]">
<xsl:element name="choice">
<xsl:element name="sic">
<xsl:apply-templates select="./@*[local-name()!='corr']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="corr">
<xsl:value-of select="@corr"/>
</xsl:element>
</xsl:element>
</xsl:template>

<xsl:template match="corr[@sic]">
<xsl:element name="choice">
<xsl:element name="corr">
<xsl:apply-templates select="./@*[local-name()!='sic']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="sic">
<xsl:value-of select="@sic"/>
</xsl:element>
</xsl:element>
</xsl:template>

<xsl:template match="orig[@reg]">
<xsl:element name="choice">
<xsl:element name="orig">
<xsl:apply-templates select="./@*[local-name()!='reg']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="reg">
<xsl:value-of select="@reg"/>
</xsl:element>
</xsl:element>
</xsl:template>

<xsl:template match="reg[@orig]">
<xsl:element name="choice">
<xsl:element name="reg">
<xsl:apply-templates select="./@*[local-name()!='orig']"/>
<xsl:apply-templates select="./child::node()"/>
</xsl:element>
<xsl:element name="orig">
<xsl:value-of select="@orig"/>
</xsl:element>
</xsl:element>
</xsl:template>

</xsl:stylesheet>
</nowiki></pre>
[[Category:P4toP5]]
[[Category:XSLT]]

Council agenda 2014-11

2014-11-13T17:09:09Z

Syd: /* Tuesday 18 November 2014 */

=Draft Agenda for TEI Technical Council Meeting 2014-11-17 to 2014-11-19=

== Monday 17 November 2014 ==
09:00 - 10:30
* TEI Simple
* Pure ODD
* TEI DH2015 HackAThon
* Correspondence
10:30 - 10:45
* Tea Break
10:45 - 13:00
* Ticket Discussion and Assignment
13:00 - 14:30
* Lunch
14:30 - 16:00 (15:30 - Tea Break)
* Tickets Recap and other discussion
16:00 - 17:00
* Ticket implementation or other TEI Work
18:00- Dinner?

== Tuesday 18 November 2014 ==
09:00 - 10:30
* JTEI Schema and authoring package: should the schema be adopted as an "official" customization, and should the authoring package be integrated into the oxygen-tei plugin? (MH)
* Global @resp and friends (MH, LB, HC)
* LOC date attrs (SB; see [http://loc.gov/standards/datetime/pre-submission.html LOC draft standard])
10:30 - 10:45
* Tea Break
10:45 - 13:00
* Tickets
13:00 - 14:00
* Lunch ?
14:00 - 17:00
* Tickets Discussion
18:00-
* ??

== Wednesday 19 November 2014 ==
09:00 - 10:30
* Presentation on how OxGarage works (JC)
10:30 - 10:45
* Tea Break
10:45 - 13:00
* Ticket Discussion and Assignment
13:10 - 14:30
* Lunch (?)
14:30 - 15:30
* Tickets Recap and other discussion
15:30
* tea break
15:30 - 17:00
* Ticket implementation or other TEI Work
18:00 -
* ??

[[Category:Council]]

Council agenda 2014-08

2014-09-05T11:01:27Z

Syd: add Council category link

Please add your agenda items below:

* Add items here
* Next Release (SB/EM); release cut-off-date
* TEI Simple (SR)
* Reminder to feed back thoughts on CorrespDesc (PWS)
* Autumn Face2Face (HC)
* List Types (MH/SR)
* HackAThon at TEI Conf?
* Reminder of tickets
* AOB

Next meeting: Friday 3 October

[[Category:Council]]

Oxford2013-Actions2

2014-02-11T17:10:42Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|has now been implemented (twice, sort of); ticket closed
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|DONE. Tried both with Options > Preferences > XML > XML Parser > RELAX NG > Check ID/IDREF checked and unchecked against tei_allPlus.rng 2.5.0, and did not reproduce error.
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|JC did, hand off to EM Jan 9 '14
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|Jan 28 '14 Discussions begun, proposal draft begun
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|Dec 10, 2013 done
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|Dec 10, 2013 Done
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Conferences

2014-02-06T13:25:13Z

Syd: /* Digital Humanities */

[[Category:Community]]
This page lists conferences at which TEI-related content appears regularly. No particular grouping is assumed at first, we'll see how this page develops. It seems that we may allow for less-formal details to appear here as well, so feel welcome to add to each section whatever you think others may like to know concerning these events.

== Balisage: The Markup Conference ==
Annual in early August. This is what Extreme Markup turned into.

Up until 2013 based in [[wikipedia:Montréal|Montréal]], Canada. The 2014 conference will be held outside Washington, DC.

'''Links'''
* http://www.balisage.net/
* [http://www.balisage.net/Proceedings/index.html Balisage Series on Markup Technologies]

== CLiP: Computers, Literature and Philology ==
Annual, with breaks. Moveable.

'''Links'''
* http://www.cch.kcl.ac.uk/clip2006/index.html – the most recent meeting
* [http://www.cch.kcl.ac.uk/clip2006/content/practicalities/past_conferences.html past meetings]

== DHCS: Chicago Colloquium on Digital Humanities and Computer Science ==
Annual. Past colloquia were hosted by the University of Chicago and Northwestern University.

The goal of the annual Chicago DHCS Colloquium is to bring together researchers and scholars in the Humanities and Computer Sciences to identify and explore new directions and perspectives for future research. The 2008 colloquium (http://dhcs.uchicago.edu) will be held at the University of Chicago from Nov. 1st – 3rd.

== Digital Humanities ==
Annual. Moveable. Latest news to be found on the [http://www.digitalhumanities.org/conference general page].

'''Links'''
* http://dh2013.unl.edu/ – the Nebraska meeting, 2013
* http://www.dh2012.uni-hamburg.de/ – the Hamburg meeting, 2012
* https://dh2011.stanford.edu/ – the Stanford meeting, 2011
* http://dh2010.cch.kcl.ac.uk/ – the London meeting, 2010
* http://www.mith2.umd.edu/dh09/
* http://www.ekl.oulu.fi/dh2008/ – the 2008 edition
* http://www.digitalhumanities.org/dh2007/ – the 2007 meeting

== DRHA: Digital Resources for the Humanities and Arts ==
Annual, based in Great Britain.

'''Links'''
* http://www.drha2010.org.uk/ – 2010 Meeting
* http://www.dho.ie/drha2009 – 2009 Meeting
* http://www.rsd.cam.ac.uk/drha08/ – 2008 Meeting
* http://www.dartington.ac.uk/drha07/ – 2007 Meeting
 

== ELPUB: Electronic Publishing ==
Annual. Moveable.

'''Links'''
* http://www.elpub.net/
* http://elpub.scix.net/cgi-bin/works/Home – ELPUB Digital Library

== Linguistic Annotation Workshop (LAW) ==
Most often a satellite of *ACL events. See the [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html homepage of the first event] for the genetics. Sponsored by the [http://www.cs.vassar.edu/sigann/ ACL Special Interest Group for Annotation].

Proceedings of LAW meetings can be found in the 'Workshop' section of the [http://www.aclweb.org/anthology-new/ ACL Anthology].

* [http://faculty.washington.edu/fxia/LAWVI/ LAW VI]
* [http://cemantix.org/workshop/law-v/ LAW V]
* [http://pages.cs.brandeis.edu/~clp/LAW4/The_LAW_IV.html LAW IV]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-09.html LAW III]
* [http://verbs.colorado.edu/LAW2008/ LAW II]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html LAW I]

== LREC: Language Resources and Evaluation ==
Biannual. Moveable. See the individual homepages for electronic versions of the proceedings.

'''Links'''
* http://www.lrec-conf.org/lrec2012/ – the 2012 edition
* http://www.lrec-conf.org/lrec2010/ – the 2010 edition
* http://www.lrec-conf.org/lrec2008/ – the 2008 edition
* http://www.lrec-conf.org/

== PALC: Practical Applications in Language and Computers ==
Biannual. It used to be "Practical Applications of Language Corpora". Based in [[wikipedia:Łódź|Łódź]], Poland.

'''Links'''
* http://palc.ia.uni.lodz.pl/

== TEI Conference and Members' Meeting ==
Annual. Moveable.

See also the [http://www.tei-c.org/Membership/Meetings/ TEI website list] for a complete listing; and
watch the [http://www.tei-c.org/News/ TEI News page] for the latest information.

'''Links''' to recent conferences

* The 2014 meeting will be in Evanston, IL
* [http://digilab2.let.uniroma1.it/teiconf2013/ The 2013 meeting: “The Linked TEI: Text Encoding in the Web”] in Rome, Italy
* [http://idhmc.tamu.edu/teiconference/ The 2012 meeting: ''TEI and the C(r|l)o(w|u)d''] in College Station, TX
* [http://www.zde.uni-wuerzburg.de/tei_mm_2011/ The 2011 meeting: ''Philology in the Digital Age''] in Würzburg, Germany
* [http://ling.unizd.hr/~tei2010/index.en.html The 2010 meeting: ''TEI Applied: Digital Texts and Language Resources''] in Zadar, Croatia
* [http://www.lib.umich.edu/spo/teimeeting09/ The 2009 meeting: ''Text encoding in the era of mass digitization''] in Ann Arbor, MI

Conferences

2014-02-06T13:22:08Z

Syd: /* Balisage: The Markup Conference */

[[Category:Community]]
This page lists conferences at which TEI-related content appears regularly. No particular grouping is assumed at first, we'll see how this page develops. It seems that we may allow for less-formal details to appear here as well, so feel welcome to add to each section whatever you think others may like to know concerning these events.

== Balisage: The Markup Conference ==
Annual in early August. This is what Extreme Markup turned into.

Up until 2013 based in [[wikipedia:Montréal|Montréal]], Canada. The 2014 conference will be held outside Washington, DC.

'''Links'''
* http://www.balisage.net/
* [http://www.balisage.net/Proceedings/index.html Balisage Series on Markup Technologies]

== CLiP: Computers, Literature and Philology ==
Annual, with breaks. Moveable.

'''Links'''
* http://www.cch.kcl.ac.uk/clip2006/index.html – the most recent meeting
* [http://www.cch.kcl.ac.uk/clip2006/content/practicalities/past_conferences.html past meetings]

== DHCS: Chicago Colloquium on Digital Humanities and Computer Science ==
Annual. Past colloquia were hosted by the University of Chicago and Northwestern University.

The goal of the annual Chicago DHCS Colloquium is to bring together researchers and scholars in the Humanities and Computer Sciences to identify and explore new directions and perspectives for future research. The 2008 colloquium (http://dhcs.uchicago.edu) will be held at the University of Chicago from Nov. 1st – 3rd.

== Digital Humanities ==
Annual. Moveable. Latest news to be found on the [http://www.digitalhumanities.org/conference general page].

'''Links'''
* http://www.dh2012.uni-hamburg.de/ – the Hamburg meeting, 2012
* https://dh2011.stanford.edu/ – the Stanford meeting, 2011
* http://dh2010.cch.kcl.ac.uk/ – the London meeting, 2010
* http://www.mith2.umd.edu/dh09/
* http://www.ekl.oulu.fi/dh2008/ – the 2008 edition
* http://www.digitalhumanities.org/dh2007/ – the 2007 meeting

== DRHA: Digital Resources for the Humanities and Arts ==
Annual, based in Great Britain.

'''Links'''
* http://www.drha2010.org.uk/ – 2010 Meeting
* http://www.dho.ie/drha2009 – 2009 Meeting
* http://www.rsd.cam.ac.uk/drha08/ – 2008 Meeting
* http://www.dartington.ac.uk/drha07/ – 2007 Meeting
 

== ELPUB: Electronic Publishing ==
Annual. Moveable.

'''Links'''
* http://www.elpub.net/
* http://elpub.scix.net/cgi-bin/works/Home – ELPUB Digital Library

== Linguistic Annotation Workshop (LAW) ==
Most often a satellite of *ACL events. See the [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html homepage of the first event] for the genetics. Sponsored by the [http://www.cs.vassar.edu/sigann/ ACL Special Interest Group for Annotation].

Proceedings of LAW meetings can be found in the 'Workshop' section of the [http://www.aclweb.org/anthology-new/ ACL Anthology].

* [http://faculty.washington.edu/fxia/LAWVI/ LAW VI]
* [http://cemantix.org/workshop/law-v/ LAW V]
* [http://pages.cs.brandeis.edu/~clp/LAW4/The_LAW_IV.html LAW IV]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-09.html LAW III]
* [http://verbs.colorado.edu/LAW2008/ LAW II]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html LAW I]

== LREC: Language Resources and Evaluation ==
Biannual. Moveable. See the individual homepages for electronic versions of the proceedings.

'''Links'''
* http://www.lrec-conf.org/lrec2012/ – the 2012 edition
* http://www.lrec-conf.org/lrec2010/ – the 2010 edition
* http://www.lrec-conf.org/lrec2008/ – the 2008 edition
* http://www.lrec-conf.org/

== PALC: Practical Applications in Language and Computers ==
Biannual. It used to be "Practical Applications of Language Corpora". Based in [[wikipedia:Łódź|Łódź]], Poland.

'''Links'''
* http://palc.ia.uni.lodz.pl/

== TEI Conference and Members' Meeting ==
Annual. Moveable.

See also the [http://www.tei-c.org/Membership/Meetings/ TEI website list] for a complete listing; and
watch the [http://www.tei-c.org/News/ TEI News page] for the latest information.

'''Links''' to recent conferences

* The 2014 meeting will be in Evanston, IL
* [http://digilab2.let.uniroma1.it/teiconf2013/ The 2013 meeting: “The Linked TEI: Text Encoding in the Web”] in Rome, Italy
* [http://idhmc.tamu.edu/teiconference/ The 2012 meeting: ''TEI and the C(r|l)o(w|u)d''] in College Station, TX
* [http://www.zde.uni-wuerzburg.de/tei_mm_2011/ The 2011 meeting: ''Philology in the Digital Age''] in Würzburg, Germany
* [http://ling.unizd.hr/~tei2010/index.en.html The 2010 meeting: ''TEI Applied: Digital Texts and Language Resources''] in Zadar, Croatia
* [http://www.lib.umich.edu/spo/teimeeting09/ The 2009 meeting: ''Text encoding in the era of mass digitization''] in Ann Arbor, MI

Conferences

2014-02-06T13:17:49Z

Syd: /* Links to recent conferences */

[[Category:Community]]
This page lists conferences at which TEI-related content appears regularly. No particular grouping is assumed at first, we'll see how this page develops. It seems that we may allow for less-formal details to appear here as well, so feel welcome to add to each section whatever you think others may like to know concerning these events.

== Balisage: The Markup Conference ==
Annual. This is what Extreme Markup turned into.

Based in [[wikipedia:Montréal|Montréal]], Canada.

'''Links'''
* http://www.balisage.net/
* [http://www.balisage.net/Proceedings/index.html Balisage Series on Markup Technologies]

== CLiP: Computers, Literature and Philology ==
Annual, with breaks. Moveable.

'''Links'''
* http://www.cch.kcl.ac.uk/clip2006/index.html – the most recent meeting
* [http://www.cch.kcl.ac.uk/clip2006/content/practicalities/past_conferences.html past meetings]

== DHCS: Chicago Colloquium on Digital Humanities and Computer Science ==
Annual. Past colloquia were hosted by the University of Chicago and Northwestern University.

The goal of the annual Chicago DHCS Colloquium is to bring together researchers and scholars in the Humanities and Computer Sciences to identify and explore new directions and perspectives for future research. The 2008 colloquium (http://dhcs.uchicago.edu) will be held at the University of Chicago from Nov. 1st – 3rd.

== Digital Humanities ==
Annual. Moveable. Latest news to be found on the [http://www.digitalhumanities.org/conference general page].

'''Links'''
* http://www.dh2012.uni-hamburg.de/ – the Hamburg meeting, 2012
* https://dh2011.stanford.edu/ – the Stanford meeting, 2011
* http://dh2010.cch.kcl.ac.uk/ – the London meeting, 2010
* http://www.mith2.umd.edu/dh09/
* http://www.ekl.oulu.fi/dh2008/ – the 2008 edition
* http://www.digitalhumanities.org/dh2007/ – the 2007 meeting

== DRHA: Digital Resources for the Humanities and Arts ==
Annual, based in Great Britain.

'''Links'''
* http://www.drha2010.org.uk/ – 2010 Meeting
* http://www.dho.ie/drha2009 – 2009 Meeting
* http://www.rsd.cam.ac.uk/drha08/ – 2008 Meeting
* http://www.dartington.ac.uk/drha07/ – 2007 Meeting
 

== ELPUB: Electronic Publishing ==
Annual. Moveable.

'''Links'''
* http://www.elpub.net/
* http://elpub.scix.net/cgi-bin/works/Home – ELPUB Digital Library

== Linguistic Annotation Workshop (LAW) ==
Most often a satellite of *ACL events. See the [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html homepage of the first event] for the genetics. Sponsored by the [http://www.cs.vassar.edu/sigann/ ACL Special Interest Group for Annotation].

Proceedings of LAW meetings can be found in the 'Workshop' section of the [http://www.aclweb.org/anthology-new/ ACL Anthology].

* [http://faculty.washington.edu/fxia/LAWVI/ LAW VI]
* [http://cemantix.org/workshop/law-v/ LAW V]
* [http://pages.cs.brandeis.edu/~clp/LAW4/The_LAW_IV.html LAW IV]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-09.html LAW III]
* [http://verbs.colorado.edu/LAW2008/ LAW II]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html LAW I]

== LREC: Language Resources and Evaluation ==
Biannual. Moveable. See the individual homepages for electronic versions of the proceedings.

'''Links'''
* http://www.lrec-conf.org/lrec2012/ – the 2012 edition
* http://www.lrec-conf.org/lrec2010/ – the 2010 edition
* http://www.lrec-conf.org/lrec2008/ – the 2008 edition
* http://www.lrec-conf.org/

== PALC: Practical Applications in Language and Computers ==
Biannual. It used to be "Practical Applications of Language Corpora". Based in [[wikipedia:Łódź|Łódź]], Poland.

'''Links'''
* http://palc.ia.uni.lodz.pl/

== TEI Conference and Members' Meeting ==
Annual. Moveable.

See also the [http://www.tei-c.org/Membership/Meetings/ TEI website list] for a complete listing; and
watch the [http://www.tei-c.org/News/ TEI News page] for the latest information.

'''Links''' to recent conferences

* The 2014 meeting will be in Evanston, IL
* [http://digilab2.let.uniroma1.it/teiconf2013/ The 2013 meeting: “The Linked TEI: Text Encoding in the Web”] in Rome, Italy
* [http://idhmc.tamu.edu/teiconference/ The 2012 meeting: ''TEI and the C(r|l)o(w|u)d''] in College Station, TX
* [http://www.zde.uni-wuerzburg.de/tei_mm_2011/ The 2011 meeting: ''Philology in the Digital Age''] in Würzburg, Germany
* [http://ling.unizd.hr/~tei2010/index.en.html The 2010 meeting: ''TEI Applied: Digital Texts and Language Resources''] in Zadar, Croatia
* [http://www.lib.umich.edu/spo/teimeeting09/ The 2009 meeting: ''Text encoding in the era of mass digitization''] in Ann Arbor, MI

Conferences

2014-02-06T13:17:00Z

Syd: /* TEI Conference and Members' Meeting */

[[Category:Community]]
This page lists conferences at which TEI-related content appears regularly. No particular grouping is assumed at first, we'll see how this page develops. It seems that we may allow for less-formal details to appear here as well, so feel welcome to add to each section whatever you think others may like to know concerning these events.

== Balisage: The Markup Conference ==
Annual. This is what Extreme Markup turned into.

Based in [[wikipedia:Montréal|Montréal]], Canada.

'''Links'''
* http://www.balisage.net/
* [http://www.balisage.net/Proceedings/index.html Balisage Series on Markup Technologies]

== CLiP: Computers, Literature and Philology ==
Annual, with breaks. Moveable.

'''Links'''
* http://www.cch.kcl.ac.uk/clip2006/index.html – the most recent meeting
* [http://www.cch.kcl.ac.uk/clip2006/content/practicalities/past_conferences.html past meetings]

== DHCS: Chicago Colloquium on Digital Humanities and Computer Science ==
Annual. Past colloquia were hosted by the University of Chicago and Northwestern University.

The goal of the annual Chicago DHCS Colloquium is to bring together researchers and scholars in the Humanities and Computer Sciences to identify and explore new directions and perspectives for future research. The 2008 colloquium (http://dhcs.uchicago.edu) will be held at the University of Chicago from Nov. 1st – 3rd.

== Digital Humanities ==
Annual. Moveable. Latest news to be found on the [http://www.digitalhumanities.org/conference general page].

'''Links'''
* http://www.dh2012.uni-hamburg.de/ – the Hamburg meeting, 2012
* https://dh2011.stanford.edu/ – the Stanford meeting, 2011
* http://dh2010.cch.kcl.ac.uk/ – the London meeting, 2010
* http://www.mith2.umd.edu/dh09/
* http://www.ekl.oulu.fi/dh2008/ – the 2008 edition
* http://www.digitalhumanities.org/dh2007/ – the 2007 meeting

== DRHA: Digital Resources for the Humanities and Arts ==
Annual, based in Great Britain.

'''Links'''
* http://www.drha2010.org.uk/ – 2010 Meeting
* http://www.dho.ie/drha2009 – 2009 Meeting
* http://www.rsd.cam.ac.uk/drha08/ – 2008 Meeting
* http://www.dartington.ac.uk/drha07/ – 2007 Meeting
 

== ELPUB: Electronic Publishing ==
Annual. Moveable.

'''Links'''
* http://www.elpub.net/
* http://elpub.scix.net/cgi-bin/works/Home – ELPUB Digital Library

== Linguistic Annotation Workshop (LAW) ==
Most often a satellite of *ACL events. See the [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html homepage of the first event] for the genetics. Sponsored by the [http://www.cs.vassar.edu/sigann/ ACL Special Interest Group for Annotation].

Proceedings of LAW meetings can be found in the 'Workshop' section of the [http://www.aclweb.org/anthology-new/ ACL Anthology].

* [http://faculty.washington.edu/fxia/LAWVI/ LAW VI]
* [http://cemantix.org/workshop/law-v/ LAW V]
* [http://pages.cs.brandeis.edu/~clp/LAW4/The_LAW_IV.html LAW IV]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-09.html LAW III]
* [http://verbs.colorado.edu/LAW2008/ LAW II]
* [http://www.ling.uni-potsdam.de/acl-lab/LAW-07.html LAW I]

== LREC: Language Resources and Evaluation ==
Biannual. Moveable. See the individual homepages for electronic versions of the proceedings.

'''Links'''
* http://www.lrec-conf.org/lrec2012/ – the 2012 edition
* http://www.lrec-conf.org/lrec2010/ – the 2010 edition
* http://www.lrec-conf.org/lrec2008/ – the 2008 edition
* http://www.lrec-conf.org/

== PALC: Practical Applications in Language and Computers ==
Biannual. It used to be "Practical Applications of Language Corpora". Based in [[wikipedia:Łódź|Łódź]], Poland.

'''Links'''
* http://palc.ia.uni.lodz.pl/

== TEI Conference and Members' Meeting ==
Annual. Moveable.

See also the [http://www.tei-c.org/Membership/Meetings/ TEI website list] for a complete listing; and
watch the [http://www.tei-c.org/News/ TEI News page] for the latest information.

===Links to recent conferences===
* The 2014 meeting will be in Evanston, IL
* [http://digilab2.let.uniroma1.it/teiconf2013/ The 2013 meeting: “The Linked TEI: Text Encoding in the Web”] in Rome, Italy
* [http://idhmc.tamu.edu/teiconference/ The 2012 meeting: ''TEI and the C(r|l)o(w|u)d''] in College Station, TX
* [http://www.zde.uni-wuerzburg.de/tei_mm_2011/ The 2011 meeting: ''Philology in the Digital Age''] in Würzburg, Germany
* [http://ling.unizd.hr/~tei2010/index.en.html The 2010 meeting: ''TEI Applied: Digital Texts and Language Resources''] in Zadar, Croatia
* [http://www.lib.umich.edu/spo/teimeeting09/ The 2009 meeting: ''Text encoding in the era of mass digitization''] in Ann Arbor, MI

Oxford2013-Actions2

2014-02-04T17:21:40Z

Syd: /* Actions for Syd Bauman */ closed FR481

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|has now been implemented (twice, sort of); ticket closed
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|JC did, hand off to EM Jan 9 '14
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|Jan 28 '14 Discussions begun, proposal draft begun
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|Dec 10, 2013 done
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|Dec 10, 2013 Done
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-02-04T16:28:07Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|was not implemented; have written code, but not tested sufficiently or checked-in
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

PublicationStmt-Changes

2014-01-21T01:49:07Z

Syd: /* Changes in P5 Version 2.6.0 */

== About <publicationStmt> ==

Since P2, the content of <publicationStmt> has been arranged by
order. The rules, much the same in P2, P3, P4, and P5, are that the
contents of <publicationStmt> should consist of one or more "sets" of
an authorizing agent (<publisher>, <distributor>, <authority>
-- we'll call this the "leader" element here) followed by zero or
more elements either describing the agent or the authorizations the
agent prohibits or allows (<pubPlace>, <address>, <idno>,
<availability>, and <date> -- we'll call these the "follower"
elements here).

== Changes in P5 Version 2.6.0 ==
However, these rules have only been partially enforced by the schema (to different extents in P2-P5). The 2.6.0 release brings two changes to <publicationStmt>, one to the rules, and one to the schema.

# Prior to this release, the "follower" elements were supposed to appear in that particular order (<pubPlace>, <address>, <idno>, <availability>, and then <date>), if at all. As of P5 version 2.6.0 this constraint is dropped: the "following" elements within a "set" may appear in any order.
# Although the rules were quite clearly written in P5, the schema did not enforce them. One could put "leader" elements after "follower" elements, or not have a "leader" element at all. However, as of P5 2.6.0 the schema now enforces the rules.

It is quite likely that some people have not noticed the detailed rules listed in the TEI P5 Guidelines, and just followed the schema. The good news is that now these folks will not have to puzzle through the rules to know if their documents conform or not -- the validator will just raise an error if the <publicationStmt> does not follow the rules. The bad news, of course, is if your document doesn't follow the rules, now you have to fix it.

We believe that the most common error to occur will be of a missing "leader" element, as happens when you have only an <availability>. We think this will be common because many on the TEI Technical Council recognise that they have done this themselves!

== Examples ==
Samples of proper <publicationStmt> structures:

''' one "set" of a "leader" with no "followers": '''
<blockquote>
<pre>
<nowiki><publicationStmt>
<publisher>  </publisher>
</publicationStmt></nowiki>
</pre>
</blockquote>

''' one "set" of a "leader" with a few "followers": '''
<blockquote>
<pre>
<nowiki> <publicationStmt>
<publisher>  </publisher>
<address>  </address>
<date>  </date>
<availability>  </availability>
</publicationStmt></nowiki>
</pre>
</blockquote>

''' two "sets" of a "leader" with 1 and 3 "followers", respectively: '''
<blockquote>
<pre>
<nowiki> <publicationStmt>
<distributor>  </distributor>
<availability>  </availability>

<publisher>  </publisher>
<pubPlace>  </pubPlace>
<date>  </date>
<idno>  </idno>
</publicationStmt></nowiki>
</pre>
</blockquote>

''' <publicationStmt> can be just a series of paragraphs or anonymous blocks: '''
<blockquote>
<pre>
<nowiki> <publicationStmt>
<ab>  </ab>
<ab>  </ab>
</publicationStmt></nowiki>
</pre>
</blockquote>

Oxford2013-Actions2

2014-01-11T03:59:27Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10)
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|was not implemented; have written code, but not tested sufficiently or checked-in
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-01-10T13:39:53Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10)
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|was not implemented; have written code, but not tested sufficiently or checked-in
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|[awaiting confirmation it has been documented.
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-01-10T12:48:53Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10)
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|was not implemented; have written code, but not tested sufficiently or checked-in
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|[awaiting confirmation it has been documented.
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-01-10T12:26:57Z

Syd: /* Actions for Syd Bauman */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10)
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|[awaiting confirmation it has been documented.
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Council agenda 2013-11

2013-11-10T23:44:15Z

Syd: /* Monday 11 November 2013 */

Map of locations: https://mapsengine.google.com/map/edit?mid=z5kNNI17e3DU.kEaB-XyBbZ-A

Open Google Doc Minutes at: https://docs.google.com/document/d/1F0pOZ5PkWvIfnPgAKCONRdrDZhl4dkig_zqCiPvUG8A/edit?usp=sharing

== Sunday 10 November 2013 ==
* Evening plans: From 6pm JamesC will be in The Royal Oak http://www.theroyaloakoxford.co.uk/ 42-44 Woodstock Road, Oxford, OX2 6HT
** And a good time was had by Kevin, Syd, Paul, Martin, and Martin’s brother Nick. Thank you, James; you’re a great pub-host!

== Monday 11 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
**Topics Including:
** EEBO TCP: Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)
*** <span style="color:navy;">Although the above link does have links to tickets and what I think is probably a set of summaries of particular problems, it does not provide a summary of '''the''' problem. Could someone (SR, JC, PS?) explain the big picture, here — what is the exact task (making sure EEBO TCP is TEI P5 conformant?), and why is it important?</span>
** Report on specification and estimated cost for XPointer resolver [HC/SB]
** Report on specification and estimated cost for oXygen front end for ODD [SB/EM]
* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Meeting Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** Pure ODD <span style="color:navy">is there a link for what pure ODD entails?</span>
** TEI Roma Replacement Specification
* 15:30 - 15:45 Break
* 15:45 - 17:30 SourceForge Tickets
* 19:00 -- "Sojo", Szechuan/Shanghainese/Cantonese restaurant, website at http://www.sojooxford.co.uk/ claims vegetarian menu on request. SoJo (Chinese) http://www.sojooxford.co.uk/ 6/9 Hythe Bridge Street, Oxford, OX1 2EW

== Tuesday 12 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
**Topics Including:
** Release Process (see below)
** Ideas on how to run an experimental TEI Hackathon [SR]
* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Dining Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]
** Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]
* 15:30 - 15:45 Break
* 15:45 - 17:30 SourceForge Tickets

* Evening: A meal chez Rahtz, 8pm directions and description to follow.

== Wednesday 13 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
** Cheatsheets: Short best/recommended practice documents
** From 09:30: Discussion with Torsten Schassan (via skype) about need for Object Description Chapter (see http://wiki.tei-c.org/index.php?title=Council_agenda_2013-11-OntologySIG)

* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Meeting Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** LingSIG Meeting and Modelling / Serializing standoff (c.f. http://sourceforge.net/p/tei/feature-requests/378/ )
** Terminology Chapter, TBX, and https://sourceforge.net/p/tei/feature-requests/482/
* 15:30 - 15:45 Break
* 15:45 - 16:30 SourceForge Tickets

*Evening -- The Rickety Press http://www.thericketypress.com, 67 Cranham Street, Oxford, OX2 6DE

== More Details on Agenda topics ==

* Discuss possible revisions to [http://www.tei-c.org/Activities/Council/Working/tcw22.xml#releaseSteps step-by-step instructions in release procedure]
** Should step 1 (creating P5/ReleaseNotes/readme-X.X.X.xml) happen at the same time as step 4 (freeze on commits)?
** Should we do steps 1 through 5 farther in advance so we can check that the version numbers etc. show up in the right places in files resulting from the build process?
** Immediately after a release, should we change the version number in the repository to next release number (e.g., "2.5a", with "a" for "alpha") so people won't be confused looking at the last successful build and seeing the old version number. Then immediately before a release, when we put out the call to TEI-L to look for typos, we can change the "a" to "b" (e.g., "2.5b") and then when we actually release, remove the "b".
** Should we have the date of a build be auto-generated? It will make it clearer that people are looking at something that's evolving, and it will also make it easier to diagnose the occasional case where one of the Jenkins servers stops updating.
* [https://sourceforge.net/p/tei/feature-requests/378/?page=2 proposals for <standoff>] -- have Javier join the discussion?

* i18n: how to take forward updating of the translations

* Development of Pure ODD [LB and SR]. See paper at http://tei.oucs.ox.ac.uk/Talks/2013-09-acmdoceng/rahtzburnard.pdf and the code at https://github.com/TEIC/pureodd

* Ideas on how to run an experimental TEI Hackathon [SR]

* Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]

* Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)

* Report on new Roma Specification [JC]

* Report on specification and estimated cost for XPointer resolver [HC/SB]

* Report on specification and estimated cost for oXygen front end for ODD [SB/EM]

* Cheatsheets: Short best/recommended practice documents

* Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]

Council agenda 2013-11

2013-11-10T23:32:52Z

Syd: /* Sunday 10 November 2013 */ yup, we met at the pub

Map of locations: https://mapsengine.google.com/map/edit?mid=z5kNNI17e3DU.kEaB-XyBbZ-A

Open Google Doc Minutes at: https://docs.google.com/document/d/1F0pOZ5PkWvIfnPgAKCONRdrDZhl4dkig_zqCiPvUG8A/edit?usp=sharing

== Sunday 10 November 2013 ==
* Evening plans: From 6pm JamesC will be in The Royal Oak http://www.theroyaloakoxford.co.uk/ 42-44 Woodstock Road, Oxford, OX2 6HT
** And a good time was had by Kevin, Syd, Paul, Martin, and Martin’s brother Nick. Thank you, James; you’re a great pub-host!

== Monday 11 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
**Topics Including:
** EEBO TCP: Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)
** Report on specification and estimated cost for XPointer resolver [HC/SB]
** Report on specification and estimated cost for oXygen front end for ODD [SB/EM]
* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Meeting Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** Pure ODD
** TEI Roma Replacement Specification
* 15:30 - 15:45 Break
* 15:45 - 17:30 SourceForge Tickets
* 19:00 -- "Sojo", Szechuan/Shanghainese/Cantonese restaurant, website at http://www.sojooxford.co.uk/ claims vegetarian menu on request. SoJo (Chinese) http://www.sojooxford.co.uk/ 6/9 Hythe Bridge Street, Oxford, OX1 2EW

== Tuesday 12 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
**Topics Including:
** Release Process (see below)
** Ideas on how to run an experimental TEI Hackathon [SR]
* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Dining Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]
** Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]
* 15:30 - 15:45 Break
* 15:45 - 17:30 SourceForge Tickets

* Evening: A meal chez Rahtz, 8pm directions and description to follow.

== Wednesday 13 November 2013 ==
* 09:00 - 10:30 Morning Discussion Session
** Cheatsheets: Short best/recommended practice documents
** From 09:30: Discussion with Torsten Schassan (via skype) about need for Object Description Chapter (see http://wiki.tei-c.org/index.php?title=Council_agenda_2013-11-OntologySIG)

* 10:30 - 10:45 Break
* 11:45 - 12:30 SourceForge Tickets
* 12:30 - 14:00 Lunch Break (in Meeting Room)
* 14:00 - 15:30 Afternoon Discussion Session
**Topics Including:
** LingSIG Meeting and Modelling / Serializing standoff (c.f. http://sourceforge.net/p/tei/feature-requests/378/ )
** Terminology Chapter, TBX, and https://sourceforge.net/p/tei/feature-requests/482/
* 15:30 - 15:45 Break
* 15:45 - 16:30 SourceForge Tickets

*Evening -- The Rickety Press http://www.thericketypress.com, 67 Cranham Street, Oxford, OX2 6DE

== More Details on Agenda topics ==

* Discuss possible revisions to [http://www.tei-c.org/Activities/Council/Working/tcw22.xml#releaseSteps step-by-step instructions in release procedure]
** Should step 1 (creating P5/ReleaseNotes/readme-X.X.X.xml) happen at the same time as step 4 (freeze on commits)?
** Should we do steps 1 through 5 farther in advance so we can check that the version numbers etc. show up in the right places in files resulting from the build process?
** Immediately after a release, should we change the version number in the repository to next release number (e.g., "2.5a", with "a" for "alpha") so people won't be confused looking at the last successful build and seeing the old version number. Then immediately before a release, when we put out the call to TEI-L to look for typos, we can change the "a" to "b" (e.g., "2.5b") and then when we actually release, remove the "b".
** Should we have the date of a build be auto-generated? It will make it clearer that people are looking at something that's evolving, and it will also make it easier to diagnose the occasional case where one of the Jenkins servers stops updating.
* [https://sourceforge.net/p/tei/feature-requests/378/?page=2 proposals for <standoff>] -- have Javier join the discussion?

* i18n: how to take forward updating of the translations

* Development of Pure ODD [LB and SR]. See paper at http://tei.oucs.ox.ac.uk/Talks/2013-09-acmdoceng/rahtzburnard.pdf and the code at https://github.com/TEIC/pureodd

* Ideas on how to run an experimental TEI Hackathon [SR]

* Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]

* Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)

* Report on new Roma Specification [JC]

* Report on specification and estimated cost for XPointer resolver [HC/SB]

* Report on specification and estimated cost for oXygen front end for ODD [SB/EM]

* Cheatsheets: Short best/recommended practice documents

* Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]

TEI-Council-FAQ

2013-11-02T15:00:10Z

Syd: /* How is the TEI Technical Council Chair elected? */

So you have some questions about how the [[Council|TEI Technical Council]] works? This page has been set up to answer questions that new council members (or other curious parties) may have.

== Overview ==

=== How does the Council do its work? ===

By every means possible. These include regular telephone conferences, endless streams of email, widely circulated discussion documents, private caucussing, public debate in other contexts such as TEI-L, and private gossip. Formally speaking, the Council meets face to face once a year (at least), and many more times than that virtually.

=== And what work does it do? ===

You should probably review the recent official work of the Council by reading the last few sets of minutes: http://www.tei-c.org/Council/ has an index page which links to them all (when we remember to update it). The minutes record topics discussed and responsibilities allocated at the Council level. Of course many Council members are also active in subgroups (formal or informal) of the Council or SIGs, which may be documented elsewhere as well.

Generally, things in Council work like this:

# A bug report or feature request is reported by anyone in [http://tei.sourceforge.net/ SourceForge].
# Sometimes others notice the ticket and comment on it.
# Sometimes a Council member may make an executive decision on the ticket. If it's a corrigible error or bug, we can just fix it in the appropriate ODD file(s) (also in SourceForge Subversion). If it is not a real issue, sometimes the ticket will just be closed. If you do not have developer access on sourceforge you'll need to ask someone who does to re-open the ticket if you want to raise it again. Otherwise, it's discussed either by email on the Council mailing list or at a Council meeting (conference call or in-person meeting). Comments are recorded in the ticket reflecting the decision reached, and changes are made in SourceForge by a member of the Council sometime thereafter.
# The change shows up on tei-c.org after the next TEI "release", which happens about two or three times a year.

However, Council does sometimes consider lengthy proposals circulated to Council outside of SourceForge and vote on them as packages, with the changes grouped together in a sensible way so they can be considered in smaller packages, or with the changes listed individually.

=== And what is its scope? ===

The Council's primary responsibility is to act as technical watchdog for the intellectual content of the TEI Guidelines. That is to say: it has the final say in just about every aspect of the TEI encoding scheme -- what elements exist in it, what they are called, how they should be used.

=== How do I join the TEI Council mailing list? ===

We have had the practice on the Council so far that elected members get added immediately to the list (and to the telecon, if there is one), with every right to participate, while outgoing members stay on until the end of their term. To join or discuss any problems using the list contact the [mailto:tei-council-owner@lists.village.virginia.edu TEI Council mailing list owner], currently this is David Sewell in Virginia. There is also a board-council mailing list to which you should be added as well.

=== Why are some people on the Council email list or attending Council meetings even though they are not on the list of elected members? ===

In addition to the members of the Council, the chair of the TEI Technical Council may invite others not elected to the Council to meetings (e.g. to speak to a particular issue). Historically the Council has also invited a representative of the Board to the Council mailing list and meetings. Currently, this is Lou Burnard as non-voting board representative. The TEI-C Webmaster (currently David Sewell) is also on the mailing lists.

=== What are the various job roles on the TEI Council? ===

==== TEI Technical Council Member ====
A TEI Technical Council Member is expected to participate in all aspects of Council work. This means that they should learn how the TEI infrastructure is organised and [http://www.tei-c.org/Activities/Council/Working/tcw20.xml how to edit the TEI Guidelines], asking on the Council list any questions they might have. They will be expected to come to face-to-face ("f2f") meetings (often two per year) and participate in a couple other teleconferences per year. They will be assigned (or take) feature requests/bugs on [http://tei.sourceforge.net/ the TEI's SourceForge site], for which they will be in charge of encouraging discussion, reporting on the issue to Council, and eventually implementing (or ensuring implementation) of the resulting decision. A TEI Technical Council Member is expected to participate in the maintenance and development of the TEI Guidelines and related outputs. Some elected TEI Council members focus more on particular aspects of the infrastructure or stylesheets as part of the contribution to the Council. Council members should always act to represent what they believe are the opinions and best interest of the community that has elected them.

==== TEI Technical Council Chair ====
The TEI Technical Council Chair's role is to administrate and facilitate the work of the TEI Technical Council. If all of the Council are the elected servants of the community, then the Council Chair is the servant of the servants of the TEI (''Servus servorum TEI''). The duties of the Technical Council Chair include (in no particular order):
* ensuring the delivery and maintenance of the Guidelines
* arranging for Council members to actively participate in Council activities
* arranging and chairing the face-to-face meetings (in conjunction with the local organiser)
* arranging and chairing the teleconferences
* assigning tickets in [http://tei.sourceforge.net/ the SourceForge system]
* acting as SIG coordinator
* liaising for and reporting on Council activities at all Board meetings
* reflecting Council wishes in Board discussions
* budgeting Council expenses,
* acting as a public point of contact and responding to technical enquiries (messages to council@tei-c.org are forwarded to the Council Chair)
* announcing new releases of the Guidelines on the TEI-L mailing list
* ensuring the smooth running of the TEI Technical Council

The TEI Technical Council Chair is also a member of the Council, so has all the duties and obligations of being a council member as well.

==== Release Technician ====
The TEI Guidelines release process (see [http://www.tei-c.org/Activities/Council/Working/tcw22.xml tcw22: Building a TEI Release]) involves a single individual responsible for 'pushing the button' and completing the steps required to make a TEI Guidelines release live. This is not a standing position; instead, the responsibility rotates for every release in order to demystify the release process and spread the expertise beyond Oxford staff. Although we have documented the work in quite a detailed manner, it is a non-trivial process and involves a fair degree of work. A release technician is usually required to set aside a whole day for the release process since history teaches us that often the entire process needs to be re-run to correct last-minute errors.

==== TEI-C Webmaster and Assistant Webmaster ====

The TEI-C Webmaster and Assistant Webmaster are not officially part of the Council but may be added to the mailing lists at the discretion of the Council Chair. They are responsible for the smooth running of the TEI-C Website.

=== How is the TEI Technical Council Chair elected? ===

The [http://www.tei-c.org/About/bylaws.xml#body.1_div.3_div.3 Bylaws of the TEI-C] say that:
<blockquote>
The Chair of the Technical Council shall be elected by the voting Members of the TEI-C Technical Council from its membership and shall serve as the chief technical officer of the Consortium. If no Technical Council Member is able or willing to assume the chair, the Technical Council may request the Board of Directors to second one of its elected members to the role, or it may nominate a non-elected individual.
</blockquote>
This leaves it intentionally vague as to the precise process the TEI Technical Council will follow. For now there is vague consensus that they will do something like the following. Note that timeframes below are not intended to be ridig or precise, but rather to be suggestive.
# The new Technical Council Members will be added to the tei-council (and board-council) mailing lists shortly after the members' meeting. Up until the last last Friday in November those who are Council members for next year will consider whether they want to run to be Chair of the TEI Technical Council. The current Chair will facilitate this process by answering any questions about the post. Before that date those intending to stand should send a statement of some sort to the Council mailing list detailing why they think the council members should vote for them.
# On the first weekday of December if only one person is running then the Chair will announce this to the tei-council mailing list as an acclamation (and after a short period for objections, to the Board and TEI-L). If multiple people are running, then the Council Chair will appoint a "returning officer" who is not a member of the incoming Council (i.e., not a voter and thus at least a somewhat disinterested party). The returning officer will set up an electronic voting system with the names of the candidates. This should be a private election with no one able to determine who has voted for who. E.g. if using opavote.org this should have the following settings: Results only shown at end, "Instant Runoff Voting" method, a single winner, "ranked enhanced" ballot type, and candidate order shuffled.
# The returning officer should ensure the election runs for at least 4 days in early December after announcing it on the tei-council mailing list (and distributing ballots depending on the system).
# The results will be announced publicly on the tei-council mailing list, and Council members given a brief chance to raise any objections with the election before the current Chair informs the Board and announces it more publicly on TEI-L.
# The new Chair assumes the role on January 1st. The current chair steps down on December 31st. The outgoing and incoming chairs should co-ordinate activities between the election and January 1st so as to ensure a smooth transition. (Remembering that the current Chair might be departing off council at the end of that year.)

== Terminology ==

=== What was the War on Free-text-bearing Attribute Values? ===

The War on Free-text-bearing Attribute Values, also known as the War on Free-text-bearing Attributes and the War on Attributes for short, happened because some have felt that if attribute values don't have a datatype, they are more prone to abuse than if they did. So there has been an effort to give datatypes to as many attributes as possible. Some discussion of this with respect to @rend is available here: http://blogs.oucs.ox.ac.uk/jamesc/2011/12/01/rend-and-the-war-on-text-bearing-attributes/

=== What is the "Birnbaum doctrine"? ===

As expressed in [http://www.tei-c.org/Activities/Council/Working/tcw09.xml TCW09: Backward Compatibility and the Maintenance of the Text Encoding Initiative Guidelines], we should avoid breaking backward compatibility and only do so after serious consideration. It does not mean that we cannot break backwards compatibility, just that we've agreed a set of steps to take when we do so.

=== In what ways will Council break backwards compatibility? ===

For an egregious error, we might actually change a content model immediately. More often, we will survey the community on TEI-L before doing so, and we might [[Practices no longer recommended or now deprecated|deprecate]].

=== What is the "Durand Conundrum"? ===

The "Durand Conundrum" was suggested by David G. Durand concerning the TEI's decision to use the [[ODD | TEI ODD]] meta-schema language rather than just one of the existing schema languages. Given that we decided to use our own language, why use RelaxNG as part of that language for describing content models? Generally, the consensus is that [[ODD | TEI ODD]] gives us greater power and flexibility than any individual schema language can do in that we can model things that those schema languages are currently unable to cope with. TEI ODD gives the ability for a single document to produce both documentation and schema since these are inherently interlinked. It also keeps the TEI honest, in requiring it to use its own system to document schemas. [[ODD | TEI ODD]] does currently have some problems, a few of which are detailed at [[ODD-dev]] and successive revisions of TEI ODD are intended to solve some of these.

=== What is a "magic token"? ===

This is an value, usually an attribute value, such as that of @key or @rend, which does not follow a standard outside vocabulary but instead is understood in some undocumented way and often used for local processing. It should usually be explained in the teiHeader if possible. Having any processing rely on undocumented magic tokens is generally considered a bad idea. See also [http://en.wikipedia.org/wiki/Magic_cookie Magic Cookie].

=== What is a non-deterministic content model? ===

If you have a content model for <tt><a></tt>:

<code>
b*, c?, b*
</code>

and you have a document with:

<pre>
<a>
<b/>
</a>
</pre>

then a parser can't tell whether the <tt><b/></tt> matches the first <tt>b*</tt> or the second <tt>b*</tt> in the content model. Thus, the content model itself is called “non-determinstic”. DTDs and W3C XML Schemas reject non-deterministic content models. Thus, if we were to create one in the TEI, validation with DTD and XSD would fail due to errors ''in the schema'', regardless of whether the instance document has an occurence that is non-deterministic or not.

=== What are Janus elements? ===

These are pairs of elements that are in a sense two sides of the same coin, such as orig and reg, corr and sic, abbr and expan.

=== What does "no magic" mean? ===

'Magic' in the sense sometimes used in Council discussion refers to pre-existing or special knowledge required to process something. For example, it was only by 'magic' that a TEI ODD processor would know to add attributes from the att.global attribute class to elements until this was changed to make all element specifications have to explicitly claim membership in this class if they wanted the global attributes. Knowing to add them was 'magic', and in general it is better if any requirements or understood knowledge is explicitly documented.

=== What does it mean to say that elements tessellate? ===

This means that all textual content is included in exactly one instance of an element. For example, once you start using divs (numbered or unnumbered), all text thereafter must be inside of one of the divs: you can't start using p elements that are not wrapped in a div.

In the Guidelines this is sometimes referred to as end-to-end segmentation.

== Meetings ==

=== Where are the minutes of previous meetings? ===

Minutes are [http://www.tei-c.org/Activities/Council/Meetings/index.xml archived on the TEI website]. Interim states of minutes may at times live in this wiki, Google Docs, or elsewhere.

=== How are the teleconferences held? ===

Currently the TEI Council uses the teleconferencing facilities provided by commercial provider since this has proved most cost effective with less problems than other VOIP-based solutions. This has 800/free call numbers for most countries, and low-cost for some. This will be set up by the Council Chair in advance and details posted to the list.

The specific details of what number to dial and what access code is needed will be circulated on the council list shortly before the meeting.

=== What funding is available for Council Activities? And how do I get reimbursed? ===

The TEI funds the participation of the council members in the meetings. Though I don't know of anyone claiming back telephone conferencing costs, I suppose that is possible as well, in most cases the council members' institutions probably swallow that.

If the council has a meeting, then the council members' travel, hotel, etc. will be reimbursed with proper receipts. The TEI reimburses all reasonable expenses in keeping with standard practice at most universities and granting agencies. We cover meals, travel, lodging, and other common daily travel expenses. Airfare should be economy class and direct return, unless otherwise arranged with the Treasurer prior to your trip. (See [http://www.tei-c.org/Board/procedures.xml#body.1_div.8 draft reimbursement policies and procedures].) If you have questions about reimbursement procedures, including what is reimbursable, please email John Unsworth, the TEI treasurer, at unsworth AT brandeis.edu.

Use the TEI Travel expense form available here: http://www.tei-c.org/Admin/TEI_travel_form.pdf '''Expense forms should be submitted within 10 days of the end of the meeting.'''

Council members are not funded to attend the TEI Members' Meeting, however, there has been discussion concerning whether the council should also officially meet here as well.

== How we get work done ==

=== How can I get straight to certain tickets in SourceForge? ===

SourceForge divides all tickets into "bugs" and "feature requests". You must browse them separately. You can browse all in a given category from the links at http://tei.sourceforge.net/ .

Before we upgraded to the new Allura system on SourceForge for our tickets, tickets had old, ugly URLs. To get around using these, we set up short URLs maintained by James Cummings and others, which which you could append the attribute ID to the end of the appropriate one of the two URLs where it says 'NUMBER' in order to reach the right ticket:

<nowiki>
http://purl.org/TEI/bug/NUMBER
http://purl.org/TEI/FR/NUMBER
</nowiki>

The new URLs are much more human readable and so those should now be used in preference. Some legacy documents may still use the old PURL URLs.

=== I have something to say about a SourceForge Feature Request or Bug: Should I comment on the ticket or the TEI Council mailing list? ===

There is no hard-and-fast policy on this. The mailing list is a better place for ongoing discussions where people are arguing back and forth during decision making. The SourceForge tracker is the appropriate place to record opinions, positions, and decisions for posterity, especially if such would help a) whoever is implementing the decisions recorded in the ticket, b) anyone revisiting this decision later to retrace the thinking. The TEI Council mailing list archives are public, so if substantial discussion has taken place there (or indeed on TEI-L), this can also be linked to from the ticket.

=== When is discussion on an element or topic "closed" and how do I know? ===

Any topic can be revisited at any point, even in the published guidelines, through posting a feature request on sourceforge. Council-specific issues should be raised on the council mailing list, after having reviewed any previous discussion on the topic in the [http://lists.village.virginia.edu/pipermail/tei-council/ council mailing list archives].

=== How can I find out about every time a ticket is created or commented on? ===

Two options:

* By RSS: Subscribe to an [http://sourceforge.net/export/rss2_keepsake.php?group_id=106328 RSS feed that includes new tickets and comments on existing ones]
* By email:
*#Create a SourceForge user, or log in to an existing account.
*# Make sure you have joined the TEI project.
*# Click the "monitor" button at https://sourceforge.net/tracker/?group_id=106328&source=navbar to receive an email for each change <em>(but what exactly does this include?)</em>

=== How are tickets assigned in SourceForge? ===
All members of Council are made 'developers' on the SourceForge TEI Project and meant to take an active role in the development and maintenance of the TEI Guidelines. This means that they have write access to the TEI Guidelines Subversion Repository, and tickets can be assigned to them in the ticket trackers. They can also update and modify tickets. This means that Council members are free to 'take' tickets which they wish to oversee. Other Council members can also 'give' tickets to each other if they think someone particularly suited to overseeing a particular ticket. (However, usually they should have the Council member's permission to do so.) On a regular basis the Council Chair will assign tickets to Council members, if a ticket gets assigned to them that they don't want to do they should tell the Chair and/or ask other Council members to swap.

=== What does Red, Amber, and Green mean in classifying a ticket? ===

* '<span style="color:red; font-weight:bold;">Red</span>' means that the ticket has not been discussed sufficiently and that the answer to it is not necessarily clear. There needs to be more discussion, more examples, use cases, and possibly a clearer proposal about what specifically needs to be done. Or possibly, the ticket does have these things but Council has not yet discussed it or enough Council members seen it for it to warrant an 'Amber' status.

* '<span style="color:orange; font-weight:bold;">Amber</span>' means that the ticket has been discussed and/or there may be some general consensus on what the correct thing to do is, but necessary components are missing. It may be some examples, use-cases, or prose are missing. Or there is a question of which of several possible solutions is the correct one.

* '<span style="color:green; font-weight:bold;">Green</span>' means that the ticket has been discussed, there is general consensus on what the correct thing to do is, and it has been assigned for someone to ensure its implementation.

=== How does a TEI release happen? ===

The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw22.xml

== Working in SourceForge ==

=== How do I edit the TEI Guidelines? ===

Editing the TEI Guidelines is a complex process and the Council has produced a document http://www.tei-c.org/Activities/Council/Working/tcw20.xml covering the logical and physical layout of the Guidelines, stylistic notes, how to make a change to the Guidelines (it requires [[TEI-Council-FAQ#How_do_I_use_Subversion.3F|using subversion]], building a release, and a reference section of useful information. If any information you need isn't in this document, ask on the Council list and get someone to update it!

=== How can I find out about every time a change is made in the TEI subversion repository? ===

# Go to https://lists.sourceforge.net/lists/listinfo/tei-notify .
# Subscribe under your SourceForge email address (which you can find at http://sourceforge.net/project/memberlist.php?group_id=106328 ).

=== How do I use Subversion? ===

The TEI stores its working files in the TEI Sourceforge Subversion Repositories, with read access to anyone who wishes. See the [http://www.tei-c.org/Guidelines/P5/get.xml instructions]. Write access is reserved for those who are developers on the SourceForge project. To request developer status, contact one of the project admins, whose usernames are given in bold on [http://sourceforge.net/project/memberlist.php?group_id=106328 the SourceForge list of users].

Note that you will have to enter your password each time you access Subversion. A way around this (which causes a security risk) is to create a public/private key pair based on no passphrase and upload your public key to SF. There is a [http://www.linuxproblem.org/art_9.html description of how this process works in general], and [https://sourceforge.net/p/forge/documentation/SSH%20Keys/ some hard-to-follow instructions specific to SourceForge].

=== What should I put in a Subversion commit message? ===

It is beneficial to all those looking at the TEI Subversion repository if commit messages are clear and detailed. This is especially true when trying to revert changes made by yourself or others to solve problems. A good commit message will include:
* an explanation to a useful level of detail about what you did
* a mention of why this is being done
* the SourceForge ticket numbers (or shortened urls) that relate to the change if applicable
* an explanation of whether this change is completing the work described or one step towards doing so.

== TEI website ==

=== I want to add a document to add meeting minutes, reports, or working papers to the TEI-C website. How do I do that? ===

The TEI webmaster(s) -- currently David Sewell, with assistance from Kevin Hawkins -- have access to the CMS behind the TEI website. The site uses a stylesheet to render TEI Lite documents in XHTML, though the CMS can also deliver non-TEI documents. However, for long-term preservation and consistency, use of TEI Lite is encouraged.

You can author a document from scratch or take an existing document as a starting point. To get the XML source of an existing document, simply click "XML View" in the footer of a page on the TEI-C website and choose "save as" in your browser.

The TEI has a longstanding naming convention for files that consists of:

# a short alphabetical abbreviation for a committee (such as "tc" for "Technical Council")
# a one-letter abbreviation for minutes ("m"), reports ("r"), or working papers ("w")
# a two-digit number for the document with a committee series, numbered sequentially (e.g., "tcw01" is the first working paper from the Technical Council, "tcm05" is the fifth minutes from the Technical Council, etc.)

There is no registry of documents, so when creating a new one, you simply name the file appropriately.

Send the file to a webmaster for putting online. If you are hesitant to have the page go live until you have previewed it, you can ask the webmaster to send you a derived HTML version using the stylesheets without publishing that document.

=== How do I get access to the Google Analytics Data for www.tei-c.org? ===

Email the TEI-C webmaster: web@tei-c.org.

== Miscellaneous ==

=== Why do some elements have @type and others do not? ===

The TEI has avoided adding @type to elements because its availability is thought to invite tag abuse. One principle used by the Technical Council is that if an element is repeatable and is something for which there can be different classifications, it should have @type.

== I have a question! ==

Then add it just above this one or email someone on the council or the council list reminding them of the existence of this wiki page when you ask your question.

[[Category:Council]]

Talk:TEI-Council-FAQ

2013-11-02T14:57:43Z

Syd: /* Elections */

== Elections ==

Shouldn't "This should be a private election with no one able to determine who has voted for who" end with "whom"?

== Durand Conundrum ==

I'm told there's something called the "Durand Conundrum". Though it hasn't yet come up in Council discussions, it would be good to add a note on the TEI-Council-FAQ because I don't think there's any more appropriate place to put this. ([[User:kshawkin|kshawkin]] 15 April 2010)

: Thanks, James, for adding. I think I understand the Conundrum now, but still this sentence doesn't quite parse: "The 'Durand Conundrum' was suggested by David G. Durand concerning the TEI's decision to use the [[ODD|TEI ODD]] meta-schema language rather than just one of the existing schema languages, or if you are going to use your own language, why use RelaxNG as part of that language for describing content models." I propose revising as:

: The "Durand Conundrum" was formulated by David G. Durand and actually contains two conundrums:

:* Why does the TEI use the [[ODD|TEI ODD]] meta-schema language rather than simply using one of the existing schema languages?
:* Why does our meta-schema language use RelaxNG as part of that language for describing content models?

: ([[User:Kshawkin|Kshawkin]] 15:04, 18 March 2012 (EDT))

Talk:TEI-Council-FAQ

2013-11-02T14:57:23Z

Syd:

== Elections ==
Shouldn't "This should be a private election with no one able to determine who has voted for who" end with "whom"?

== Durand Conundrum ==

I'm told there's something called the "Durand Conundrum". Though it hasn't yet come up in Council discussions, it would be good to add a note on the TEI-Council-FAQ because I don't think there's any more appropriate place to put this. ([[User:kshawkin|kshawkin]] 15 April 2010)

: Thanks, James, for adding. I think I understand the Conundrum now, but still this sentence doesn't quite parse: "The 'Durand Conundrum' was suggested by David G. Durand concerning the TEI's decision to use the [[ODD|TEI ODD]] meta-schema language rather than just one of the existing schema languages, or if you are going to use your own language, why use RelaxNG as part of that language for describing content models." I propose revising as:

: The "Durand Conundrum" was formulated by David G. Durand and actually contains two conundrums:

:* Why does the TEI use the [[ODD|TEI ODD]] meta-schema language rather than simply using one of the existing schema languages?
:* Why does our meta-schema language use RelaxNG as part of that language for describing content models?

: ([[User:Kshawkin|Kshawkin]] 15:04, 18 March 2012 (EDT))