Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#402 revise valList and valItem, revise ch. 22 accordingly

GREEN
closed-accepted
Lou Burnard
5
2012-09-23
2012-04-26
Piotr Banski
No

Currently,
* valList "contains one or more valItem elements defining possible values for an attribute"
* valItem "documents a single attribute-value within a list of possible or mandatory items."

This is misleading, because valList may be used for elementSpec just as well.

Additionally, both specs send the reader to section 22.4.5, "Attribute List Specification", only. They are not discussed elsewhere in ch. 22.

Moreover, the example in valItem is not very intuitive (and the one in valList shows an attribute definition, which is fine, but another one would be good to have, for elements).

Discussion

  • James Cummings
    James Cummings
    2012-06-29

    • assigned_to: nobody --> stuartyeates
     
  • Lou Burnard
    Lou Burnard
    2012-09-16

    • milestone: --> GREEN
     
  • Lou Burnard
    Lou Burnard
    2012-09-16

    The use of valList to define element content is not well documented, possibly because it's not supported by schema langs other than RelaxNG. Some wording should be proposed however, if we leave things as they are in the schema.

     
  • James Cummings
    James Cummings
    2012-09-19

    • assigned_to: stuartyeates --> louburnard
     
  • James Cummings
    James Cummings
    2012-09-22

    • status: open --> open-accepted
     
  • James Cummings
    James Cummings
    2012-09-22

    Council decided (Oxford, 2012-09), that LB should propose some wording to explain this.

     
  • Lou Burnard
    Lou Burnard
    2012-09-23

    At svn release 10864, added discussion of use of valList for content models; removed limitation to attributes in doc

     
  • Lou Burnard
    Lou Burnard
    2012-09-23

    • status: open-accepted --> closed-accepted