TEIWiki - User contributions [en]

Oxford2013-Actions2

2013-11-21T21:51:28Z

Brettttt: /* Actions for Brett Barney */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from 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.
|
|-
|[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/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|
|-
|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.
|
|-
|[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.
|
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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/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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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].
|
|-
|[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.
|
|-
|[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.
|
|-
|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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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/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].
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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].
|
|-
|[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].
|
|-
|[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.
|
|}

===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.
|
|-
|[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].
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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].
|
|}

===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
|
|
|-
|[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.
|
|-
|[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.]
|
|-
|[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.
|-
|i18n: take forward updating translations

|MH
|MH to get contact info on original groups and activate if possible, probably starting with French and Italian
|
|-
|[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
|-
|[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/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.
|
|-
|[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.
|Emailed GB 2013-11-21
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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.
|
|-
|[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
|-
|[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].
|
|}

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

Text Directionality Draft

2013-11-13T00:19:02Z

Brettttt: /* Boustrophedon */

This is a preliminary draft of proposed sections for the TEI Guidelines, created by the [[Text Directionality Workgroup]]. Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions. There is also a [[Talk:Text_Directionality_Draft|talk page]] for more informal discussion.

==Text directionality and transformation==

===Introduction===

Scripts used for writing human languages vary not only in the glyphs they use, but also in the direction in which these glyphs are to be read. The majority of modern languages are written from left to right within the line, and have their lines stacked from top to bottom vertically (English, Russian, Greek), but there are several widely-used scripts which run right-to-left (Arabic, Hebrew), while also stacking lines top-to-bottom. Some east Asian languages such as Japanese and Chinese can be written with the same directionality as English, but are often also written from top to bottom within the line, with their lines sequenced from right to left. There are a few cases of bottom-to-top writing, such as Ancient Berber, and some Ogham inscriptions; there are even instances of writing which changes direction on alternate lines (boustrophedon, discussed in detail below).

When a language or script can be arranged in two or more different directions, there are often other consequences arising out of the choice; for example, when Japanese is written horizontally, the Unicode character U+3001, the "ideographic comma", is used, whereas in vertical writing an alternative glyph, U+FE11, may be used to ensure that the comma appears in the correct position relative to the surrounding glyphs. In addition, scripts which normally have a single directionality (such as English) may be written in a different direction in the context of another language (English words inserted into vertical Chinese text, for example), or in response to layout constraints such as those imposed by a complex table, in which column or row labels may be written vertically to make the most effective use of available space.

The directionality features of scripts, and the consequences arising out of them, are generally referred to as "writing modes". For many documents encoded in TEI, there may be no need to encode any information relating to writing mode, because it will be obvious. Modern printed texts in most European languages, for instance, may be expected to use left-to-right/top-to-bottom directionality; Arabic or Hebrew texts are expected to run right-to-left/top-to-bottom. It may appear that directionality can be reliably deduced from the language and script settings, and these are probably already encoded using the @xml:lang attribute in TEI documents (although the W3C i18n Working Group recommends against reliance on language tags for encoding directionality information [per Richard Ishida, W3C; I need to find a formal reference for this]). Even in the case of many "mixed mode" documents (documents in which languages or scripts with different writing modes are mixed together), it may not be necessary to be explicit about directionality. Consider the case of an English text containing a few Arabic words--what is termed a "bidirectional" text:

<code>The Arabic term قلم رصاص means "pencil".</code>

Since Arabic is always written from right to left, we can assume that the Arabic glyphs are to be read in that direction, even if they are in the context of a left-to-right English sentence. In fact, most codepoints in the Unicode standard have a specific directionality setting which helps any rendering engine to determine how they should be ordered. The Latin glyph "a" has a bidirectionality setting of strong left-to-right; the Hebrew א (alef) is strongly right-to-left. Other glyphs have weak or neutral settings because of the contexts in which they may appear. The Unicode Bidirectional Algorithm (http://www.unicode.org/reports/tr9/) provides a complex series of rules enabling user agents to render most mixed-mode texts with predictable and reliable results, based on the bidirectionality class values of their glyphs.

In some mixed-mode texts, though, the Bidirectional Algorithm may not give the desired results. To deal with this, Unicode provides a set of "directional formatting characters" (http://www.unicode.org/reports/tr9/#Directional_Formatting_Codes), also called "bidi formatting code characters", which are additional codepoints whose only function is to signal to a user-agent that a specific directionality setting should be turned on or off. These can be inserted into a text to influence the outcome of the bidirectional algorithm. However, in the case of documents encoded in XML, the W3C explicitly advises that markup rather than directional formatting characters should be used ("In (X)HTML and XML do not use the paired Unicode bidi formatting code characters where equivalent markup is available," http://www.w3.org/International/questions/qa-bidi-controls). We concur with this recommendation, and the remainder of this section and the next provide a set of encoding strategies for handling text directionality without the use of directional formatting characters. The approach we recommend is based on two external specifications, in line with our normal practice of incorporating existing standards where they are available and appropriate. Those specifications are the CSS Writing Modes module (http://dev.w3.org/csswg/css-writing-modes/) and the CSS Transforms module (http://www.w3.org/TR/css3-transforms/). Since (at the time of writing) neither of these modules has yet reached the stage of a Recommendation, the advice offered below should be regarded as provisional, and you should check your usage of the properties concerned against the current version of each specification where possible.

The following sections will present a few simple examples of phenomena relating to text directionality and transformation, along with some suggested encoding strategies based on the following CSS properties from CSS Writing Modes:

<code>
direction: ltr | rtl<br/>
writing-mode: horizontal-tb | vertical-rl | vertical-lr<br/>
text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation<ref>The value "use-glyph-orientation" may be dropped from the CSS Writing Modes specification.</ref><br/>
unicode-bidi: normal | embed | isolate | bidi-override | isolate-override | plaintext
</code>

along with the <code>transform</code> property from CSS Transforms.

In the following examples, CSS rules are encoded in the global TEI @style attribute, which applies them directly to the element on which they are specified (and in most cases, its descendants). It is also appropriate, and will often be more efficient, to express the rules in TEI <rendition> elements in the <teiHeader> and point to them using @rendition attributes. It should also be remembered that the CSS specifications are written primarily to guide users providing instructions for the rendering of digital texts, and implementers creating user-agents which will act on these instructions. However, our usage in the context of a TEI document is primarily ''descriptive'' rather than ''prescriptive''; we are typically describing the features of a text we are encoding, rather than providing instructions for rendering it. Our purpose below is not to enumerate an exhaustive set of strategies for encoding any writing mode feature you may encounter; rather we will show some simple examples which serve as an introduction to the topic.

===Text directionality===

====Horizontal directionality====

Returning to our previous simple example

<code>The Arabic term قلم رصاص means "pencil".</code>

we could use the <code>direction</code> property to make directionality explicit:

<code>direction: ltr | rtl</code>

<syntaxhighlight lang="xml">
<seg xml:lang="en" style="direction: ltr">The Arabic term </seg>
<seg xml:lang="ar" style="unicode-bidi: embed; direction: rtl">قلم رصاص</seg>
<seg xml:lang="en" style="direction: ltr">means "pencil".</seg>
</syntaxhighlight>

The use of the <code>direction</code> property is straightforward, but the <code>unicode-bidi</code> property requires some explanation. These three segments are all inline; they form part of a single sentence, although they happen to be encoded on separate lines in this example. The default value for <code>unicode-bidi</code> is "normal", and the CSS Writing Modes specification stipulates that the <code>direction</code> property "has no effect on bidi reordering when specified on inline elements whose unicode-bidi property’s value is normal, because the element does not open an additional level of embedding with respect to the bidirectional algorithm." In other words, if we want to make it clear that the <code>direction</code> property is effective here, we must include a value for <code>unicode-bidi</code> which will make it so.

However, as mentioned above, all of the directional encoding in this example is superfluous; ambiguity does not arise in this particular case. Moreover, "ltr" is the default value for the <code>direction</code> property, so we do not need to specify it for the English segments. However, consider the following example, contributed by Efraim Feinstein, in which Hebrew and English text are mixed. (This example is presented in the form of graphics, because we cannot rely on user agents that may be rendering or displaying these Guidelines to provide a consistent output.)

[[File:En he embedding.png|800px]]

Here, an English period appears in between two runs of Hebrew text. Should that period be interpreted as part of a single run of right-to-left text, or should it be deemed to terminate the first run and precede the second? For the Unicode Bidi Algorithm, punctuation is not strongly directional; it inherits directionality from the surrounding characters. Without further clues, therefore, it would interpret the example as a sequence of three runs (English, Hebrew, English), and arrive at an incorrect interpretation. A clear and correct interpretation requires that not only that the glyphs themselves be transcribed in the correct logical order, but that the encoding eliminate potential ambiguity by delimiting the two Hebrew runs separately, like this:

<syntaxhighlight lang="xml">
<p>
Here's a sentence that begins in English
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ויש מלים בעברית והפסק</seg>.
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ועוד מלים בעברית</seg>
and it continues in English.
</p>
</syntaxhighlight>

Here the English is unmarked for directionality, but the period is clearly not included in either of the RTL runs, so the ambiguity inherent in the plain text is avoided. Once again, we might argue that the <code>@xml:lang</code> attribute should provide enough information; the important component here is the explicit delimitation of two distinct RTL runs. But additional clarity in the encoding certainly does no harm.

[Would it be helpful to have another example presenting ambiguity arising out of the use of a g element at the end of a text run?]

====Vertical writing modes====

So far, we have looked only at left-to-right and right-to-left text running horizontally, using the <code>direction: ltr|rtl</code> property. However, there are many scripts and languages which are written vertically (mostly top-to-bottom, but with a few unusal examples running bottom-to-top, as we shall see below). Handling vertical directionality requires the use of another CSS property, the writing mode:

<code>writing-mode: horizontal-tb | vertical-rl | vertical-lr</code>

The values for this property include two components: "horizontal" or "vertical" specifies the inline writing direction, while the second component specifies the direction in which lines in a block, and blocks in a sequence may be arranged: from top to bottom (as in most European languages, in which lines and paragraphs are arranged from top to bottom on a page), from right to left (as in the case of some East Asian languages such as Japanese, which we will see below), or left-to-right (e.g. Mongolian). This example shows a Japanese haiku poem transcribed first in Japanese, then in Romaji (Japanese in Latin script), and finally in an English translation.

[[File:Basho_furu_ike_ya.png|thumb|left|alt=Basho poem|Taken from p.42 of ''Haiku: Japanese Art and Poetry''. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. Used with permission.]]

<syntaxhighlight lang="xml">
<div>
<ab xml:lang="ja" style="writing-mode: vertical-rl"
xml:id="furu-ike-ya_jp" corresp="#furu-ike-ya_romaji #furu-ike-ya_en">
古池や<lb/>
蛙<lb/>
飛び込む<lb/>
水の音
</ab>

<lg xml:lang="ja-Latn" style="writing-mode: horizontal-tb"
xml:id="furu-ike-ya_romaji" corresp="#furu-ike-ya_jp #furu-ike-ya_en">
<l>furu ike ya</l>
<l>kawazu tobikomu</l>
<l>mizu no oto</l>
</lg>

<lg xml:lang="en"
xml:id="furu-ike-ya_en" corresp="#furu-ike-ya_jp #furu-ike-ya_romaji">
<l>Old pond,</l>
<l>and a frog dives in—</l>
<l>"Splash"!</l>
</lg>

<bibl>—Bashō (1644–1694)</bibl>
</div>
</syntaxhighlight>

Note: for the sake of simplicity, the indenting of lines in the vertical Japanese and the central alignment of the other components have been ignored in this encoding, since this section focuses on language and writing mode issues. The Japanese transcription has <code>writing-mode: vertical-rl</code>, which is required because Japanese may be written either in this mode or horizontally. The transcription in Romaji has <code>@xml:lang="ja-Latn"</code> (Japanese written in Latin script) and has a horizontal writing mode; this may seem superfluous, but vertically-written romaji is not unknown.

<div style="clear: both"> </div>

====Vertical text with embedded horizontal text====

When Japanese is written vertically, the glyph orientation remains the same as when it is written horizontally. In other words, glyphs are not rotated (although as noted above some different glyphs may be used for some characters the two orientations; punctuation for instance needs to be positioned differently in vertical versus horizontal text). However, it is very common for languages written vertically to have embedded runs of text from languages normally written horizontally. This raises the issue of the orientation of the glyphs from the horizontal language. Are they written upright, as they would normally appear in horizontal text runs, or are they rotated? Consider this fragment from a Japanese article about the Indonesian language, which takes the form of a glossary list:

[[File:Ja vertical indonesian frag sm.jpg|thumb|left|alt=Glossary list|Taken from p.62 of "インドネシア語". 崎山理. 1985. ''外国語との対照II''. 講座日本語学 11.]]

This might be transcribed as follows:

<syntaxhighlight lang="xml">
<list type="gloss" xml:lang="ja"
style="writing-mode: vertical-rl; text-orientation: mixed">

<label xml:lang="id">hampir</label> 　
<item>「近い、ほとんど」</item>

<label xml:lang="id">baru</label>
<item>「新しい、ばかい」</item>


</list>
</syntaxhighlight>

The rule <code>text-orientation: mixed</code> gives the expected orientation: "In vertical writing modes, characters from horizontal-only scripts are set sideways, i.e. 90° clockwise from their standard orientation in horizontal text. Characters from vertical scripts are set with their intrinsic orientation" ([http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131024/#text-orientation CSS Writing Modes]). In actual fact, the default value for <code>text-orientation</code> is "mixed", so this rule is not strictly required, but if the Indonesian glyphs had been set vertically, like this:

<div style="clear: both"> </div>

[[File:Ja vertical indonesian frag rotated sm.jpg|50px|thumb|left|alt=Glossary list|Fragment of previous image with Indonesian glyphs upright.]]

then the encoding would have to be explicit, and we could capture the orientation with <code>text-orientation: upright</code>.

<div style="clear: both"> </div>

====Vertical orientation in horizontal scripts====

It is not unusual to see text from horizontal languages written vertically even where it is not embedded in a text run from a vertically-written script. This example is a fragment from a table of information about agricultural development on Vancouver Island, written in 1855:

[[File:bcgenesis co 305 06 00131v table extract.jpg|thumb|center|600px|alt=Agricultural report table|Enclosure with 10048, CO 305/6, p. 109 http://bcgenesis.uvic.ca/getDoc.htm?id=V55116.scx]]

Four subheading cells in this fragment contain English text, written vertically, bottom-to-top, to conserve space on the page. This is not a "native orientation" for English; readers would not find it easy to read this text, and might be inclined to rotate the page in order to read it in a more natural way. To describe this sort of phenomenon, we can use the text-orientation property again:

<code>text-orientation: mixed|upright|sideways-right|sideways-left|sideways|use-glyph-orientation</code>

For full details on this property, we refer the reader to the CSS Writing Modes specification. For the present example, we will make use only of the "sideways-left" value, which "causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise." We might encode one of the four cells containing vertical text like this:

<syntaxhighlight lang="xml">
<cell style="writing-mode: vertical-lr; text-orientation: sideways-left">
Cash Value<lb/>
of<lb/>
Farms
</cell>
</syntaxhighlight>

The <code>writing-mode</code> captures the fact that the script is written vertically, and its line/block flow is from left to right (so "of" is to the right of "Cash value"), while the <code>text-orientation</code> value encodes the orientation (rotated 90° counter-clockwise). We might also add <code>text-align: center</code> to the style, to express the fact that the text is centrally-aligned; alignment properties are mapped relative to the line flow, so the word "of" is visibly centred relative to the physical top and bottom of the box, which are the left and right from the point of view of the line flow.

====Bottom-to-top writing====

There are a very small number of scripts which appear to be written bottom-to-top; perhaps the most well-known is Ogham, an alphabet used mainly to write Archaic Irish. The CSS Writing Modes specification does not explicitly provide for the distinction between top-to-bottom and bottom-to-top in vertically-written scripts; it is argued that all instances of bottom-to-top scripts are actually left-to-right horizontal scripts, oriented vertically because of the constraints of the medium on which they are inscribed (as in the case of Ogham inscriptions on tombstones). In other words, the case of scripts like this is analogous to the vertical English text-runs in the table cells in the example above, and can be handled in exactly the same manner (<code>writing-mode: vertical-lr; text-orientation: sideways-left</code>).

====Summary====

In this section, we have presented one approach to encoding text directionality features in TEI files, using the properties and values from the CSS Writing Modes module, encoded in the global TEI @style attribute (or in the TEI <code><rendition></code> element and linked with the @rendition attribute). For most texts, it will not be necessary to encode any information about text directionality, either because it follows unambiguously from <code>@xml:lang</code> values, or because it can be expected to be handled unequivocally by the Unicode Bidi Algorithm. Where it is important to encode text directionality, we believe that most phenomena can be well described through the use of the CSS Writing Modes features; of those which cannot, other approaches based on the CSS Transforms module are presented below.

===Text transformation===

====Rotation====

In what follows, we examine a range of textual phenomena which in some ways appear very similar to those examined above, and even overlap with them. We can categorize these as text transformation features, and suggest some strategies for encoding them based on the properties detailed in the [http://www.w3.org/TR/css3-transforms/ CSS Transforms] specification. The CSS Transforms module provides a complex array of properties, values and functions which can be used to rotate, skew, translate and otherwise transform textual and graphical objects. We can borrow this vocabulary in order to describe textual phenomena in a precise manner.

We begin with a simple example of a rotational transform:

[[File:Rotation_on_z_axis.png|frame‎]]

Here a block of text has been rotated around its z-axis. This is clearly not a "writing mode"; the writing mode for this text is horizontal, left to right. Furthermore, even if we wished to treat this as a writing mode, we could not do so, because there is no way to use writing modes properties to describe an text orientation which is angled at 45 degrees; no human languages are consistently written in this orientation. It is more appropriate to treat this as a rotational transformation. We can do this using two properties: <code>transform</code> and <code>transform-origin</code>. (Both of these properties have quite complex value sets, and we will not look at all of them here. See the [http://www.w3.org/TR/css3-transforms/ specification] for full details.)

The <code>transform</code> property takes as its value one or more of the transform functions, one of which is the function <code>rotateZ</code>:

<syntaxhighlight lang="xml">

<ab style="transform:rotateZ(-45deg)">TEI-C.ORG</ab>

</syntaxhighlight>

Any rotation must take place around an axis positioned relative to the element being rotated, and the <code>transform-origin</code> property can be used to specify the pivot point. By default, the value of <code>transform-origin</code> is "50% 50%", the point at the centre of the element, but these values can be changed to reflect rotation around a different origin point. (The TEI [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone element] also bears an attribute @rotate which can specify rotation in degrees around the z-axis, but it is not available for any other element.)

An element may also be rotated about either of its other axes. For example, this shows rotation around the Y (vertical) axis:

[[File:Rotation_on_y_axis.png|frame‎‎]]

<syntaxhighlight lang="xml">

<ab style="transform:rotateY(45deg)">TEI-C.ORG</ab>

</syntaxhighlight>

These are obviously trivial examples, but similar features do appear in historical texts. George Herbert's ''The Temple'' includes two stanzas headed "Easter Wings" which are both normally printed in a rotated form so that they represent a pair of wings:

[[File:Herbert church p35 sm.jpg|thumb|left|300px|Page 35 of Herbert's ''The Temple'', second stanza of Easter Wings (or second poem so named). Used with permission of the Folger Library.]]

This could be encoded thus:

<syntaxhighlight lang="xml">
<lg style="transform:rotateX(90deg)">
<l>My tender age in ſorrow did beginne:</l>
<l>And ſtill with ſickneſſes and ſhame</l>

</lg>
</syntaxhighlight>

but we might also argue that this is in fact a vertical writing mode, and express it with <code>writing-mode: vertical-rl; text-orientation: sideways-right</code>.

<div style="clear: both;"> </div>

====Boustrophedon====

We may also use rotation as a method of handling a true writing mode which is not covered by the CSS Writing Modes: boustrophedon. This is a writing mode common in inscriptions in Latin, Greek and other languages, in which alternate lines run from left to right and from right to left; its name derives from the path of an ox pulling a plough. Right-to-left lines in boustrophedon have another unexpected feature: their glyphs are reversed, so that these lines appear as "mirror writing". This example shows a transcription of a Greek inscription at Dodona:

[[File:Boustrophedon small J.NW.Epeiros.13.p03.jpg|thumb|left|300px|Drawing of a leaden plaque bearing an inquiry by Hermon from the oracular precinct at Dodona. Image and transcription from http://poinikastas.csad.ox.ac.uk, used with permission.]]

This might be transcribed as follows (ignoring word boundaries for the moment):

<syntaxhighlight lang="xml">
<ab>
ΗΕΡΜΟΝΤΙΝΑ <lb/>
<seg style="rotateY(180deg)">ΚΑΘΕΟΝΠΟΤΘΕΜ</seg> <lb/>
ΕΝΟΣΥΕΝΕΑϜ <lb/>
<seg style="rotateY(180deg)">ΟΙΥΕΝΟΙΤΙΕΚΚ</seg> <lb/>
ΡΕΤΑΙΑΣΟΝΑ <lb/>
<seg style="rotateY(180deg)">ΣΙΜΟΣΟΤΤΑΙΕ</seg> <lb/>
ΑΣΣΑΙ
</ab>
</syntaxhighlight>

The 180-degree rotation around the Y (vertical) axis here gives us exactly the effect of the RTL line in boustrophedon; the order of glyphs is reversed, and so is their individual orientation (in fact, we see them "from the back", as it were). <code><seg></code> elements have been used here because these are clearly not "lines" in the sense of poetic lines; the text is continuous prose, and linebreaks are incidental.

There are obviously some unsatisfactory aspects of this manner of encoding boustrophedon. In the inscription above, some words run across linebreaks, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform function rather than a writing mode property, we are apparently suggesting that boustrophedon is not in fact a writing mode, whereas it clearly is. But the CSS Writing Modes specification does not provide support for boustrophedon, because it is a rather obscure historical phenomenon; using a rotational transform is one practical alternative.

<div style="clear: both;"> </div>

====Caveats====

The effect and behaviour of CSS Transforms properties and values according to the specification are highly dependent on the computed [http://www.w3.org/TR/CSS2/visuren.html Visual formatting model] of an HTML document. TEI currently does not have an explicit processing or formatting model. That is, it is by no means clear whether any given TEI element should be interpreted, for instance, as a block-level or inline-level element; for many elements we may think we can assume block-level (<code><ab></code>, "anonymous block") or inline-level (<code><w></code>, "word") from the semantics, but even this is risky. As long as the properties and values from the CSS Transforms module are used as a convenient, well-specified descriptive language to capture features of a text, without any expectation of using them directly and reliably for rendering, this is not problematic; we are simply borrowing a useful vocabulary from an external source, and benefiting from the clarity of definition provided by the specification. However, if there is any expectation of using this information to render a text in a predictable and accurate way, it will be essential to provide enough styling information throughout the document hierarchy to resolve all ambiguities with regard to size, positioning, block status, etc. before any element undergoes a transform operation.

<references/>

[[Category:Council]]

AttsWithoutEgs

2013-11-11T03:57:17Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
| Low
|-
| 41
| gradual
| writing
|
|
| Low
|-
| 42
| group
| att.damaged
|
|
| High, I guess, though if I had a time machine I'd destroy this attribute name
|-
| 43
| hand
| att.damaged
|
|
| Medium. Shouldn't all these instances of @hand--except maybe the one in att.textCritical--be consolidated into one definition, presumably in att.transcriptional all be defined in the same place, though?
|-
| 44
| hand
| att.transcriptional
|
|
| Low
|-
| 45
| hand
| gap
|
|
| Low
|-
| 46
| hand
| unclear
|
|
| Low
|-
| 47
| hand
| att.textCritical
|
|
| Low
|-
| 48
| height
| graphic
|
|
| Low. I'm not sure why @width isn't in this list, though--I don't see an example for it, either.
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| d

AttsWithoutEgs

2013-11-11T03:52:43Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
| Low
|-
| 41
| gradual
| writing
|
|
| Low
|-
| 42
| group
| att.damaged
|
|
| High, I guess, though if I had a time machine I'd destroy this attribute name
|-
| 43
| hand
| att.damaged
|
|
| Medium. Shouldn't all these instances of @hand--except maybe the one in att.textCritical--be consolidated into one definition, presumably in att.transcriptional all be defined in the same place, though?
|-
| 44
| hand
| att.transcriptional
|
|
| Low
|-
| 45
| hand
| gap
|
|
| Low
|-
| 46
| hand
| unclear
|
|
| Low
|-
| 47
| hand
| att.textCritical
|
|
| Low
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| d

AttsWithoutEgs

2013-11-11T03:40:11Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
| Low
|-
| 41
| gradual
| writing
|
|
| Low
|-
| 42
| group
| att.damaged
|
|
| High, I guess, though if I had a time machine I'd destroy this attribute name
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| d

AttsWithoutEgs

2013-11-11T03:36:09Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
| Low
|-
| 41
| gradual
| writing
|
|
| Low
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:34:27Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
| Low
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:31:50Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
| High
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:29:45Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
| Medium
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:26:38Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
| Deprecated
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:25:08Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
| Low
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:23:17Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
| Low
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:20:29Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
| Low
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:18:35Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
| Low
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:16:37Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
| Medium
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:15:18Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
| Low
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:13:12Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
| High
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:11:15Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
| Low
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:09:48Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
| Low
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:08:49Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
| High (same, I presume, as @start). There are examples embedded in 8.4.1, though.
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:06:47Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
| Low
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:05:40Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|Low
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T03:04:32Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|Low but I think the example in 13.3.6.3 is mistaken. Unfortunately, the spam filter won't allow the naughty text here so I can't reproduce or correct it.
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:50:34Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
| Low
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:47:45Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
| Low
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:46:22Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
| Medium
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:43:22Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
| Low
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:33:37Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
| Medium
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:29:03Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
| High
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:27:21Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:24:34Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:22:22Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:19:24Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:17:40Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:16:25Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:14:18Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Low
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Low
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-10T19:14:17Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|
|-
| 146
| uly
| att.coordinated
|
|
|
|-
| 147
| unit
| pc
|
|
|
|-
| 148
| url
| moduleRef
|
|
|
|-
| 149
| value
| att.lexicographic
|
|
|
|-
| 150
| value
| node
|
|
|
|-
| 151
| value
| root
|
|
|
|-
| 152
| value
| iNode
|
|
|
|-
| 153
| value
| leaf
|
|
|
|-
| 154
| value
| eTree
|
|
|
|-
| 155
| value
| triangle
|
|
|
|-
| 156
| varSeq
| att.textCritical
|
|
|
|-
| 157
| version
| unicodeName
|
|
|
|-
| 158
| versionDate
| att.translatable
|
|
|
|-
| 159
| when
| docDate
|
|
|
|-
| 160
| where
| event
|
|
|
|-
| 161
| width
| graphic
|
|
|
|-
| 162
| width
| binaryObject
|
|
|
|-
| 163
| wit
| att.rdgPart
|
|
|
|-
| 164
| wit
| att.witnessed
|
|
|
|}

AttsWithoutEgs

2013-11-10T18:46:34Z

Brettttt:

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
|
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|
|-
| 146
| uly
| att.coordinated
|
|
|
|-
| 147
| unit
| pc
|
|
|
|-
| 148
| url
| moduleRef
|
|
|
|-
| 149
| value
| att.lexicographic
|
|
|
|-
| 150
| value
| node
|
|
|
|-
| 151
| value
| root
|
|
|
|-
| 152
| value
| iNode
|
|
|
|-
| 153
| value
| leaf
|
|
|
|-
| 154
| value
| eTree
|
|
|
|-
| 155
| value
| triangle
|
|
|
|-
| 156
| varSeq
| att.textCritical
|
|
|
|-
| 157
| version
| unicodeName
|
|
|
|-
| 158
| versionDate
| att.translatable
|
|
|
|-
| 159
| when
| docDate
|
|
|
|-
| 160
| where
| event
|
|
|
|-
| 161
| width
| graphic
|
|
|
|-
| 162
| width
| binaryObject
|
|
|
|-
| 163
| wit
| att.rdgPart
|
|
|
|-
| 164
| wit
| att.witnessed
|
|
|
|}

AttsWithoutEgs

2013-10-16T20:54:08Z

Brettttt: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed

|-
| 1
| absolute
| when
|
|
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|-
| 3
| ana
| att.global.analytic
|
|
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|-
| 6
| baseTypes
| fsDecl
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|-
| 9
| change
| att.global.change
|
|
|-
| 10
| class
| msContents
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|-
| 12
| confidence
| att.ranging
|
|
|-
| 13
| contemporary
| seal
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|-
| 16
| datingPoint
| att.datable.custom
|
|
|-
| 17
| decls
| att.declaring
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|-
| 19
| degree
| att.damaged
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|-
| 24
| encoding
| binaryObject
|
|
|-
| 25
| end
| att.timed
|
|
|-
| 26
| except
| moduleRef
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|-
| 29
| fVal
| f
|
|
|-
| 30
| facs
| att.global.facs
|
|
|-
| 31
| feats
| fs
|
|
|-
| 32
| filter
| equiv
|
|
|-
| 33
| flipping
| surface
|
|
|-
| 34
| follow
| leaf
|
|
|-
| 35
| form
| quotation
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|-
| 37
| from
| app
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|-
| 39
| from-iso
| att.datable.iso
|
|
|-
| 40
| function
| att.segLike
|
|
|-
| 41
| gradual
| writing
|
|
|-
| 42
| group
| att.damaged
|
|
|-
| 43
| hand
| att.damaged
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|-
| 45
| hand
| gap
|
|
|-
| 46
| hand
| unclear
|
|
|-
| 47
| hand
| att.textCritical
|
|
|-
| 48
| height
| graphic
|
|
|-
| 49
| height
| binaryObject
|
|
|-
| 50
| ident
| att.identified
|
|
|-
| 51
| inst
| att.interpLike
|
|
|-
| 52
| instant
| att.editLike
|
|
|-
| 53
| key
| classRef
|
|
|-
| 54
| key
| macroRef
|
|
|-
| 55
| level
| sense
|
|
|-
| 56
| loc
| app
|
|
|-
| 57
| location
| att.lexicographic
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|-
| 59
| lry
| att.coordinated
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|-
| 61
| max
| att.ranging
|
|
|-
| 62
| max
| memberOf
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|-
| 65
| met
| att.metrical
|
|
|-
| 66
| min
| att.ranging
|
|
|-
| 67
| min
| memberOf
|
|
|-
| 68
| module
| att.identified
|
|
|-
| 69
| new
| handShift
|
|
|-
| 70
| next
| att.global.linking
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|-
| 76
| ns
| attDef
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|-
| 78
| nymRef
| att.naming
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|-
| 80
| optional
| fDecl
|
|
|-
| 81
| ord
| root
|
|
|-
| 82
| ord
| iNode
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|-
| 84
| parts
| nym
|
|
|-
| 85
| perf
| tech
|
|
|-
| 86
| period
| att.datable
|
|
|-
| 87
| pre
| pc
|
|
|-
| 88
| precision
| att.dimensions
|
|
|-
| 89
| predeclare
| att.identified
|
|
|-
| 90
| prefix
| moduleRef
|
|
|-
| 91
| prefix
| elementSpec
|
|
|-
| 92
| prev
| att.global.linking
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|-
| 94
| real
| att.metrical
|
|
|-
| 95
| ref
| att.canonical
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|-
| 98
| resp
| space
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|-
| 100
| role
| att.naming
|
|
|-
| 101
| role
| org
|
|
|-
| 102
| rotate
| zone
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|-
| 104
| sameAs
| att.global.linking
|
|
|-
| 105
| scale
| graphic
|
|
|-
| 106
| scale
| binaryObject
|
|
|-
| 107
| scheme
| catRef
|
|
|-
| 108
| scheme
| locus
|
|
|-
| 109
| scheme
| locusGrp
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|-
| 112
| script
| att.handFeatures
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|-
| 114
| select
| att.global.linking
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|-
| 116
| social
| distinct
|
|
|-
| 117
| sort
| att.personal
|
|
|-
| 118
| source
| att.editLike
|
|
|-
| 119
| source
| att.readFrom
|
|
|-
| 120
| source
| writing
|
|
|-
| 121
| space
| distinct
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|-
| 123
| split
| att.lexicographic
|
|
|-
| 124
| start
| att.timed
|
|
|-
| 125
| start
| att.coordinated
|
|
|-
| 126
| stdDeviation
| precision
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|-
| 128
| subtype
| abbr
|
|
|-
| 129
| subtype
| title
|
|
|-
| 130
| synch
| att.global.linking
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|-
| 132
| target
| change
|
|
|-
| 133
| target
| relatedItem
|
|
|-
| 134
| targetEnd
| note
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|-
| 136
| targets
| link
|
|
|-
| 137
| targets
| join
|
|
|-
| 138
| targets
| alt
|
|
|-
| 139
| time
| distinct
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|-
| 141
| to
| app
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|-
| 143
| to-iso
| att.datable.iso
|
|
|-
| 144
| type
| sound
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|-
| 146
| uly
| att.coordinated
|
|
|-
| 147
| unit
| pc
|
|
|-
| 148
| url
| moduleRef
|
|
|-
| 149
| value
| att.lexicographic
|
|
|-
| 150
| value
| node
|
|
|-
| 151
| value
| root
|
|
|-
| 152
| value
| iNode
|
|
|-
| 153
| value
| leaf
|
|
|-
| 154
| value
| eTree
|
|
|-
| 155
| value
| triangle
|
|
|-
| 156
| varSeq
| att.textCritical
|
|
|-
| 157
| version
| unicodeName
|
|
|-
| 158
| versionDate
| att.translatable
|
|
|-
| 159
| when
| docDate
|
|
|-
| 160
| where
| event
|
|
|-
| 161
| width
| graphic
|
|
|-
| 162
| width
| binaryObject
|
|
|-
| 163
| wit
| att.rdgPart
|
|
|-
| 164
| wit
| att.witnessed
|
|
|}

IRC

2013-01-18T17:19:25Z

Brettttt: /* Freenode 'NickServ' Service */

== Introduction ==

Although it is completely unofficial, a number of us involved with the [http://www.tei-c.org/ Text Encoding Initiative] have been hanging out in an Internet Relay Chat (IRC) channel. This allows us to communicate on all sorts of topics quickly, and occasionally a bit of social banter. In order to join into the network and the #tei-c channel you will need to use an IRC client which you run on your computer.

The technical information needed is:
* Server: '''irc.freenode.net'''
* Channel: '''#tei-c'''

More information is available about the [http://freenode.net/ freenode network] if you wish.

== IRC Commands ==
IRC is at its heart a text-based discussion network. This network is controlled by text-based commands prefixed with a '/'. Text without this command prefix is sent to the chat channel. In many modern clients there are graphical buttons or other methods instead of typing the following commands. However, for reference, some basic IRC commands are:

* '''/away [message]''' (Set an away message, or use no message to return from being away)
** /away In a meeting, back at 1pm
* '''/invite <nick> [channel]''' (Invite a user to join the current or a specific channel)
** /invite JuliaF #tei-c
* '''/join <channel>''' (Join an existing or new IRC channel)
** /join #tei-c
* '''/list''' (Display a list of channels on a server. '''Warning, this can be quite large!''')
** /list
* '''/me <action to perform>''' (Perform an action in a channel or private chat)
** /me yawns and falls asleep over Chapter 16.
* '''/msg <nick> <message>''' (Send a private message to a user (as opposed to a channel))
** /msg Syd What is your opinion on floating <div> elements?
* '''/names [channel]''' (List the users currently in a channel)
** /names #tei-c
* '''/nick <new nickname>''' (Change your nickname)
** /nick SebastianR
* '''/part [room] [message]''' (Leave the current channel, or a specified channel, with an optional message)
** /part #tei-c I'm off to the pub!
* '''/ping [nick]''' (Asks how much lag a user (or the server if no user specified) has)
** /ping LOU
* '''/quit [message]''' (Disconnect from the server, with an optional message)
** /quit I'm off to the pub!
* '''/whois <nick>''' (Get information on a user)
** e.g. /whois James-C

There are other commands, but those basic ones should allow you to participate fully in discussions. Some clients remove the ability to send these commands in this way and implement other ways to send them on your behalf.

== Freenode 'NickServ' Service ==

Freenode provides a method for you to have control over a static nickname. The 'NickServ' service allows you to register a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type '''/msg NickServ <command>'''.
For more information on a specific command, type '''/msg NickServ help <command>''' where <command> is any of:

* '''access''' (Modify the list of authorized addresses)
* '''drop''' (Cancel the registration of a nickname)
* '''ghost''' (Kill a ghosted nickname)
* '''identify''' (Identify yourself with your password)
* '''info''' (Get information for a nickname)
* '''link''' (Link your nickname to another)
* '''list''' (Display list of nicks matching a pattern)
* '''recover''' (Kill another user who has taken your nick)
* '''register''' (Register a nickname)
* '''release''' (Regain custody of your nick after RECOVER)
* '''set''' (Set various options for your nickname)
* '''unlink''' (UnLink your nickname)



== Setup for Specific Clients ==

If you want to add installation instructions, helpful hints, or suggested customisations and links for specific clients, do it here.

=== Pidgin ===

Pidgin is a multi-protocol multi-operating system client that allows connection not only to IRC, but AIM/AOL, MSN, Yahoo, Jabber/Gmail, and other chat protocols all from a single client.

* http://pidgin.sourceforge.net/

=== XChat ===

XChat is a multi-operating system IRC client

* http://www.xchat.org/

=== Chatzilla ===

Chatzilla is a a firefox extension IRC client. If you have it installed then [irc://irc.freenode.net/#tei-c irc://irc.freenode.net/#tei-c] url should take you straight to the #tei-c channel. Otherwise just do /join #tei-c

* https://addons.mozilla.org/extensions/moreinfo.php?id=16

== IRC-Related Links ==
* http://freenode.net/ (The irc.freenode.net network website)
* http://www.irc.org/

[[Category:Community]]

Council

2012-11-26T22:37:02Z

Brettttt: /* Teleconference, 2012-12 */

The TEI Technical Council, often referred to as 'TEI Council' or 'Council' is the elected body that is responsible for maintaining and implementing the TEI Guidelines. Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ. The TEI Council also uses this page to store some of its draft agendas while working them up before Face 2 Face meetings.

== Teleconference, 2012-12 ==
* Introduce new members if present (who can say if they have pressing stuff they want to work on), say farewell to people leaving (who can say if they have any unfinished business) (JC)
* Chair's report back on issues arising from TEI members meeting and Board meeting (JC)
* Next P5 release - when, what and who (JC)
* Report on deprecation of TEI P4 (JC & KH)
* How to proceed with proof of concept Roma rewrite (Byzantium); see http://tei.oucs.ox.ac.uk/Byzantium/ - for amusement, cf Council minutes below from 9 September 2008 (SR)
* Guidelines front page: should we merge index.html with index_toc.html for a single, simpler page? (MH)
* Spring Face 2 Face Meeting (JC)
* [http://wiki.tei-c.org/index.php/Oxford2012-Actions Action items] from Oxford F2F

== Face to Face Meeting: Oxford 2012-09-19 to 2012-09-21 ==

=== Wednesday 19 September 2012 ===
Location: IT Services, 13 Banbury Road, Oxford, OX2 8NP - Kennet Room

'''09:30 - 10:30''' Items to discuss
* Review of [[AnnArbor2012-Actions|Ann Arbor Actions]] and [http://www.tei-c.org/Activities/Council/Meetings/tcm51.xml Teleconference Actions] (JC)
* Reports from SIGs (JC)
* Deprecation policy: We need to figure out what we're doing. See [http://wiki.tei-c.org/index.php/Deprecation Kevin's summary of current practice] and [http://wiki.tei-c.org/index.php/Talk:Deprecation stalled discussion]
* [[Private URI Schemes|Private URI Schemes proposal]] (MH)

'''10:30 - 12:30''' (tea break ~11:00)
* [[Council-ticketTriage|Ticket]] Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''14:00 - 15:00''' Items to discuss
* [http://tinyurl.com/teicouncil-oddsummary Report on TEI ODD Workshop]; ODD Proposals (JC/SR)
* [https://docs.google.com/document/d/1JsMA-gOGrevyY-crzHGiC7eZ8XdV5H_wFTlUGzrf20w/edit XPointer Proposal] (GB)
* Resolving Durand: c.f. http://foxglove.hypotheses.org/368 (LB)

'''15:00 - 16:30''' (tea break ~16:00)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans

'''19:30 - '''
* Supper: http://www.al-shami.co.uk/ (Middle Eastern)

=== Thursday 20 September 2012 ===
Location: Buttery, Wolfson College, Linton Road, Oxford, OX2 6UD

'''09:30 - 10:30''' Items to discuss
* Roma Templates and Example Customizations (from discussion in early September on tei-council)
** Sebastian should explain the purpose of providing downloadable customizations.
** On http://www.tei-c.org/Guidelines/Customization/ and http://www.tei-c.org/Guidelines/Customization/odds.xml , are any modules labeled as experimental that should not be, or any modules not labeled but should be? (Note that currently the dictionaries module is documented differently on these two pages.) Sebastian said that none are experimental any more.
** Roma interface
*** Do we agree with Sebastian removing MS, dict, speech, drama, and corpus from the "Create Customization from template" drop-down menu at http://www.tei-c.org/Roma/ ? He said that Bare, Lite, and Tite make sense since they are coherent and have a purpose, and that SVG, MathML, XInclude, ITS, and ODD are also sensible since they involve non-obvious techniques which you can't recreate easily in Roma. But the remaining five are are not meaningfully useful, documented, or follow any known recommendation. James said they were supplied here as simple example customisations. Martin suggested separating out such options as "advanced".
*** Should we provide template for community-created customisations in Roma that are reasonably mature and well-supported, such as EpiDoc? What would be our management process for this?
** Should we begin generating HTML and PDF documentation for any modules besides Lite and Tite (and putting them in http://www.tei-c.org/release/doc/tei-p5-exemplars/ )?
** For the two sections of customizations at http://www.tei-c.org/Guidelines/Customization/ :
*** Do we want to rename the first heading "Customizations provided by the TEI Consortium" to "Customizations maintained by the TEI Consortium" or "Customizations supported by the TEI Consortium"?
*** Can we clarify what "more restricted or experimental" means? These are not the same thing, and it isn't clear what either means.
*** Do we want to set up a procedure for deciding what can be added to the "TEI Community Customizations" or for periodically revisiting those listed there? Even if not, should we just go ahead and remove MEP from the list since the links are broken and it's not a P3 thing?
*** Do we find the heading "TEI Community Customizations" clear enough, or do we want to add a paragraph here explaining ?
* Div.Liminal (LB)
* LingSIG issues (PB)
* Add yours here
*

'''10:30 - 12:30''' (tea break ~11am)
* Ticket Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''13:30 - 15:00''' Items to discuss
* Board Proposals for Council Consideration (EP)
* We have very similar information on writing ODDs [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#MD in the Guidelines] and [http://www.tei-c.org/Guidelines/Customization/odds.xml#body.1_div.2 on the TEI-C website]. I think these should be merged into one place. Where should the merged documentation be? Can someone review each document to make sure it's accurate before we ask someone to merge the two?
* Questions for candidates (See David Sewell's Email http://lists.village.virginia.edu/pipermail/tei-council/2012/016259.html )
* Add yours here
*

'''15:00 - 16:30''' (tea break ~4pm)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans
* Supper: If weather is nice, we thought about walking up the river from Wolfson to: http://www.victoriaarms.co.uk a nearby pub run by the Oxford Preservation Trust (British pub food). We may even take you here by punt. If weather is not so good we’ll go elsewhere in nearby Summertown.

=== Friday 21 September 2012 ===
Location: Buttery, Wolfson College, Linton Road, Oxford, OX2 6UD

'''09:30 - 10:30''' Items to discuss
* Code Bounties: Decide Topics: (e.g. Roma ReWrite), poss specification brainstorming
* Options for freezing and/or archiving Lite. Planning Lite reLaunch.
* Move TEI to GitHub?
* Deprecation of TEI P4

'''10:30 - 12:30''' (tea break ~11am)
* Ticket Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''13:30 - 15:00''' Items to discuss
* @rend
*
*

'''15:00 - 16:30''' (tea break ~4pm)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans

'''19:30 - '''
* Supper: http://www.mysichuan.co.uk/ (Chinese)

== Teleconference - 2012-08-09 20:00 BST ==
=== Agenda ===

* Brief Reports
** TEI Tite (KH)
** SIG reports (JC)
** Google Books (KH)
** Physical Bibliography (KH)
** ODD Meeting after DH2012 (JC)
** XPointer scheme proposal (GB)
** Face2Face Meeting: arrangements (JC)
* Replacement for SY or not? (JC)
* TEI Lite (LB)
* Reminder to finish off Ann Arbor Actions (JC)
* (more items TBD)

== F2F meeting - Ann Arbor 15-18 April 2012 ==

Turkish-American Friendship Room, Shapiro Science Library

Description : http://www.lib.umich.edu/node/22671/
Location : <location><geo>42.275832 -83.737265</geo></location>

Here is a list of [[AnnArbor2012-Actions]] to be done.

=== Agenda ===
==== Sunday 15 April 10:00-16:00 (optional) ====
Optional TEI HackFest for those arriving early (because of flights including a Saturday being cheaper) or local people who wish to attend.

Possible tasks for the day:

* From Sebastian: "I think there is some problem of ODD processing in a pending ticket which I said was doable with some concentration - was it the idea of redeclaration of attributes (i.e. datatypes) in the P5 source itself?"
* From Sebastian: "We need to reassess what is left over from EEBO/ECCO work which still needs resolving, to give a context for Monday"
* James-C: Vault-related tidying perhaps; Also have some TEI -> MARC (for Google eBooks from TEI -> ePub) XSLT to complete.
* Lou : I would like to work on accomodating some existing TEI-like schemas into proper TEI ODDs. Notably Vogeler's "Charters Encoding Initiative" dtd; other suggestions welcome. How about a proper effort to bring EAD back into the paths of righteousness? (Sebastian says: in a day?????)
* Lou : I would also like to work on some Garage case studies, of the Word -> P5 variety

'''10:00 - 12:30'ish:'''
* Hack on TEI-related development

'''12:30 - 14:30:'''
*lunch

'''14:30 - 16:00:'''
* More TEI-related hacking

'''19:00 -'''
* Supper

==== Monday 16 April 09:00 - 17:30 ====
(Tentative and flexible timetabled agenda)

'''09:00 - 10:00:'''
* TEI - Google Books
* TEI - EEBO / ECCO

'''10:00 - 12:30:'''
* TEI Bugs and FR: (Green and hopefully some amber ones)

'''12:30 - 14:30 (shorter if possible):'''
* Lunch

'''14:30 - 15:30:'''
* TEI and Schematron Tests
* TEI Exemplars (e.g. Tite)
* Best Practices for TEI in Libraries

'''15:30 - 17:30:'''
* TEI Bugs and FR: (Amber)

'''19:00-'''
Supper (optional)

==== Tuesday 17 April 09:00 - 17:30 ====

'''09:00-10:00:'''
* TEI Namespaces and Conformance
* Chapter/module fragmentation and consolidation (e.g. should things like 'dates' become a chapter of its own)
* TEI Examples

'''10:00 - 12:30:'''
* TEI Bugs and FR (Amber)

'''12:30 - 14:30:'''
* 'Open Lunch' with people from University of Michigan community interested in meeting us

'''14:30 - 15:30:'''
* TEI FR: Floating Div
* TEI ODD Meeting

'''15:30 - 17:30:'''
* TEI Bugs and FR (Amber)

'''19:00-'''
Supper (optional)

==== Wednesday 18 April 09:00 - 16:00 ====

'''09:00 - 10:00:'''
* TEI and URIs
* TEI Release Process
* TEI Outreach and Education
* Any Other Council Business

'''10:00 - 12:30:'''
* Bugs and FR (Amber / Red)

'''12:30 - 14:30 (or shorter):'''
* Lunch

'''14:30 - 16:00 (or longer?):'''
* Bugs and FR: outstanding / summary
*(early end for those who need flights)

== Teleconference - Tuesday 28 February 2012 at 18:00 GMT ==
# Brief Reports
## [[Ad-hoc_committee_on_encoding_of_bibliographic_citations|Bibliographic Citations]] (KH & MH)
## TEI Tite (KH)
## TEI and AdBlock (MH)
## Google Books (KH)
## Xpointer (GB)
## Attribute Datatypes (MH)
## Physical Bibliography (KH)
## TEI Release Process Document (MH)
## Future of ODD meeting, DH2012 (JC)
# @ref/key/cRef & Private URI Schemes (MH)
# Best Practices for TEI in Libraries (KH)
# Practical Arrangements for April Face2Face (RW)
# Agenda for the April Face2Face (JC)
# AOB

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* organisational:
** 9:30: breakfast
** 12:30: lunch at Pizzeria Via Italia (Pizzeria Via Italia - 21, avenue d'Italie - 01 42 16 97 89)
** 15:30: coffee break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût (L'avant Goût - 26, rue Bobillot - 01 53 80 24 00)
** 15:30: coffee break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffee break
* topical
** Wiki access restrictions
** P4 survey

** grp vs. list
** Magic tokens
** translations

** P6 discussion and visions
** community project
** core too big
** modifying attributes from a class
** revamping Roma
** Planning priorities for next year

=== Minutes/notes Paris 2011 Meeting ===

* [http://www.tei-c.org/Activities/Council/Meetings/tcm48.xml minutes in TEI]
* [[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== Agenda ===
Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on editing the Guidelines (Lou cf. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kevin for TEI PUB SIG?)
* deprecation, beta, etc.

* automatic generation of feeds/twitts from SF tickets (new ones; solved ones)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== TEI and Google ====

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

SY Gate is a really good flexible framework that includes tokenisation, but only pretends to do XML: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

KH: cf. http://purl.oclc.org/NET/teiinlibraries

=== Minutes ====

[http://www.tei-c.org/Activities/Council/Meetings/tcm46.xml Minutes of the Chicago meeting for reference]

== Item for further consideration ==
* Stable URIs to discrete bits of the guidelines
* [[Council FR assignments]]

== F2F meeting - Dublin 28-30 April 2010 ==

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* Manuscript (genetic editions)
* Second SF session
* 4 p.m.: biblStruct

==== Friday morning ====
* hyphenation
* ODD - (r)evolutions
* Third SF session
==== Friday afternoon ====
* remaining issues
* prospective

=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

=== Minutes ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml Minutes of the Dublin meeting for reference]

== Ad-hoc committee on encoding of bibliographic citations ==

[[Ad-hoc committee on encoding of bibliographic citations]]

== Telko October 2009 ==
=== Connexion details ===

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:
*Domestic*

USA USA 1-201-793-9022
Canada Canada 1-201-793-9022
Long distance costs apply
*International*

Austria Austria 0820 401 15470
Belgium Belgium 0703 57 134
France France 0826 109 071
Germany Germany 01805 00 9527
Ireland Ireland 0818 270 968
Italy Italy 848 390 177
Spain Spain 902 885 791
Switzerland Switzerland 0848 560 397
United Kingdom United Kingdom 0870 0990 931

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content
* report to TEI MM

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml Minutes of the October meeting for reference]
* Bug and features - SF
* Focussed technical discussions
** Placement of schematron constraints in ODD - Sebastian Rahtz
** Discussion of "canonical way of referencing TEI element definitions"
** Wider debate: the future of ODD
(SourceForge item 2411994) and related issue of permanent URLs for TEI
documentation - David Sewell
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 SF ID: 2411994]
** Reporting on stylesheets (SR, DOD)
*** Evolution towards XSL 2.0
**** main advantages (features) provided by a switch to 2.0
**** consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
**** how much of this should be known by the TEI community?

* Getting started (PB)
* Projects
** TEI - ISO
* Perspective workshop on TEI for the next decade
** communities
*** role of TEI in research infrastructures (AC)
**event
*** Dagstuhl
*** ESF [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd:
They used to be at
http://www.tei-c.org/Vault/GL/P1/ [source only]
http://www.tei-c.org/Vault/GL/P2/ [source only]
http://www.tei-c.org/Vault/GL/P3/index.htm [source in P3X/]

But I don't know where old stuff went when we moved to the new
website. In any case, there are copies of P3 at:
http://quod.lib.umich.edu/t/tei/
http://etext.virginia.edu/standards/tei/teip3/

== Council Telco - 21 August 2008 ==
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml
== Issues for next Telco - Oct 2008 ==
* update on SF bugs and features (Oxford)

* report to TEI MM

* naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ([http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html]) about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

* update on SIGs + responsabilities

* placement of Schematron rules in ODD
http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html

Note to be produced by SR

* update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and [[Getting Started]]

Looking for candidates:
** 6. Choosing and installing an editor
** 9. Getting this to work on sample of own text
** 11. Where to go from here

== Issues for next F2F ==

* Discussion on ODD and its evolution--[[User:Romary|Romary]] 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)

Namespaces

* Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

* should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

== Highlights to be brought to the TEI MM 2008 ==

== Topics (could be moved up to one F2F or Telco meeting ==

* Stable reference to TEI objects

(For original source of these comments, see tei-council thread [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|stable references]].)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in http://www.tei-c.org/ns/1.0), sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>: http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html
but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e.
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log
which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:
http://www.tei-c.org/Guidelines/access.xml

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we
might want to consider adopting one or another of the standard systems
for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to
register the DOIs with one of the national registries, but some more
extensive costs in human time to set up a good system for mapping from
our existing nomenclature to a set of DOI identifiers. (Publishers
typically use DOIs to identify individual books or journal articles, but
they can be more granular: every reference page in the Guidelines could
have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using
DOIs for citations could simply cite a DOI. So instead of the reference
for <name> in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

which would be resolved to the actual Web address by a DOI resolver.
(Many journal DOIs are mostly numeric but the syntax allows more
human-readable names).

If we seriously want to consider an option like this, we should put out
a call to the librarians/metadata gurus in our community for assistance
with implementation.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2012-11-26T22:29:29Z

Brettttt: /* Teleconference, 2012-12 */

The TEI Technical Council, often referred to as 'TEI Council' or 'Council' is the elected body that is responsible for maintaining and implementing the TEI Guidelines. Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ. The TEI Council also uses this page to store some of its draft agendas while working them up before Face 2 Face meetings.

== Teleconference, 2012-12 ==
* Introduce new members if present (who can say if they have pressing stuff they want to work on), say farewell to people leaving (who can say if they have any unfinished business) (JC)
* Chair's report back on issues arising from TEI members meeting and Board meeting (JC)
* Next P5 release - when, what and who (JC)
* Report on deprecation of TEI P4 (JC & KH)
* How to proceed with proof of concept Roma rewrite (Byzantium); see http://tei.oucs.ox.ac.uk/Byzantium/ - for amusement, cf Council minutes below from 9 September 2008 (SR)
* Guidelines front page: should we merge index.html with index_toc.html for a single, simpler page? (MH)
* Spring Face 2 Face Meeting (JC)

== Face to Face Meeting: Oxford 2012-09-19 to 2012-09-21 ==

=== Wednesday 19 September 2012 ===
Location: IT Services, 13 Banbury Road, Oxford, OX2 8NP - Kennet Room

'''09:30 - 10:30''' Items to discuss
* Review of [[AnnArbor2012-Actions|Ann Arbor Actions]] and [http://www.tei-c.org/Activities/Council/Meetings/tcm51.xml Teleconference Actions] (JC)
* Reports from SIGs (JC)
* Deprecation policy: We need to figure out what we're doing. See [http://wiki.tei-c.org/index.php/Deprecation Kevin's summary of current practice] and [http://wiki.tei-c.org/index.php/Talk:Deprecation stalled discussion]
* [[Private URI Schemes|Private URI Schemes proposal]] (MH)

'''10:30 - 12:30''' (tea break ~11:00)
* [[Council-ticketTriage|Ticket]] Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''14:00 - 15:00''' Items to discuss
* [http://tinyurl.com/teicouncil-oddsummary Report on TEI ODD Workshop]; ODD Proposals (JC/SR)
* [https://docs.google.com/document/d/1JsMA-gOGrevyY-crzHGiC7eZ8XdV5H_wFTlUGzrf20w/edit XPointer Proposal] (GB)
* Resolving Durand: c.f. http://foxglove.hypotheses.org/368 (LB)

'''15:00 - 16:30''' (tea break ~16:00)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans

'''19:30 - '''
* Supper: http://www.al-shami.co.uk/ (Middle Eastern)

=== Thursday 20 September 2012 ===
Location: Buttery, Wolfson College, Linton Road, Oxford, OX2 6UD

'''09:30 - 10:30''' Items to discuss
* Roma Templates and Example Customizations (from discussion in early September on tei-council)
** Sebastian should explain the purpose of providing downloadable customizations.
** On http://www.tei-c.org/Guidelines/Customization/ and http://www.tei-c.org/Guidelines/Customization/odds.xml , are any modules labeled as experimental that should not be, or any modules not labeled but should be? (Note that currently the dictionaries module is documented differently on these two pages.) Sebastian said that none are experimental any more.
** Roma interface
*** Do we agree with Sebastian removing MS, dict, speech, drama, and corpus from the "Create Customization from template" drop-down menu at http://www.tei-c.org/Roma/ ? He said that Bare, Lite, and Tite make sense since they are coherent and have a purpose, and that SVG, MathML, XInclude, ITS, and ODD are also sensible since they involve non-obvious techniques which you can't recreate easily in Roma. But the remaining five are are not meaningfully useful, documented, or follow any known recommendation. James said they were supplied here as simple example customisations. Martin suggested separating out such options as "advanced".
*** Should we provide template for community-created customisations in Roma that are reasonably mature and well-supported, such as EpiDoc? What would be our management process for this?
** Should we begin generating HTML and PDF documentation for any modules besides Lite and Tite (and putting them in http://www.tei-c.org/release/doc/tei-p5-exemplars/ )?
** For the two sections of customizations at http://www.tei-c.org/Guidelines/Customization/ :
*** Do we want to rename the first heading "Customizations provided by the TEI Consortium" to "Customizations maintained by the TEI Consortium" or "Customizations supported by the TEI Consortium"?
*** Can we clarify what "more restricted or experimental" means? These are not the same thing, and it isn't clear what either means.
*** Do we want to set up a procedure for deciding what can be added to the "TEI Community Customizations" or for periodically revisiting those listed there? Even if not, should we just go ahead and remove MEP from the list since the links are broken and it's not a P3 thing?
*** Do we find the heading "TEI Community Customizations" clear enough, or do we want to add a paragraph here explaining ?
* Div.Liminal (LB)
* LingSIG issues (PB)
* Add yours here
*

'''10:30 - 12:30''' (tea break ~11am)
* Ticket Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''13:30 - 15:00''' Items to discuss
* Board Proposals for Council Consideration (EP)
* We have very similar information on writing ODDs [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#MD in the Guidelines] and [http://www.tei-c.org/Guidelines/Customization/odds.xml#body.1_div.2 on the TEI-C website]. I think these should be merged into one place. Where should the merged documentation be? Can someone review each document to make sure it's accurate before we ask someone to merge the two?
* Questions for candidates (See David Sewell's Email http://lists.village.virginia.edu/pipermail/tei-council/2012/016259.html )
* Add yours here
*

'''15:00 - 16:30''' (tea break ~4pm)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans
* Supper: If weather is nice, we thought about walking up the river from Wolfson to: http://www.victoriaarms.co.uk a nearby pub run by the Oxford Preservation Trust (British pub food). We may even take you here by punt. If weather is not so good we’ll go elsewhere in nearby Summertown.

=== Friday 21 September 2012 ===
Location: Buttery, Wolfson College, Linton Road, Oxford, OX2 6UD

'''09:30 - 10:30''' Items to discuss
* Code Bounties: Decide Topics: (e.g. Roma ReWrite), poss specification brainstorming
* Options for freezing and/or archiving Lite. Planning Lite reLaunch.
* Move TEI to GitHub?
* Deprecation of TEI P4

'''10:30 - 12:30''' (tea break ~11am)
* Ticket Breakout Groups

'''12:30 - 13:30'''
* Lunch

'''13:30 - 15:00''' Items to discuss
* @rend
*
*

'''15:00 - 16:30''' (tea break ~4pm)
* Ticket Breakout Groups

'''16:30 - 17:30'''
* Discussion and supper plans

'''19:30 - '''
* Supper: http://www.mysichuan.co.uk/ (Chinese)

== Teleconference - 2012-08-09 20:00 BST ==
=== Agenda ===

* Brief Reports
** TEI Tite (KH)
** SIG reports (JC)
** Google Books (KH)
** Physical Bibliography (KH)
** ODD Meeting after DH2012 (JC)
** XPointer scheme proposal (GB)
** Face2Face Meeting: arrangements (JC)
* Replacement for SY or not? (JC)
* TEI Lite (LB)
* Reminder to finish off Ann Arbor Actions (JC)
* (more items TBD)

== F2F meeting - Ann Arbor 15-18 April 2012 ==

Turkish-American Friendship Room, Shapiro Science Library

Description : http://www.lib.umich.edu/node/22671/
Location : <location><geo>42.275832 -83.737265</geo></location>

Here is a list of [[AnnArbor2012-Actions]] to be done.

=== Agenda ===
==== Sunday 15 April 10:00-16:00 (optional) ====
Optional TEI HackFest for those arriving early (because of flights including a Saturday being cheaper) or local people who wish to attend.

Possible tasks for the day:

* From Sebastian: "I think there is some problem of ODD processing in a pending ticket which I said was doable with some concentration - was it the idea of redeclaration of attributes (i.e. datatypes) in the P5 source itself?"
* From Sebastian: "We need to reassess what is left over from EEBO/ECCO work which still needs resolving, to give a context for Monday"
* James-C: Vault-related tidying perhaps; Also have some TEI -> MARC (for Google eBooks from TEI -> ePub) XSLT to complete.
* Lou : I would like to work on accomodating some existing TEI-like schemas into proper TEI ODDs. Notably Vogeler's "Charters Encoding Initiative" dtd; other suggestions welcome. How about a proper effort to bring EAD back into the paths of righteousness? (Sebastian says: in a day?????)
* Lou : I would also like to work on some Garage case studies, of the Word -> P5 variety

'''10:00 - 12:30'ish:'''
* Hack on TEI-related development

'''12:30 - 14:30:'''
*lunch

'''14:30 - 16:00:'''
* More TEI-related hacking

'''19:00 -'''
* Supper

==== Monday 16 April 09:00 - 17:30 ====
(Tentative and flexible timetabled agenda)

'''09:00 - 10:00:'''
* TEI - Google Books
* TEI - EEBO / ECCO

'''10:00 - 12:30:'''
* TEI Bugs and FR: (Green and hopefully some amber ones)

'''12:30 - 14:30 (shorter if possible):'''
* Lunch

'''14:30 - 15:30:'''
* TEI and Schematron Tests
* TEI Exemplars (e.g. Tite)
* Best Practices for TEI in Libraries

'''15:30 - 17:30:'''
* TEI Bugs and FR: (Amber)

'''19:00-'''
Supper (optional)

==== Tuesday 17 April 09:00 - 17:30 ====

'''09:00-10:00:'''
* TEI Namespaces and Conformance
* Chapter/module fragmentation and consolidation (e.g. should things like 'dates' become a chapter of its own)
* TEI Examples

'''10:00 - 12:30:'''
* TEI Bugs and FR (Amber)

'''12:30 - 14:30:'''
* 'Open Lunch' with people from University of Michigan community interested in meeting us

'''14:30 - 15:30:'''
* TEI FR: Floating Div
* TEI ODD Meeting

'''15:30 - 17:30:'''
* TEI Bugs and FR (Amber)

'''19:00-'''
Supper (optional)

==== Wednesday 18 April 09:00 - 16:00 ====

'''09:00 - 10:00:'''
* TEI and URIs
* TEI Release Process
* TEI Outreach and Education
* Any Other Council Business

'''10:00 - 12:30:'''
* Bugs and FR (Amber / Red)

'''12:30 - 14:30 (or shorter):'''
* Lunch

'''14:30 - 16:00 (or longer?):'''
* Bugs and FR: outstanding / summary
*(early end for those who need flights)

== Teleconference - Tuesday 28 February 2012 at 18:00 GMT ==
# Brief Reports
## [[Ad-hoc_committee_on_encoding_of_bibliographic_citations|Bibliographic Citations]] (KH & MH)
## TEI Tite (KH)
## TEI and AdBlock (MH)
## Google Books (KH)
## Xpointer (GB)
## Attribute Datatypes (MH)
## Physical Bibliography (KH)
## TEI Release Process Document (MH)
## Future of ODD meeting, DH2012 (JC)
# @ref/key/cRef & Private URI Schemes (MH)
# Best Practices for TEI in Libraries (KH)
# Practical Arrangements for April Face2Face (RW)
# Agenda for the April Face2Face (JC)
# AOB

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* organisational:
** 9:30: breakfast
** 12:30: lunch at Pizzeria Via Italia (Pizzeria Via Italia - 21, avenue d'Italie - 01 42 16 97 89)
** 15:30: coffee break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût (L'avant Goût - 26, rue Bobillot - 01 53 80 24 00)
** 15:30: coffee break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffee break
* topical
** Wiki access restrictions
** P4 survey

** grp vs. list
** Magic tokens
** translations

** P6 discussion and visions
** community project
** core too big
** modifying attributes from a class
** revamping Roma
** Planning priorities for next year

=== Minutes/notes Paris 2011 Meeting ===

* [http://www.tei-c.org/Activities/Council/Meetings/tcm48.xml minutes in TEI]
* [[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== Agenda ===
Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on editing the Guidelines (Lou cf. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kevin for TEI PUB SIG?)
* deprecation, beta, etc.

* automatic generation of feeds/twitts from SF tickets (new ones; solved ones)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== TEI and Google ====

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

SY Gate is a really good flexible framework that includes tokenisation, but only pretends to do XML: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

KH: cf. http://purl.oclc.org/NET/teiinlibraries

=== Minutes ====

[http://www.tei-c.org/Activities/Council/Meetings/tcm46.xml Minutes of the Chicago meeting for reference]

== Item for further consideration ==
* Stable URIs to discrete bits of the guidelines
* [[Council FR assignments]]

== F2F meeting - Dublin 28-30 April 2010 ==

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* Manuscript (genetic editions)
* Second SF session
* 4 p.m.: biblStruct

==== Friday morning ====
* hyphenation
* ODD - (r)evolutions
* Third SF session
==== Friday afternoon ====
* remaining issues
* prospective

=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

=== Minutes ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml Minutes of the Dublin meeting for reference]

== Ad-hoc committee on encoding of bibliographic citations ==

[[Ad-hoc committee on encoding of bibliographic citations]]

== Telko October 2009 ==
=== Connexion details ===

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:
*Domestic*

USA USA 1-201-793-9022
Canada Canada 1-201-793-9022
Long distance costs apply
*International*

Austria Austria 0820 401 15470
Belgium Belgium 0703 57 134
France France 0826 109 071
Germany Germany 01805 00 9527
Ireland Ireland 0818 270 968
Italy Italy 848 390 177
Spain Spain 902 885 791
Switzerland Switzerland 0848 560 397
United Kingdom United Kingdom 0870 0990 931

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content
* report to TEI MM

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml Minutes of the October meeting for reference]
* Bug and features - SF
* Focussed technical discussions
** Placement of schematron constraints in ODD - Sebastian Rahtz
** Discussion of "canonical way of referencing TEI element definitions"
** Wider debate: the future of ODD
(SourceForge item 2411994) and related issue of permanent URLs for TEI
documentation - David Sewell
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 SF ID: 2411994]
** Reporting on stylesheets (SR, DOD)
*** Evolution towards XSL 2.0
**** main advantages (features) provided by a switch to 2.0
**** consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
**** how much of this should be known by the TEI community?

* Getting started (PB)
* Projects
** TEI - ISO
* Perspective workshop on TEI for the next decade
** communities
*** role of TEI in research infrastructures (AC)
**event
*** Dagstuhl
*** ESF [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd:
They used to be at
http://www.tei-c.org/Vault/GL/P1/ [source only]
http://www.tei-c.org/Vault/GL/P2/ [source only]
http://www.tei-c.org/Vault/GL/P3/index.htm [source in P3X/]

But I don't know where old stuff went when we moved to the new
website. In any case, there are copies of P3 at:
http://quod.lib.umich.edu/t/tei/
http://etext.virginia.edu/standards/tei/teip3/

== Council Telco - 21 August 2008 ==
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml
== Issues for next Telco - Oct 2008 ==
* update on SF bugs and features (Oxford)

* report to TEI MM

* naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ([http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html]) about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

* update on SIGs + responsabilities

* placement of Schematron rules in ODD
http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html

Note to be produced by SR

* update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and [[Getting Started]]

Looking for candidates:
** 6. Choosing and installing an editor
** 9. Getting this to work on sample of own text
** 11. Where to go from here

== Issues for next F2F ==

* Discussion on ODD and its evolution--[[User:Romary|Romary]] 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)

Namespaces

* Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

* should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

== Highlights to be brought to the TEI MM 2008 ==

== Topics (could be moved up to one F2F or Telco meeting ==

* Stable reference to TEI objects

(For original source of these comments, see tei-council thread [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|stable references]].)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in http://www.tei-c.org/ns/1.0), sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>: http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html
but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e.
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log
which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:
http://www.tei-c.org/Guidelines/access.xml

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we
might want to consider adopting one or another of the standard systems
for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to
register the DOIs with one of the national registries, but some more
extensive costs in human time to set up a good system for mapping from
our existing nomenclature to a set of DOI identifiers. (Publishers
typically use DOIs to identify individual books or journal articles, but
they can be more granular: every reference page in the Guidelines could
have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using
DOIs for citations could simply cite a DOI. So instead of the reference
for <name> in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

which would be resolved to the actual Web address by a DOI resolver.
(Many journal DOIs are mostly numeric but the syntax allows more
human-readable names).

If we seriously want to consider an option like this, we should put out
a call to the librarians/metadata gurus in our community for assistance
with implementation.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

AttsWithoutEgs

2012-09-20T21:50:18Z

Brettttt:

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

List generated 2012-04-23T08:14:26.517-07:00

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Claimed By
! Completed
|-
|| 1 || absolute || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 2 || adj || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 3 || adjFrom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 4 || adjTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 5 || age || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-personGrp.html personGrp] || ||
|-
|| 6 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 7 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || BW ||
|-
|| 8 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 9 || ana || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.analytic.html att.global.analytic] || ||
|-
|| 10 || atLeast || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || BB ||
|-
|| 11 || atMost || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || BB ||
|-
|| 12 || attachment || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 13 || autoPrefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-content.html content] || ||
|-
|| 14 || baseTypes || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fsDecl.html fsDecl] || ||
|-
|| 15 || break || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.breaking.html att.breaking] || MDH || 2012-05-20
|-
|| 16 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss] || ||
|-
|| 17 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term] || ||
|-
|| 18 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ptr.html ptr] || ||
|-
|| 19 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ref.html ref] || ||
|-
|| 20 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 21 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 22 || cert || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 23 || change || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.change.html att.global.change] || ||
|-
|| 24 || class || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-msContents.html msContents] || ||
|-
|| 25 || cols || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 26 || confidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 27 || contemporary || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-seal.html seal] || ||
|-
|| 28 || copyOf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 29 || corresp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || MDH || 2012-05-20
|-
|| 30 || datingMethod || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 31 || datingPoint || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 32 || decls || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declaring.html att.declaring] || ||
|-
|| 33 || default || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declarable.html att.declarable] || ||
|-
| 34 || defective || att.ms<nowiki/>Excerpt || ||
|-
|| 35 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 36 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 37 || dim || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || BB ||
|-
|| 38 || direct || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said] || MDH || 2012-05-21
|-
|| 39 || docLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 40 || domains || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 41 || dur || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.att.duration.w3c.html att.duration.w3c] || ||
|-
|| 42 || dur-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.duration.iso.html att.duration.iso] || ||
|-
|| 43 || encoding || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 44 || end || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 45 || enjamb || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.enjamb.html att.enjamb] || BW ||
|-
|| 46 || evaluate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.html att.pointing] || ||
|-
|| 47 || evidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 48 || except || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 49 || exclude || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 50 || expand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 51 || extent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-orth.html orth] || ||
|-
|| 52 || fVal || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-f.html f] || ||
|-
|| 53 || facs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.facs.html att.global.facs] || ||
|-
|| 54 || feats || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fs.html fs] || ||
|-
|| 55 || filter || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-equiv.html equiv] || ||
|-
|| 56 || flipping || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 57 || follow || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 58 || force || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 59 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || BB ||
|-
|| 60 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 61 || from-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 62 || from-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 63 || full || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 64 || function || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 65 || generate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classSpec.html classSpec] || ||
|-
|| 66 || gradual || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 67 || group || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 68 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 69 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 70 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || ||
|-
|| 71 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 72 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 73 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 74 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 75 || ident || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 76 || inst || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 77 || instant || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 78 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || SY || 2012-06-06
|-
|| 79 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classRef.html classRef] || ||
|-
|| 80 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-macroRef.html macroRef] || ||
|-
|| 81 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title] || ||
|-
|| 82 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sense.html sense] || ||
|-
|| 83 || loc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 84 || location || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 85 || lrx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 86 || lry || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 87 || material || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-supportDesc.html supportDesc] || ||
|-
|| 88 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 89 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 90 || medium || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 91 || mergedIn || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 92 || met || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 93 || method || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 94 || mimeType || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.internetMedia.html att.internetMedia] || ||
|-
|| 95 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 96 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 97 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classes.html classes] || ||
|-
|| 98 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 99 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.combinable.html att.combinable] || ||
|-
|| 100 || module || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 101 || new || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-handShift.html handShift] || ||
|-
|| 102 || next || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 103 || notAfter-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 104 || notAfter-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 105 || notBefore-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 106 || notBefore-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 107 || notation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pron.html pron] || ||
|-
|| 108 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 109 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 110 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attDef.html attDef] || ||
|-
|| 111 || nymRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 112 || opt || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 113 || optional || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fDecl.html fDecl] || ||
|-
|| 114 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 115 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 116 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 117 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attList.html attList] || ||
|-
|| 118 || orig || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 119 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 120 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 121 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html ab] || ||
|-
|| 122 || parts || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-nym.html nym] || ||
|-
|| 123 || perf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tech.html tech] || ||
|-
|| 124 || period || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.html att.datable] || ||
|-
|| 125 || pre || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 126 || precision || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 127 || predeclare || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 128 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 129 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 130 || prev || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 131 || quantity || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || BB ||
|-
|| 132 || real || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 133 || ref || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || ||
|-
|| 134 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || BB ||
|-
|| 135 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 136 || rhyme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 137 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 138 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 139 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-org.html org] || ||
|-
|| 140 || rotate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone] || ||
|-
|| 141 || rows || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 142 || sameAs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 143 || sample || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 144 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 145 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 146 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-catRef.html catRef] || ||
|-
|| 147 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locus.html locus] || ||
|-
|| 148 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locusGrp.html locusGrp] || ||
|-
|| 149 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tag.html tag] || ||
|-
|| 150 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 151 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 152 || scribe || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 153 || scribeRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 154 || script || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 155 || scriptRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 156 || select || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 157 || seq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 158 || social || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 159 || sort || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 160 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 161 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.readFrom.html att.readFrom] || ||
|-
|| 162 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 163 || space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 164 || spanTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.spanning.html att.spanning] || BB ||
|-
|| 165 || split || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 166 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 167 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 168 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 169 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 170 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 171 || stdDeviation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-precision.html precision] || ||
|-
|| 172 || subtype || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || pfs ||
|-
|| 173 || synch || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 174 || targFunc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 175 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-change.html change] || ||
|-
|| 176 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relatedItem.html relatedItem] || ||
|-
|| 177 || targetEnd || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-note.html note] || ||
|-
|| 178 || targetLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 179 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-link.html link] || ||
|-
|| 180 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html join] || ||
|-
|| 181 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html alt] || ||
|-
|| 182 || time || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 183 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 184 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 185 || to-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 186 || to-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 187 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 188 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || SY || 2012-06-06
|-
|| 189 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-q.html q] || ||
|-
|| 190 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-abbr.html abbr] || ||
|-
|| 191 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sound.html sound] || ||
|-
|| 192 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.entryLike.html att.entryLike] || | |
|-
|| 193 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-form.html form] || ||
|-
|| 194 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 195 || ulx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 196 || uly || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 197 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || BB ||
|-
|| 198 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 199 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 200 || url || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 201 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 202 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || ||
|-
|| 203 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 204 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 205 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 206 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-eTree.html eTree] || ||
|-
|| 207 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-triangle.html triangle] || ||
|-
|| 208 || varSeq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 209 || version || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unicodeName.html unicodeName] || ||
|-
|| 210 || versionDate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.translatable.html att.translatable] || ||
|-
|| 211 || when || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-docDate.html docDate] || ||
|-
|| 212 || where || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html event] || ||
|-
|| 213 || who || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ascribed.html att.ascribed] || ||
|-
|| 214 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 215 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 216 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.rdgPart.html att.rdgPart] || ||
|-
|| 217 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.witnessed.html att.witnessed] || ||
|-
|| 218 || xml:base || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || || Appears to be done already
|-
|| 219 || xml:id || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|-
|| 220 || xml:lang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || SY || 2012-06-06
|-
|| 221 || xml:space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|}

AttsWithoutEgs

2012-09-20T21:37:15Z

Brettttt:

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

List generated 2012-04-23T08:14:26.517-07:00

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Claimed By
! Completed
|-
|| 1 || absolute || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 2 || adj || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 3 || adjFrom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 4 || adjTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 5 || age || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-personGrp.html personGrp] || ||
|-
|| 6 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 7 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || BW ||
|-
|| 8 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 9 || ana || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.analytic.html att.global.analytic] || ||
|-
|| 10 || atLeast || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || BB ||
|-
|| 11 || atMost || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || BB ||
|-
|| 12 || attachment || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 13 || autoPrefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-content.html content] || ||
|-
|| 14 || baseTypes || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fsDecl.html fsDecl] || ||
|-
|| 15 || break || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.breaking.html att.breaking] || MDH || 2012-05-20
|-
|| 16 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss] || ||
|-
|| 17 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term] || ||
|-
|| 18 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ptr.html ptr] || ||
|-
|| 19 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ref.html ref] || ||
|-
|| 20 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 21 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 22 || cert || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 23 || change || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.change.html att.global.change] || ||
|-
|| 24 || class || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-msContents.html msContents] || ||
|-
|| 25 || cols || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 26 || confidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 27 || contemporary || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-seal.html seal] || ||
|-
|| 28 || copyOf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 29 || corresp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || MDH || 2012-05-20
|-
|| 30 || datingMethod || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 31 || datingPoint || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 32 || decls || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declaring.html att.declaring] || ||
|-
|| 33 || default || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declarable.html att.declarable] || ||
|-
| 34 || defective || att.ms<nowiki/>Excerpt || ||
|-
|| 35 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 36 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 37 || dim || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 38 || direct || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said] || MDH || 2012-05-21
|-
|| 39 || docLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 40 || domains || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 41 || dur || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.att.duration.w3c.html att.duration.w3c] || ||
|-
|| 42 || dur-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.duration.iso.html att.duration.iso] || ||
|-
|| 43 || encoding || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 44 || end || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 45 || enjamb || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.enjamb.html att.enjamb] || BW ||
|-
|| 46 || evaluate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.html att.pointing] || ||
|-
|| 47 || evidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 48 || except || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 49 || exclude || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 50 || expand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 51 || extent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-orth.html orth] || ||
|-
|| 52 || fVal || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-f.html f] || ||
|-
|| 53 || facs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.facs.html att.global.facs] || ||
|-
|| 54 || feats || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fs.html fs] || ||
|-
|| 55 || filter || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-equiv.html equiv] || ||
|-
|| 56 || flipping || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 57 || follow || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 58 || force || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 59 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 60 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 61 || from-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 62 || from-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 63 || full || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 64 || function || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 65 || generate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classSpec.html classSpec] || ||
|-
|| 66 || gradual || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 67 || group || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 68 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 69 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 70 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || ||
|-
|| 71 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 72 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 73 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 74 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 75 || ident || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 76 || inst || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 77 || instant || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 78 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || SY || 2012-06-06
|-
|| 79 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classRef.html classRef] || ||
|-
|| 80 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-macroRef.html macroRef] || ||
|-
|| 81 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title] || ||
|-
|| 82 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sense.html sense] || ||
|-
|| 83 || loc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 84 || location || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 85 || lrx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 86 || lry || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 87 || material || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-supportDesc.html supportDesc] || ||
|-
|| 88 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 89 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 90 || medium || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 91 || mergedIn || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 92 || met || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 93 || method || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 94 || mimeType || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.internetMedia.html att.internetMedia] || ||
|-
|| 95 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 96 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 97 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classes.html classes] || ||
|-
|| 98 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 99 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.combinable.html att.combinable] || ||
|-
|| 100 || module || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 101 || new || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-handShift.html handShift] || ||
|-
|| 102 || next || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 103 || notAfter-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 104 || notAfter-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 105 || notBefore-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 106 || notBefore-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 107 || notation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pron.html pron] || ||
|-
|| 108 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 109 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 110 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attDef.html attDef] || ||
|-
|| 111 || nymRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 112 || opt || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 113 || optional || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fDecl.html fDecl] || ||
|-
|| 114 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 115 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 116 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 117 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attList.html attList] || ||
|-
|| 118 || orig || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 119 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 120 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 121 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html ab] || ||
|-
|| 122 || parts || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-nym.html nym] || ||
|-
|| 123 || perf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tech.html tech] || ||
|-
|| 124 || period || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.html att.datable] || ||
|-
|| 125 || pre || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 126 || precision || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 127 || predeclare || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 128 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 129 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 130 || prev || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 131 || quantity || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 132 || real || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 133 || ref || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || ||
|-
|| 134 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 135 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 136 || rhyme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 137 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 138 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 139 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-org.html org] || ||
|-
|| 140 || rotate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone] || ||
|-
|| 141 || rows || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 142 || sameAs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 143 || sample || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 144 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 145 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 146 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-catRef.html catRef] || ||
|-
|| 147 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locus.html locus] || ||
|-
|| 148 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locusGrp.html locusGrp] || ||
|-
|| 149 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tag.html tag] || ||
|-
|| 150 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 151 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 152 || scribe || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 153 || scribeRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 154 || script || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 155 || scriptRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 156 || select || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 157 || seq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 158 || social || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 159 || sort || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 160 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 161 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.readFrom.html att.readFrom] || ||
|-
|| 162 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 163 || space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 164 || spanTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.spanning.html att.spanning] || ||
|-
|| 165 || split || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 166 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 167 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 168 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 169 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 170 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 171 || stdDeviation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-precision.html precision] || ||
|-
|| 172 || subtype || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || pfs ||
|-
|| 173 || synch || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 174 || targFunc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 175 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-change.html change] || ||
|-
|| 176 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relatedItem.html relatedItem] || ||
|-
|| 177 || targetEnd || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-note.html note] || ||
|-
|| 178 || targetLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 179 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-link.html link] || ||
|-
|| 180 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html join] || ||
|-
|| 181 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html alt] || ||
|-
|| 182 || time || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 183 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 184 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 185 || to-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 186 || to-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 187 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 188 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || SY || 2012-06-06
|-
|| 189 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-q.html q] || ||
|-
|| 190 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-abbr.html abbr] || ||
|-
|| 191 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sound.html sound] || ||
|-
|| 192 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.entryLike.html att.entryLike] || | |
|-
|| 193 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-form.html form] || ||
|-
|| 194 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 195 || ulx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 196 || uly || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 197 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 198 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 199 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 200 || url || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 201 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 202 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || ||
|-
|| 203 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 204 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 205 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 206 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-eTree.html eTree] || ||
|-
|| 207 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-triangle.html triangle] || ||
|-
|| 208 || varSeq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 209 || version || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unicodeName.html unicodeName] || ||
|-
|| 210 || versionDate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.translatable.html att.translatable] || ||
|-
|| 211 || when || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-docDate.html docDate] || ||
|-
|| 212 || where || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html event] || ||
|-
|| 213 || who || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ascribed.html att.ascribed] || ||
|-
|| 214 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 215 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 216 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.rdgPart.html att.rdgPart] || ||
|-
|| 217 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.witnessed.html att.witnessed] || ||
|-
|| 218 || xml:base || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || || Appears to be done already
|-
|| 219 || xml:id || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|-
|| 220 || xml:lang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || SY || 2012-06-06
|-
|| 221 || xml:space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|}

ODD

2011-04-13T22:43:10Z

Brettttt:

'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Documentation Elements] module.

== Description ==
The TEI Guidelines, its DTD, and its schema fragments, are all produced from a single XML resource containing:

# Descriptive prose (lots of it)
# Examples of usage (plenty)
# Formal declarations for components of the TEI Abstract Model:
## elements and attributes
## modules
## classes and macros

We call this resource an ODD (One Document Does it all), although the master source is instantiated as a gazillion XML mini-documents.

A system of XSLT stylesheets called [[Roma]] has been created for the purpose of easy manipulation of ODD files.

== Example ==
The TEI scheme can only be used by customizing it. Customizations are also expressed in the ODD language. For example:

<pre>
<schemaSpec ident="myTEIlite">
<desc>This is TEI Lite with simplified heads</desc>
<moduleRef name="teistructure"/>
<moduleRef name="linking"/>
<moduleRef name="core"/>
<moduleRef name="teiheader"/>
<elementSpec ident="head" mode="change">
<content><rng:text/></content>
</elementSpec>
</schemaSpec>
</pre>

produces the schema for TEI Lite, with a slight change.

== Uses besides the TEI Guidelines and various customizations ==

* [http://www.w3.org/TR/its/ Internationalization Tag Set (ITS)]
* various standards proposal designed within ISO committee TC 37 have been totally or partially written in TEI/ODD: MLIF, MAF, ISO 16642 rev., ISOTimeML

== Future plans ==

Over the years ODD has evolved progressively to reflect more and more needs of the TEI community, both as the core specification language for the TEI guidelines, but also as generic customization language for any TEI users. Still ODD remains a hybrid environment combining its own vacabulary with RelaxNG fragments and at times, validation vocabularies from external languages (e.g. Schematron). The TEI council contemplates putting on its work program a revision of the ODD infrastructure, considering either to drop it altogether in favor of one existing schema language, or extend its capabilities to make it a self contained and generic specification language. Some thoughts are included at [[ODD-dev]].

== See also ==
*[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
*[http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
*[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop
*[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
*[http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
* [http://conferences.idealliance.org/extreme/html/2004/Bauman01/EML2004Bauman01.html Odd Customizations], by Syd Bauman and Julia Flanders.
* [http://conferences.idealliance.org/extreme/html/2004/Burnard01/EML2004Burnard01.html RelaxNG with Son of ODD], by Lou Burnard and Sebastian Rahtz.
* [http://www.balisage.net/Proceedings/vol1/html/Bauman01/BalisageVol1-Bauman01.html Freedom to Constrain] by Syd Bauman

[[Category:Customization|!]]

TEI-Council-FAQ

2011-04-13T22:21:18Z

Brettttt: /* Why are some people from Oxford and Virginia on the Council email list, and why do they attend Council meetings, even though they are not on the list of elected members? */

So you've been elected to the TEI Technical Council and have some questions about how things work. This page has been set up to answer questions that new council members may have. It is entirely unofficial. See in first instance, http://www.tei-c.org/Council/

== 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 Lou Burnard makes an executive decision on the ticket. If it's a corrigible error, he just fixes it in the appropriate ODD file(s) (also in SoureForge). If he thinks it's not a real issue, he closes the ticket. (If you want to comment on a ticket after it has been closed, you'll need to email Lou and ask him to re-open the ticket.) Otherwise, it's discussed 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 Lou 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... The editors have the responsibility of ensuring that the Guidelines are intellectually coherent and well expressed, but they do not have the last word on what they actually say: the Council does.

== What funding is available for Council Activities? ==

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. If you have questions about reimbursement procedures, including what is reimbursable, please email Sarah Wells, the TEI treasurer, at spw4s AT virginia.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 are the teleconferences held? ==

Currently the TEI Council uses the teleconferencing facilities provided by the institution of a council member. This involves a long distance call for most people participating in the teleconference. The TEI Council has been investigating other forms of teleconferencing, specifically VOIP-related software.

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.

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

The minutes of previous meetings are stored on the TEI website, see http://www.tei-c.org/Council/

== 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. The list is maintained by [mailto:dsewell@virginia.edu David Sewell] in Virginia.

== Where do I find the Trac system? ==

In the work with TEI P5 we used the Trac system, see http://tei.oucs.ox.ac.uk/trac/TEIP5/ . Trac is a minimalistic approach to web-based management of software projects. The success was limited, but it was used to some extent, but '''we probably won't continue to use it'''.

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

To find a known ticket number ("attribute ID"), either:

* Browse bugs or feature requests and filter by attribute ID. Note that in order to go back to browsing other feature requests, you will need to reset the filter.

* Use short URLs created by James Cummings appending the attribute ID to the end of the appropriate one of the two URLs:

<nowiki>
http://sn.im/tei-bugs&aid=
</nowiki>

<nowiki>
http://sn.im/tei-fr&aid=
</nowiki>

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

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

== Why are some people from Oxford and Virginia on the Council email list, and why do they attend Council meetings, even though they are not on the list of elected members? ==

Part of Oxford's contribution as a TEI host institution is its "editorial support group" for the TEI—currently Lou Burnard, James Cummings and Sebastian Rahtz. They administer the SourceForge code repository and ticketing system and make most of the changes to the ODDs for the Guidelines. As such they are allowed to attend meetings as representatives of the editorial support group. However, currently Lou Burnard is an elected member of the TEI Board and attends Council meetings as its representative, and both James Cummings and Sebastian Rahtz are elected members of the TEI Council. Any list of elected members should contain their names. Similarly the Web Master (currently David Sewell at Virginia) is also a member of the TEI Council mailing list.

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

2011-04-13T21:08:36Z

Brettttt: /* How do I use subversion? */

So you've been elected to the TEI Technical Council and have some questions about how things work. This page has been set up to answer questions that new council members may have. It is entirely unofficial. See in first instance, http://www.tei-c.org/Council/

== 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 Lou Burnard makes an executive decision on the ticket. If it's a corrigible error, he just fixes it in the appropriate ODD file(s) (also in SoureForge). If he thinks it's not a real issue, he closes the ticket. (If you want to comment on a ticket after it has been closed, you'll need to email Lou and ask him to re-open the ticket.) Otherwise, it's discussed 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 Lou 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... The editors have the responsibility of ensuring that the Guidelines are intellectually coherent and well expressed, but they do not have the last word on what they actually say: the Council does.

== What funding is available for Council Activities? ==

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. If you have questions about reimbursement procedures, including what is reimbursable, please email Sarah Wells, the TEI treasurer, at spw4s AT virginia.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 are the teleconferences held? ==

Currently the TEI Council uses the teleconferencing facilities provided by the institution of a council member. This involves a long distance call for most people participating in the teleconference. The TEI Council has been investigating other forms of teleconferencing, specifically VOIP-related software.

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.

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

The minutes of previous meetings are stored on the TEI website, see http://www.tei-c.org/Council/

== 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. The list is maintained by [mailto:dsewell@virginia.edu David Sewell] in Virginia.

== Where do I find the Trac system? ==

In the work with TEI P5 we used the Trac system, see http://tei.oucs.ox.ac.uk/trac/TEIP5/ . Trac is a minimalistic approach to web-based management of software projects. The success was limited, but it was used to some extent, but '''we probably won't continue to use it'''.

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

To find a known ticket number ("attribute ID"), either:

* Browse bugs or feature requests and filter by attribute ID. Note that in order to go back to browsing other feature requests, you will need to reset the filter.

* Use short URLs created by James Cummings appending the attribute ID to the end of the appropriate one of the two URLs:

<nowiki>
http://sn.im/tei-bugs&aid=
</nowiki>

<nowiki>
http://sn.im/tei-fr&aid=
</nowiki>

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

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

== Why are some people from Oxford and Virginia on the Council email list, and why do they attend Council meetings, even though they are not on the list of elected members? ==

Part of Oxford's contribution as a TEI host institution is its "editorial support group" for the TEI—currently Lou Burnard, James Cummings and Sebastian Rahtz. They administer the SourceForge code repository and ticketing system and make most of the changes to the ODDs for the Guidelines. As such they would be allowed to attend meetings as representatives of the editorial support group. However, currently Lou Burnard is an elected member of the TEI Board and attends Council meetings as a representative, and both James Cummings and Sebastian Rahtz are elected members of the TEI Council. Any list of elected members should contain their names. Similarly the Web Master (currently David Sewell at Virginia) is also a member of the TEI Council mailing list.

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

2011-04-13T21:07:58Z

Brettttt: /* How do I use subversion? */

So you've been elected to the TEI Technical Council and have some questions about how things work. This page has been set up to answer questions that new council members may have. It is entirely unofficial. See in first instance, http://www.tei-c.org/Council/

== 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 Lou Burnard makes an executive decision on the ticket. If it's a corrigible error, he just fixes it in the appropriate ODD file(s) (also in SoureForge). If he thinks it's not a real issue, he closes the ticket. (If you want to comment on a ticket after it has been closed, you'll need to email Lou and ask him to re-open the ticket.) Otherwise, it's discussed 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 Lou 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... The editors have the responsibility of ensuring that the Guidelines are intellectually coherent and well expressed, but they do not have the last word on what they actually say: the Council does.

== What funding is available for Council Activities? ==

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. If you have questions about reimbursement procedures, including what is reimbursable, please email Sarah Wells, the TEI treasurer, at spw4s AT virginia.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 are the teleconferences held? ==

Currently the TEI Council uses the teleconferencing facilities provided by the institution of a council member. This involves a long distance call for most people participating in the teleconference. The TEI Council has been investigating other forms of teleconferencing, specifically VOIP-related software.

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.

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

The minutes of previous meetings are stored on the TEI website, see http://www.tei-c.org/Council/

== 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. The list is maintained by [mailto:dsewell@virginia.edu David Sewell] in Virginia.

== Where do I find the Trac system? ==

In the work with TEI P5 we used the Trac system, see http://tei.oucs.ox.ac.uk/trac/TEIP5/ . Trac is a minimalistic approach to web-based management of software projects. The success was limited, but it was used to some extent, but '''we probably won't continue to use it'''.

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

To find a known ticket number ("attribute ID"), either:

* Browse bugs or feature requests and filter by attribute ID. Note that in order to go back to browsing other feature requests, you will need to reset the filter.

* Use short URLs created by James Cummings appending the attribute ID to the end of the appropriate one of the two URLs:

<nowiki>
http://sn.im/tei-bugs&aid=
</nowiki>

<nowiki>
http://sn.im/tei-fr&aid=
</nowiki>

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

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

== Why are some people from Oxford and Virginia on the Council email list, and why do they attend Council meetings, even though they are not on the list of elected members? ==

Part of Oxford's contribution as a TEI host institution is its "editorial support group" for the TEI—currently Lou Burnard, James Cummings and Sebastian Rahtz. They administer the SourceForge code repository and ticketing system and make most of the changes to the ODDs for the Guidelines. As such they would be allowed to attend meetings as representatives of the editorial support group. However, currently Lou Burnard is an elected member of the TEI Board and attends Council meetings as a representative, and both James Cummings and Sebastian Rahtz are elected members of the TEI Council. Any list of elected members should contain their names. Similarly the Web Master (currently David Sewell at Virginia) is also a member of the TEI Council mailing list.

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

Council

2011-04-10T22:20:14Z

Brettttt: /* Item for further consideration */

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents.

== F2F meeting - Chicago 11-13 April 2010 ==

=== Agenda ===
Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on editing the Guidelines (Lou cf. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kevin for TEI PUB SIG?)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== TEI and Google ====

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

KH: cf. http://purl.oclc.org/NET/teiinlibraries

== Item for further consideration ==
* Stable URIs to discrete bits of the guidelines
* [[Council FR assignments]]

== F2F meeting - Dublin 28-30 April 2010 ==

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* Manuscript (genetic editions)
* Second SF session
* 4 p.m.: biblStruct

==== Friday morning ====
* hyphenation
* ODD - (r)evolutions
* Third SF session
==== Friday afternoon ====
* remaining issues
* prospective

=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

=== Minutes ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== Ad-hoc committee on encoding of bibliographic citations ==

[[Ad-hoc committee on encoding of bibliographic citations]]

== Telko October 2009 ==
=== Connexion details ===

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:
*Domestic*

USA USA 1-201-793-9022
Canada Canada 1-201-793-9022
Long distance costs apply
*International*

Austria Austria 0820 401 15470
Belgium Belgium 0703 57 134
France France 0826 109 071
Germany Germany 01805 00 9527
Ireland Ireland 0818 270 968
Italy Italy 848 390 177
Spain Spain 902 885 791
Switzerland Switzerland 0848 560 397
United Kingdom United Kingdom 0870 0990 931

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content
* report to TEI MM

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml Minutes of the October meeting for reference]
* Bug and features - SF
* Focussed technical discussions
** Placement of schematron constraints in ODD - Sebastian Rahtz
** Discussion of "canonical way of referencing TEI element definitions"
** Wider debate: the future of ODD
(SourceForge item 2411994) and related issue of permanent URLs for TEI
documentation - David Sewell
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 SF ID: 2411994]
** Reporting on stylesheets (SR, DOD)
*** Evolution towards XSL 2.0
**** main advantages (features) provided by a switch to 2.0
**** consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
**** how much of this should be known by the TEI community?

* Getting started (PB)
* Projects
** TEI - ISO
* Perspective workshop on TEI for the next decade
** communities
*** role of TEI in research infrastructures (AC)
**event
*** Dagstuhl
*** ESF [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd:
They used to be at
http://www.tei-c.org/Vault/GL/P1/ [source only]
http://www.tei-c.org/Vault/GL/P2/ [source only]
http://www.tei-c.org/Vault/GL/P3/index.htm [source in P3X/]

But I don't know where old stuff went when we moved to the new
website. In any case, there are copies of P3 at:
http://quod.lib.umich.edu/t/tei/
http://etext.virginia.edu/standards/tei/teip3/

== Council Telco - 21 August 2008 ==
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml
== Issues for next Telco - Oct 2008 ==
* update on SF bugs and features (Oxford)

* report to TEI MM

* naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ([http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html]) about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

* update on SIGs + responsabilities

* placement of Schematron rules in ODD
http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html

Note to be produced by SR

* update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and [[Getting Started]]

Looking for candidates:
** 6. Choosing and installing an editor
** 9. Getting this to work on sample of own text
** 11. Where to go from here

== Issues for next F2F ==

* Discussion on ODD and its evolution--[[User:Romary|Romary]] 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)

Namespaces

* Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

* should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

== Highlights to be brought to the TEI MM 2008 ==

== Topics (could be moved up to one F2F or Telco meeting ==

* Stable reference to TEI objects

(For original source of these comments, see tei-council thread [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|stable references]].)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in http://www.tei-c.org/ns/1.0), sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>: http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html
but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e.
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log
which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:
http://www.tei-c.org/Guidelines/access.xml

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we
might want to consider adopting one or another of the standard systems
for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to
register the DOIs with one of the national registries, but some more
extensive costs in human time to set up a good system for mapping from
our existing nomenclature to a set of DOI identifiers. (Publishers
typically use DOIs to identify individual books or journal articles, but
they can be more granular: every reference page in the Guidelines could
have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using
DOIs for citations could simply cite a DOI. So instead of the reference
for <name> in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

which would be resolved to the actual Web address by a DOI resolver.
(Many journal DOIs are mostly numeric but the syntax allows more
human-readable names).

If we seriously want to consider an option like this, we should put out
a call to the librarians/metadata gurus in our community for assistance
with implementation.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-04-10T22:19:32Z

Brettttt: /* TEI and Google */

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents.

== F2F meeting - Chicago 11-13 April 2010 ==

=== Agenda ===
Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on editing the Guidelines (Lou cf. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kevin for TEI PUB SIG?)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== TEI and Google ====

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

KH: cf. http://purl.oclc.org/NET/teiinlibraries

== Item for further consideration ==
* Stable URIs to whatever bits of the guidelines
* [[Council FR assignments]]

== F2F meeting - Dublin 28-30 April 2010 ==

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* Manuscript (genetic editions)
* Second SF session
* 4 p.m.: biblStruct

==== Friday morning ====
* hyphenation
* ODD - (r)evolutions
* Third SF session
==== Friday afternoon ====
* remaining issues
* prospective

=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

=== Minutes ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== Ad-hoc committee on encoding of bibliographic citations ==

[[Ad-hoc committee on encoding of bibliographic citations]]

== Telko October 2009 ==
=== Connexion details ===

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:
*Domestic*

USA USA 1-201-793-9022
Canada Canada 1-201-793-9022
Long distance costs apply
*International*

Austria Austria 0820 401 15470
Belgium Belgium 0703 57 134
France France 0826 109 071
Germany Germany 01805 00 9527
Ireland Ireland 0818 270 968
Italy Italy 848 390 177
Spain Spain 902 885 791
Switzerland Switzerland 0848 560 397
United Kingdom United Kingdom 0870 0990 931

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content
* report to TEI MM

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml Minutes of the October meeting for reference]
* Bug and features - SF
* Focussed technical discussions
** Placement of schematron constraints in ODD - Sebastian Rahtz
** Discussion of "canonical way of referencing TEI element definitions"
** Wider debate: the future of ODD
(SourceForge item 2411994) and related issue of permanent URLs for TEI
documentation - David Sewell
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 SF ID: 2411994]
** Reporting on stylesheets (SR, DOD)
*** Evolution towards XSL 2.0
**** main advantages (features) provided by a switch to 2.0
**** consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
**** how much of this should be known by the TEI community?

* Getting started (PB)
* Projects
** TEI - ISO
* Perspective workshop on TEI for the next decade
** communities
*** role of TEI in research infrastructures (AC)
**event
*** Dagstuhl
*** ESF [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd:
They used to be at
http://www.tei-c.org/Vault/GL/P1/ [source only]
http://www.tei-c.org/Vault/GL/P2/ [source only]
http://www.tei-c.org/Vault/GL/P3/index.htm [source in P3X/]

But I don't know where old stuff went when we moved to the new
website. In any case, there are copies of P3 at:
http://quod.lib.umich.edu/t/tei/
http://etext.virginia.edu/standards/tei/teip3/

== Council Telco - 21 August 2008 ==
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml
== Issues for next Telco - Oct 2008 ==
* update on SF bugs and features (Oxford)

* report to TEI MM

* naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ([http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html]) about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

* update on SIGs + responsabilities

* placement of Schematron rules in ODD
http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html

Note to be produced by SR

* update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and [[Getting Started]]

Looking for candidates:
** 6. Choosing and installing an editor
** 9. Getting this to work on sample of own text
** 11. Where to go from here

== Issues for next F2F ==

* Discussion on ODD and its evolution--[[User:Romary|Romary]] 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)

Namespaces

* Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

* should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

== Highlights to be brought to the TEI MM 2008 ==

== Topics (could be moved up to one F2F or Telco meeting ==

* Stable reference to TEI objects

(For original source of these comments, see tei-council thread [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|stable references]].)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in http://www.tei-c.org/ns/1.0), sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>: http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html
but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e.
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log
which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:
http://www.tei-c.org/Guidelines/access.xml

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we
might want to consider adopting one or another of the standard systems
for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to
register the DOIs with one of the national registries, but some more
extensive costs in human time to set up a good system for mapping from
our existing nomenclature to a set of DOI identifiers. (Publishers
typically use DOIs to identify individual books or journal articles, but
they can be more granular: every reference page in the Guidelines could
have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using
DOIs for citations could simply cite a DOI. So instead of the reference
for <name> in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

which would be resolved to the actual Web address by a DOI resolver.
(Many journal DOIs are mostly numeric but the syntax allows more
human-readable names).

If we seriously want to consider an option like this, we should put out
a call to the librarians/metadata gurus in our community for assistance
with implementation.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]