Skip to content

Fix epochs schema to resolve double nesting of sdpi:Epoch element.#521

Open
PaulMartinsen wants to merge 3 commits intomasterfrom
520-example-13-does-not-comply-to-the-schema-because-of-sdpiepochs
Open

Fix epochs schema to resolve double nesting of sdpi:Epoch element.#521
PaulMartinsen wants to merge 3 commits intomasterfrom
520-example-13-does-not-comply-to-the-schema-because-of-sdpiepochs

Conversation

@PaulMartinsen
Copy link
Copy Markdown
Collaborator

📑 Description

Resolves TimeStampVersion.xsd schema bug in #520 to avoid nesting sdpi:Epoch found by Leon.

☑ Mandatory Tasks

The following aspects have been respected by the pull request assignee and at least one reviewer:

  • Changelog update (necessity checked and entry added or not added respectively)
  • Pull Request Assignee
  • Reviewer

type="sdpi:EpochVersion"
use="required">
<xsd:annotation>
<xsd:documentation>Current epoch version. Implied value is 0.</xsd:documentation>
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Just bumped into this. A required field cannot have an implied value. You would need to make the attribute optional and set a default="0".

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Thanks David. Updated now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Example 13 does not comply to the schema, because of sdpi:Epochs

3 participants