Closed ronaldtse closed 4 years ago
CC: @ogcscotts @gbuehler @ghobona
@andrew2net this has become necessary to implement since Metanorma-OGC needs to support 1 and 2.
- approved-technical-baseline => Not a document type, remove.
@ronaldtse but the json still contains "D-ATB" type. How should we handle it?
Let's mark it as "others"?
@ronaldtse I have no objection
- candidate-standard => (standard, in draft stage)
@ronaldtse which subtype should be in this case?
Just the default subtype please, since we don't know which each of one are.
Do you mean to use null
as default subtype fo standard
? Here there is a default subtype for best practice
only.
- implementation-standard-corrigendum => (standard: implementation, with corrigendum)
what does with corrigendum
mean?
Do you mean to use null as default subtype fo standard? Here there is a default subtype for best practice only.
Let's use "general".
what does
with corrigendum
mean?
Just ignore with corrigendum
for now.
- policy => (standard: policy)
is the "policy" subtype? There isn't "policy" in the subtypes list.
@andrew2net @opoudjis There is an issue we have with OGC synchronization.
Items 1 and 2 affect both Metanorma and Relaton.
Items 3 and 4 affect Relaton only.
This means that Relaton needs to support the NEW document types / subtypes and the NEW document stages, and also the translation of the OLD to NEW.
Metanorma only needs to support the NEW document types / subtypes and the NEW document stages.
NEW document type and subtypes + old document type to new document type mapping: https://github.com/metanorma/metanorma-ogc/issues/58
NEW document stages: https://github.com/metanorma/metanorma-ogc/issues/57