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
The <remarks> element has its own @ident defined as teidata.text with the description “specifies the remark concerned.”.
At first blush, almost everything about that seems wrong. (After thinking about it, only the definition and description seem wrong.)
Why does <remarks> get an @ident at all? It is not processed by the Stylesheets. (The answer is that we hope to change the Stylesheets so that they are properly processed, someday.)
Given that it has an @ident, why not get it from being a member of att.identified? (The answer is, I would guess, that we did not want @predeclare, @module, or @validUntil, and thought it better to add it directly than to add it to att.identified and then delete those attributes.)
Why is it defined as teidata.text rather than teidata.name? (I think this is just a corrigible error that should be fixed ASAR.)
The description is wrong. At the least it should be “identifies the remark concerned”; but to be more like att.identified probably “supplies the identifier by which these remarks may be referenced.”
The text was updated successfully, but these errors were encountered:
The
<remarks>
element has its own@ident
defined as teidata.text with the description “specifies the remark concerned.”.At first blush, almost everything about that seems wrong. (After thinking about it, only the definition and description seem wrong.)
<remarks>
get an@ident
at all? It is not processed by the Stylesheets. (The answer is that we hope to change the Stylesheets so that they are properly processed, someday.)@ident
, why not get it from being a member of att.identified? (The answer is, I would guess, that we did not want@predeclare
,@module
, or@validUntil
, and thought it better to add it directly than to add it to att.identified and then delete those attributes.)The text was updated successfully, but these errors were encountered: