Closed ronaldtse closed 5 years ago
The two are completely different issues. Fetching the 2nd draft remains an issue here. The prefixing of "nist" is a separate issue: https://github.com/metanorma/metanorma-nist/issues/124
(though it too will need to be propagated into relaton-nist)
@andrew2net also, the "type" is wrong -- this is a "white-paper" not a "standard". See the Relaton XML cache attached.
nist_framework_for_improving_critical_infrastructure_cybersecurity_version_1.1.xml.zip
Ronald, you're behind.
bibitem@type
is now "standard" for all of Relaton. That is because document types are idiosyncratic to each flavour, so we cannot get a single grammar to specify all the possible enums.
The document type for a specific standard subclass is bibdata/ext/doctype
.
If the document type is going to be referenced in a citation, it must NOT be modelled as document type. It must be modelled as a series.
Note that #124 has also fixed this so that "White Paper" is populated in ext/doctype, which was the other issue raised here.
@opoudjis just to confirm, is @andrew2net going to take care of this?
@ronaldtse I'm going but have a lot of tasks. Feel free to prioritize tasks in my todo and in progress lists.
@andrew2net already done :wink:
Yes, I wasn't offering to take this one on.
Priority remains relaton. There's some instability still in the gems, I'm seeing that in metanorma-gb rpsec, <gbtype>
etc are still being returned in rspec from relaton: in bib_retval
the obsolete elements are not being rendered to XML, but in fetch_ref
they are.
Using the following reference item:
Originally posted by @ronaldtse in https://github.com/metanorma/relaton-nist/issues/17#issuecomment-496233868