Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Bitmaps element of v2.1 in visinfo.xsd #380

Open
wants to merge 1 commit into
base: release_2_1
Choose a base branch
from

Conversation

thbeu
Copy link

@thbeu thbeu commented Jun 21, 2024

The Bitmaps element in v2.1 is wrong and needs to be fixed.

Unfortunately there is not a single v2.1 test case that has this optional element set.

@thbeu thbeu changed the title Fix Bitmaps element in visinfo.xsd Fix Bitmaps element of v2.1 in visinfo.xsd Jun 21, 2024
@@ -25,7 +25,7 @@
</xs:complexType>
</xs:element>
<!-- ISG Jira issue BCF-17: Add support for text in the viewpoints -->
<xs:element name="Bitmap" minOccurs="0" maxOccurs="unbounded">
<xs:element name="Bitmaps" minOccurs="0" maxOccurs="unbounded">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would rename the individual elements each to Bitmaps, but they'd still all appear in a sequence in the parent object. I think it would be better to create a wrapper element Bitmaps which holds one or many Bitmap elements, like this:

<Visinfo>
  <Bitmaps>
	  <Bitmap>
		<Reference>123</Reference>
	  </Bitmap>
	  <Bitmap>
		<Reference>456</Reference>
	  </Bitmap>
	  <Bitmap>
		<Reference>789</Reference>
	  </Bitmap>
  </Bitmaps>
</Visinfo>

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yes. This was my intention, but done wrong.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GeorgDangl Please check again. It looks similar to Lines/Line or ClippingPlanes/ClippingPlane to me (with some exceptions on minOccurs/maxOccurs).

@thbeu thbeu marked this pull request as draft July 15, 2024 09:29
@thbeu thbeu marked this pull request as ready for review July 16, 2024 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants