[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Comments on public reviews for Akoma Ntoso Version 1.0
Dear all, Based on my very latest works with Akoma Ntoso, I would like to give you the following comment/suggestion to
improve the Akoma Ntoso specifications. Thanks in advance to take this into consideration.
Comment in the Akoma Ntoso Version 1.0 Part 1: XML Vocabulary
The 4.1.5.1, Categories in content model states that, "The Akoma Ntoso schema uses
six categories of content models. This means that all content models and complex types used in the schema follow precisely the form of the relevant category, and all elements can be simply described and treated according to their category rather
than individually."
The 6 categories are markers, inlines, blocks, subFlows, containers and hContainers.
The 5.3, An introduction to general elements,
on the other hand, states that "All elements in this schema fall under one of
five content models: hierarchical container, container, block, inline and marker. Besides named elements, the schema also provides for a generic element for each of them that can be used for markup and that fits the content models but can be specified
by a precise name that is not used in this schema. The 'name' attribute must be used for naming the element. The attribute name is required and gives a name to the element."
Can we align 5.3 to 4.1.5.1 and change the text into "All elements in this schema fall under one of
six content models: hierarchical container, container,subFlow, block, inline and marker. Besides named elements, the schema also provides for a generic element for each of them that can be used for markup and that fits the content
models but can be specified by a precise name that is not used in this schema. The 'name' attribute must be used for naming the element. The attribute name is required and gives a name to the element."
Comment on the schema
In the current schema, the subFlow element is a generic element without the "name" attribute.
Can we add the "name" attribute to the subFlow element ?
Thanks in advance Kind regards Véronique Parisse |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]