From b3d485c24b6c574551fa7884a0878b3f88d560e9 Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 6 Jun 2021 18:13:33 +0200 Subject: [PATCH] add a maxver attribute to enum values This could allow deprecating enum values. --- EBMLSchema.xsd | 1 + specification.markdown | 15 +++++++++++++++ 2 files changed, 16 insertions(+) diff --git a/EBMLSchema.xsd b/EBMLSchema.xsd index 9838920..6ade224 100644 --- a/EBMLSchema.xsd +++ b/EBMLSchema.xsd @@ -140,6 +140,7 @@ + diff --git a/specification.markdown b/specification.markdown index 9ee470d..7601515 100644 --- a/specification.markdown +++ b/specification.markdown @@ -1168,6 +1168,21 @@ The `minver` attribute is **OPTIONAL**. If the `minver` attribute is not present, then the enum value has the same value as the `minver` attribute of the EBML Element it belongs to. +#### maxver + +Within an EBML Schema, the XPath of the `@value` attribute is +`/EBMLSchema/element/restriction/enum/@maxver`. + +The `maxver` (maximum version) attribute stores a nonnegative integer that +represents the last or most recent version of the docType to support +the enum value. `maxver` **MUST** be greater than or equal to +the first version of the docType to support the enum value, whether it's set +in the `minver` attribute of the enum or implied. + +The `maxver` attribute is **OPTIONAL**. If the `maxver` attribute is +not present, then the enum value's maximum version is the value +stored in the `version` attribute of . + ### `` Element Within an EBML Schema, the XPath of the ``