TEIC/TEI

New issue

Exemplar schema for ENRICH includes duplicate ids for Schematron constraint Priority: Medium TEI: Schema Type: Bug
#1447 opened Apr 7, 2016 by martindholmes

0
Solve base-uri problem in Stylesheets before next release Priority: High Status: Go Tool: Oxgarage Tool: Roma Tool: Stylesheets Type: Bug
#1446 opened Apr 5, 2016 by jamescummings Guidelines 3.1.0

0
Old datatype reference pages? Priority: Medium TEI: Guidelines & Documentation Type: Bug
#1445 opened Apr 4, 2016 by jamescummings Guidelines 3.1.0

2
expand documentation of idno to include a table of values, their corresponding standard and documentation
#1442 opened Apr 4, 2016 by stuartyeates

3
the future of the Debian packages
#1441 opened Apr 1, 2016 by lddubeau

5
consider adding @xml:space as global attribute in Tite Status: Needs Discussion TEI: Schema: Tite Type: FeatureRequest
#1436 opened Feb 20, 2016 by kshawkin

2
Encoding the various possible readings of an unclear word Status: Needs Discussion TEI: Guidelines & Documentation TEI: Schema Type: FeatureRequest
#1434 opened Feb 11, 2016 by MarjorieBurghart

16
clarify how to encode short-form citations Status: Needs Discussion Type: FeatureRequest
#1431 opened Feb 3, 2016 by kshawkin

8
Refine elements that can contain <secFol>, <signatures>, <catchwords> Status: Needs Discussion Type: Bug
#1428 opened Jan 29, 2016 by adunning

1
Restructure chapter 11 Status: Needs Discussion TEI: Guidelines & Documentation Type: FeatureRequest
#1427 opened Jan 27, 2016 by brettttt

1
Allow <bibl> in <witDetail> Status: Go Type: FeatureRequest
#1425 opened Jan 22, 2016 by hcayless

3
Inconsistent handling of <idno>? Status: Needs Discussion Type: Bug
#1424 opened Jan 22, 2016 by StefanDumont

4
tei:f/@fVal constraints FUBAR Priority: Low Status: Needs Discussion TEI: Guidelines & Documentation TEI: Schema Type: Bug
#1422 opened Jan 12, 2016 by sydb

3
Examples for @calendar and @datingMethod Status: Needs Discussion Type: Bug
#1421 opened Jan 11, 2016 by schassan

13
<valItem> should allow <remarks>, too Status: Needs Discussion TEI: Guidelines & Documentation Type: FeatureRequest
#1420 opened Jan 7, 2016 by sydb

2
<lg> and <gap> Status: Needs Discussion Type: Bug
#1419 opened Jan 5, 2016 by hcayless

19
Make @select a bit more generalized Status: Needs Discussion TEI: Guidelines & Documentation TEI: Schema Type: FeatureRequest
#1418 opened Jan 5, 2016 by hcayless

3
Define useful constants for classSpecs, e.g. $MEMBERS Status: Needs Discussion TEI: ODD Tool: Stylesheets Type: FeatureRequest
#1417 opened Dec 28, 2015 by raffazizzi

1
`<taxonomy>` should allow both description elements and categories Priority: Medium Status: Needs Discussion TEI: Schema Type: FeatureRequest
#1415 opened Dec 20, 2015 by martindholmes

3
ogrophy elements should be in att.canonical Status: Needs Discussion TEI: Schema Type: FeatureRequest
#1414 opened Dec 15, 2015 by sydb

7
<title> should be in att.datable Status: Needs Discussion TEI: Schema Type: Bug
#1410 opened Dec 10, 2015 by sydb

2
Note on <egXML> incorrect Status: Needs Discussion TEI: Guidelines & Documentation Type: Bug
#1409 opened Dec 7, 2015 by sydb

2
abstract model constraint problems on model.pLike elements Status: Needs Discussion TEI: Schema Type: Bug
#1407 opened Dec 3, 2015 by sydb

0
Differentiate <ex> and <expan> more clearly Status: Needs Discussion TEI: Guidelines & Documentation Type: FeatureRequest
#1404 opened Nov 10, 2015 by adunning

12
Allow <expan> to be less than a complete word or phrase Status: Needs Discussion TEI: Guidelines & Documentation Type: FeatureRequest
#1403 opened Nov 10, 2015 by adunning

12

Previous 1 2 3 4 Next

ProTip! Type g p on any issue or pull request to go back to the pull request listing page.