#392 confusing semantics of @ns

AMBER
closed-fixed
5
2012-10-21
2012-04-08
No

Sebastian reported on tei-council on 2012-01-04 that he has implemented @ns to indicate that an element or attribute *is currently* in the following namespace. However, the examples in section 23.2.1 involving @ns (where mode="add" or mode="change") use this attribute to mean that an element or attribute *shall be* in the following namespace. It would be good if we could be internally consistent.

Discussion

  • James Cummings

    James Cummings - 2012-06-29
    • assigned_to: nobody --> rahtz
     
  • Lou Burnard

    Lou Burnard - 2012-09-16
    • milestone: --> AMBER
     
  • Kevin Hawkins

    Kevin Hawkins - 2012-09-21

    A Council subgroup realized that @ns only specifies desired namespace of output (what it *shall be*). Sebastian was wrong in his posting on tei-council.

    However, @ns should be declared once in a single attribute class rather than separately on three different elements.

    Furthermore, we will remove misleading @ns examples in Guidelines.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2012-10-21
    • status: open --> closed-fixed
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2012-10-21

    new attrubute class added to define @ns on the affected elements. Sebastian accepts the punishment of his peers for his unwise posting.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks