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 original document lists the following normative references:
In all places except from the following, they are cross-referenced as listed in the Normative references.
These exceptions are by Metanorma's default encoded as in Normative references. Is there a specific reason why these should be manually encoded differently?
The text was updated successfully, but these errors were encountered:
@anermina you mean in these two cross-references, the document identifiers appear in a different form (with year or without year) than when cited.
There is actually a reason for that:
In Terms and definitions, the SOURCE should be a dated reference in order to provide a clause number.
In the content, if a standard is referenced as a requirement, it can be undated. For example, the requirement perhaps could be satisfied using any edition of that standard.
Encoding:
I think for the first, technically citing “undated” already includes all dated references, and because ISO does not like citing undated + dated, so using an undated in Norm refs then citing dated in SOURCE is acceptable. This is a feature change.
for the second, I think the Norm refs should have cited the undated reference instead.
The original document lists the following normative references:

In all places except from the following, they are cross-referenced as listed in the Normative references.


These exceptions are by Metanorma's default encoded as in Normative references. Is there a specific reason why these should be manually encoded differently?
The text was updated successfully, but these errors were encountered: