From 7649732c1a89a275442d7cd83fb8bf66c0770d51 Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 20 Oct 2019 10:26:56 +0200 Subject: [PATCH 1/5] rename note_type to note_atttribute to make it clear we add rule on an attribute --- specification.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/specification.markdown b/specification.markdown index 78938e76..9a9030cd 100644 --- a/specification.markdown +++ b/specification.markdown @@ -516,15 +516,15 @@ The purpose attribute is REQUIRED. ### \ Element -In some cases within an EBML Document Type, the attributes of the `` element are not sufficient to clearly communicate how the defined EBML Element is intended to be implemented. For instance, one EBML Element might only be mandatory if another EBML Element is present, or as another example, the default value of an EBML Element might derive from a related Element's content. In these cases where the Element's definition is conditional or advanced implementation notes are needed, one or many `` elements can be used to store that information. The `` refer to a specific attribute of the parent `` as expressed by the `note_type` attribute (#note-type). +In some cases within an EBML Document Type, the attributes of the `` element are not sufficient to clearly communicate how the defined EBML Element is intended to be implemented. For instance, one EBML Element might only be mandatory if another EBML Element is present, or as another example, the default value of an EBML Element might derive from a related Element's content. In these cases where the Element's definition is conditional or advanced implementation notes are needed, one or many `` elements can be used to store that information. The `` refer to a specific attribute of the parent `` as expressed by the `note_attribute` attribute (#note-type). ### \ Attributes -#### note_type +#### note_attribute -The note\_type attribute references which of the ``'s attributes that the implementation\_note is in regards to. The note_type attribute MUST be set to one of the following values (corresponding to that attribute of the parent ``): `minOccurs`, `maxOccurs`, `range`, `length`, `default`, `minver`, or `maxver`. The `` SHALL supersede the parent ``'s attribute that is named in the `note_type` attribute. An `` SHALL NOT have more than one `` of the same `note_type`. +The note\_attribute attribute references which of the ``'s attributes that the implementation\_note is in regards to. The note_attribute attribute MUST be set to one of the following values (corresponding to that attribute of the parent ``): `minOccurs`, `maxOccurs`, `range`, `length`, `default`, `minver`, or `maxver`. The `` SHALL supersede the parent ``'s attribute that is named in the `note_attribute` attribute. An `` SHALL NOT have more than one `` of the same `note_attribute`. -The note\_type attribute is REQUIRED. +The note\_attribute attribute is REQUIRED. ### \ Element From 405b8ab71278db34c8fe2cc51b8a0ea63c60d050 Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 20 Oct 2019 10:29:35 +0200 Subject: [PATCH 2/5] fix EBMLSchema.xsd after renaming --- EBMLSchema.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EBMLSchema.xsd b/EBMLSchema.xsd index 16956ec6..031e3715 100644 --- a/EBMLSchema.xsd +++ b/EBMLSchema.xsd @@ -96,7 +96,7 @@ - + From d5074be66d461fe2fa7ea4f6b88a616c7062a26d Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 20 Oct 2019 10:30:38 +0200 Subject: [PATCH 3/5] use new lines so that future changes are more readable --- specification.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/specification.markdown b/specification.markdown index 9a9030cd..c858b7f5 100644 --- a/specification.markdown +++ b/specification.markdown @@ -522,7 +522,10 @@ In some cases within an EBML Document Type, the attributes of the `` el #### note_attribute -The note\_attribute attribute references which of the ``'s attributes that the implementation\_note is in regards to. The note_attribute attribute MUST be set to one of the following values (corresponding to that attribute of the parent ``): `minOccurs`, `maxOccurs`, `range`, `length`, `default`, `minver`, or `maxver`. The `` SHALL supersede the parent ``'s attribute that is named in the `note_attribute` attribute. An `` SHALL NOT have more than one `` of the same `note_attribute`. +The note\_attribute attribute references which of the ``'s attributes that the implementation\_note is in regards to. +The note_attribute attribute MUST be set to one of the following values (corresponding to that attribute of the parent ``): `minOccurs`, `maxOccurs`, `range`, `length`, `default`, `minver`, or `maxver`. +The `` SHALL supersede the parent ``'s attribute that is named in the `note_attribute` attribute. +An `` SHALL NOT have more than one `` of the same `note_attribute`. The note\_attribute attribute is REQUIRED. From 290306583c66140ccf29c84e96518702492e979f Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 20 Oct 2019 10:31:32 +0200 Subject: [PATCH 4/5] more new lines --- specification.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/specification.markdown b/specification.markdown index c858b7f5..62ebf4ee 100644 --- a/specification.markdown +++ b/specification.markdown @@ -516,7 +516,10 @@ The purpose attribute is REQUIRED. ### \ Element -In some cases within an EBML Document Type, the attributes of the `` element are not sufficient to clearly communicate how the defined EBML Element is intended to be implemented. For instance, one EBML Element might only be mandatory if another EBML Element is present, or as another example, the default value of an EBML Element might derive from a related Element's content. In these cases where the Element's definition is conditional or advanced implementation notes are needed, one or many `` elements can be used to store that information. The `` refer to a specific attribute of the parent `` as expressed by the `note_attribute` attribute (#note-type). +In some cases within an EBML Document Type, the attributes of the `` element are not sufficient to clearly communicate how the defined EBML Element is intended to be implemented. +For instance, one EBML Element might only be mandatory if another EBML Element is present, or as another example, the default value of an EBML Element might derive from a related Element's content. +In these cases where the Element's definition is conditional or advanced implementation notes are needed, one or many `` elements can be used to store that information. +The `` refer to a specific attribute of the parent `` as expressed by the `note_attribute` attribute (#note-type). ### \ Attributes From fa5bee2f258f0ce1a014722b12df75f7557a7294 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Sun, 20 Oct 2019 13:02:21 -0400 Subject: [PATCH 5/5] fix intersectional link to note_attribute --- specification.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification.markdown b/specification.markdown index 62ebf4ee..ce2f5b98 100644 --- a/specification.markdown +++ b/specification.markdown @@ -519,7 +519,7 @@ The purpose attribute is REQUIRED. In some cases within an EBML Document Type, the attributes of the `` element are not sufficient to clearly communicate how the defined EBML Element is intended to be implemented. For instance, one EBML Element might only be mandatory if another EBML Element is present, or as another example, the default value of an EBML Element might derive from a related Element's content. In these cases where the Element's definition is conditional or advanced implementation notes are needed, one or many `` elements can be used to store that information. -The `` refer to a specific attribute of the parent `` as expressed by the `note_attribute` attribute (#note-type). +The `` refer to a specific attribute of the parent `` as expressed by the `note_attribute` attribute (#note-attribute). ### \ Attributes