Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trying to make the current situation of zib-TimeInterval visible.
The profiles either reference extension
ext-TimeInterval.Period
or (if the resource allows a Period) Period datatype profilezib-TimeInterval
.ext-TimeInterval.Period
is an extension with a valuePeriod which haszib-TimeInterval
placed on it.zib-TimeInterval
contains extensionext-TimeInterval.Duration
.Previously (in the version that is currently at the Validatieraad), the 'Duration' and 'Period' extensions were added next to each other (or only the Duration extension was added when a Period element was already present) within the various profiles instead of nested. This situation would allow more 'control' over the cardinality of 'Duration` separate from Period.
Previously 2 (in the version that is currently at the Validatieraad),
ext-TimeInterval.Duration
had the comment:This has been removed, we could re-add the text using 'SHOULD'. Maybe even specifically add that it should only be used in v3 IVL_TS conversions?
(There is an nl-core-TimeInterval profile, but it isn't referenced from other nl-core-profiles. This is a situation should be fixed anyway, so I left it out of this comparison.)