| Re: @minOccurs, @maxOccurs and @use [message #1984 is a reply to message #1979] |
Thu, 04 October 2018 16:56  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 02.10.2018 um 13:18 schrieb Christian Rahmig:
> elements... are by default mandatory (minOccurs="1" and maxOccurs="1") [1]
>
> attributes... are by default optional (use="optional") [2]
>
> Therefore, mandatory elements and optional attributes don't have to have
> mentioned properties.
>
> For the following cases, properties have to be provided in the schema:
> * optional elements occuring once: minOccurs="0"
> * optional elements occuring up to n times: minOccurs="0" and
> maxOccurs="n" (with n being a positive number)
> * mandatory elements occurinng up to n times: maxOccurs="n" (with n
> being a positive number)
> * mandatory attributes: use="required"
A ticket [1] has been created with the aim to identify and delete all
occurances of
* minOccurs="1"
* maxOccurs="1"
* use="optional"
The ticket has been implemented with railML version 2.4.
[1] https://trac.railml.org/ticket/344
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
