Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • PyI40AAS PyI40AAS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Lehrstuhl für Informations- und AutomatisierungssystemeLehrstuhl für Informations- und Automatisierungssysteme
  • PyI40AASPyI40AAS
  • Issues
  • #56
Closed
Open
Issue created Mar 13, 2020 by Sebastian Heppner@sebastian.heppnerOwner

XSD-Schema: group `qualifiable` definition inelegant and confusing

The current Schema uses the plural "s" for qualifiers in group qualifiable in a confusing way. For example a qualifiable property could look like this, when serialized according to the current schema:

<property>
[...]
<qualifier>
    <qualifiers>
        <qualifier/>
    </qualifiers>
    <qualifiers>
        <formula/>
    </qualifiers>
    [...]
</qualifier>
[...]
</property>

The wrapping <qualifiers> element around each inner <qualifier> or <formula> seems unneccesary. We suggest to remove it, to look like this:

<property>
    [...]
    <qualifiers>
        <qualifier/>
        <formula/>
        [...]
    </qualifiers>
    [...]
</property>

This can be achieved by changing the current version of the XSD-Schema from:

        <group name="qualifiable">
		<sequence>
			<element maxOccurs="1" minOccurs="0" name="qualifier" type="aas:constraints_t"/>
		</sequence>
	</group>
	<complexType name="constraints_t">
		<sequence>
			<element maxOccurs="unbounded" minOccurs="0" name="qualifiers" type="aas:constraint_t"/>
		</sequence>
	</complexType>
	<complexType name="constraint_t">
		<choice>
			<element maxOccurs="1" minOccurs="0" name="formula" type="aas:formula_t"/>
			<element maxOccurs="1" minOccurs="0" name="qualifier" type="aas:qualifier_t"/>
		</choice>
	</complexType>

to our suggested fix:

	<group name="qualifiable">
		<sequence>
			<element maxOccurs="1" minOccurs="0" name="qualifiers" type="aas:constraints_t"/>
		</sequence>
	</group>
	<complexType name="constraints_t">
		<sequence>
			<group maxOccurs="unbounded" minOccurs="0" ref="aas:constraintGroup"/>
		</sequence>
	</complexType>
	<group name="constraintGroup">
		<choice>
			<element maxOccurs="1" minOccurs="0" name="formula" type="aas:formula_t"/>
			<element maxOccurs="1" minOccurs="0" name="qualifier" type="aas:qualifier_t"/>
		</choice>
	</group>
Edited Mar 16, 2020 by Sebastian Heppner
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking