Closed manuelfuenmayor closed 1 week ago
Fixes https://github.com/metanorma/ogc-modspec/issues/2
There are several differences between previous content and model-based content:
Previous content includes source blocks, but in model-based these are re-encoded in tables: Previous content: Model-based content:
There are cases where source content from previous encoding is not equal to model-based content
Likewise, there are cases where definition content from previous encoding is not same as model-based: Previous encoding:
=== Requirement Each normative statement which is tested by any conformance test is a requirement.
Model-based content:
class Requirement { definition { Normative statement that constitutes a requirement. }
Also, there are a few cases where quotation rules are not fulfilled in model-based: Example:
If class "a" is dependent on class "b", then to pass the test for...
I think the "b", should be "b,". (As previous encoding.)
"b",
"b,"
In StandardizationTargetType class, there is no content in model-based. Which results in an empty sub-section.
StandardizationTargetType
Fixes https://github.com/metanorma/ogc-modspec/issues/2
There are several differences between previous content and model-based content:
Previous content includes source blocks, but in model-based these are re-encoded in tables: Previous content:
Model-based content:
![issue1-2](https://user-images.githubusercontent.com/33627611/183231801-4a3d826f-99b6-422a-b214-714361249ad2.PNG)
There are cases where source content from previous encoding is not equal to model-based content
Likewise, there are cases where definition content from previous encoding is not same as model-based: Previous encoding:
Model-based content:
Also, there are a few cases where quotation rules are not fulfilled in model-based: Example:
I think the
"b",
should be"b,"
. (As previous encoding.)In
StandardizationTargetType
class, there is no content in model-based. Which results in an empty sub-section.