You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In section "#PH-changes" (11.7 “11.7 Identifying Changes and Revisions”)
a. There is a case of disagreement in number (“A nested <gi>listChange</gi> elements is also useful”), and
b. The example immediately following (which includes the ID "ST1") shows an @ordered on the outer <listChange> (which is not a problem) and none on the inner <listChange>. Since the default is "true", this is a problem, as the point of the example is to show that the inner list contains unordered changes even though the outer one is ordered.
P.S. Error (b) is evidence in favor of @martindholmes’s “no default attribute values at all ever” position; and against, or at least not in favor, if my “a default attribute value is just a suggestion” position.
The text was updated successfully, but these errors were encountered:
In section "#PH-changes" (11.7 “11.7 Identifying Changes and Revisions”)
a. There is a case of disagreement in number (“A nested
<gi>
listChange</gi>
elements is also useful”), andb. The example immediately following (which includes the ID "ST1") shows an
@ordered
on the outer<listChange>
(which is not a problem) and none on the inner<listChange>
. Since the default is "true", this is a problem, as the point of the example is to show that the inner list contains unordered changes even though the outer one is ordered.P.S. Error (b) is evidence in favor of @martindholmes’s “no default attribute values at all ever” position; and against, or at least not in favor, if my “a default attribute value is just a suggestion” position.
The text was updated successfully, but these errors were encountered: