Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #475
Closed
Open
Issue created Jul 02, 2021 by CO Coordination@coordination.COMaintainer

Check all schemes for unnecessary @minOccurs, @maxOccurs and @usage

Description

Clone of railML 2.4 ticket #344 (closed)

In railML schemes there are elements that occur exactly one time. Thus, @minOccurs="1" and @maxOccurs="1". Since these are default values, they don't have to be given explicitly. The same applies for @use="optional" for attributes.

Background

See #344 (closed)

Links

  • Trac tickets:
  • #344 (closed)

Proposed solution

Before finalising railML 2.5, remove in all schema files:

  • minOccurs="1"
  • maxOccurs="1"
  • use="optional"
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany