Closed ronaldtse closed 4 years ago
The date of superseding can be found in the bibliographic date:
Isn't the date of stage's changes?
Obsoleted documents like ISO 8601:2004 (https://www.iso.org/standard/40874.html) have a section:
There isn't the section anymore.
They just moved it to the top:
They just moved it to the top:
Anyway, it's the same information as in the REVISIONS / CORRIGENDA
section. We already use it.
@andrew2net that's great then, do we now parse all of the dates to stages properly?
@ronaldtse we don't have a date in the status element
status =
element status {
( stage, substage?, iteration? )
}
stage = element stage { text }
substage = element substage { txt }
iteration = element iteration { text }
I think each document stage will use a separate bibitem. For example, if we have ISO 9001, we can find out the date of ISO/DIS 9001 from the same page.
Ok, as soon as the changes will be implemented in grammar I'll use it to store stage date, but now it will be lost when we save a document in an XML file.
Wait, I just saw this randomly in my periodic review of notifications, and I think you're talking at cross purposes.
@andrew2net, you're assuming that there will be an optional date stored in the status for each distinct status assigned to a document.
@ronaldtse and I have assumed that, if you are tracking dates or other metadata for each status: the bibitems are related as instances/versions of the same underlying document. Since there will be one status per bibitem, the date of the status assignment will be the /date[@type = 'circulated']
for that bibitem: the date of that bibitem is after all going to be the date specific to that status. So there is no need to embed the date within the status.
Each document contains relationships:
ISO 8601-1:2019 (https://www.iso.org/standard/70907.html)
The date of superseding can be found in the bibliographic date:
Obsoleted documents like ISO 8601:2004 (https://www.iso.org/standard/40874.html) have a section:
And this information for the date and relations: