Dear Veronique, you are right on both counts. There are two minor modifications to be done. 1) Section 5.3 needs to change as follows: ------------------------------------------ 1a) From: 5.3 An introduction to general elements To: 5.3 An introduction to generic elements 1b) From: All elements in this schema fall under one of five content models: hierarchical container, container, block, inline and marker. To: All elements in this schema fall under one of six content models: hierarchical container, container, subFlow, block, inline and marker. 1c) From: container - The container element is a generic element for a container. It includes elements belonging to the block pattern. To: container - The container element is a generic element for a container. It includes elements belonging to the block pattern. subFlow - The subFlow element is a generic element for a subFlow. It includes elements belonging to the hcontainer, container and/or block pattern. 2) The schema needs to change as follows: ----------------------------------------- 2a) Attribute name is added to generic element subFlow I will post later tonight a new release of the schema named CSD14. Ciao Fabio -- On 03/giu/2015, at 15:33, "PARISSE, Véronique" <
V.PARISSE@aubay.lu> wrote: > 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 > > -- Fabio Vitali The sage and the fool Dept. of Informatics go to their graves Univ. of Bologna ITALY alike in this respect: phone: +39 051 2094872 both believe the sage to be a fool. e-mail:
fabio@cs.unibo.it Where, then, may wisdom be found?
http://vitali.web.cs.unibo.it/ Qi, "Neither Yes nor No", The codeless code