-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
Critical
-
Affects Version/s: cd03
-
Component/s: PR01 Comments
-
None
- Suggestion: Please consider adding the following addition to all
items that read: "This is an extensibility mechanism to allow
additional attributes, based on schemas, to be added to the abbrvX
element in the future. _*Requesting new elements for future
versions of the specification should be considered before
developing possible dependencies upon attributes which may be
deprecated in favor of such future elements.*_ Unrecognized
attributes MAY cause a fault or be silently ignored."
WTC: This comment has several aspects.
(1) The management of new attributes in the extensibility mechanism has a request for specific text
(2) The evolvability and management of the spec requires a mechanism ("requesting new elements..." needs management)
(3) The conformance statements must say something about conforming behavior if an attribute that is not understood is receive (the commenter's suggestion is in the description above)
(4) Note should be taken that an arbitrary "any" at the end of an object is a serious barrier to evolution; viz. W3C TAG notes over the past 5+ years.