In the ATS, the subject field refers in many places to the "/conf/..." reference, e.g.:
|
[[ats_dismiss]] |
|
[conformance_class] |
|
.Dismiss |
|
==== |
|
[%metadata] |
|
identifier:: https://www.opengis.net/spec/ogcapi-processes-1/2.0/conf/dismiss |
|
subject:: <<rc_core,https://www.opengis.net/spec/ogcapi-processes-1/2.0/conf/dismiss>> |
If I understand the references properly, shouldn't they instead refer to the "/req/...", such that they match the identifier of the corresponding Requirement Class ?
|
[[rc_dismiss]] |
|
[requirements_class] |
|
.Requirements Class 'Dismiss' |
|
==== |
|
[%metadata] |
|
identifier:: https://www.opengis.net/spec/ogcapi-processes-1/2.0/req/dismiss |
There also seems to be an issue with this subject field, since they are all rendered "empty" in https://docs.ogc.org/DRAFTS/18-062r3.html (even when the subject is just a plain text, not a ref, like Web API).
In the ATS, the
subjectfield refers in many places to the"/conf/..."reference, e.g.:ogcapi-processes/core/abstract_tests/ATS_class_dismiss.adoc
Lines 1 to 7 in 8e96af4
If I understand the references properly, shouldn't they instead refer to the
"/req/...", such that they match theidentifierof the corresponding Requirement Class ?ogcapi-processes/core/requirements/requirements_class_dismiss.adoc
Lines 1 to 6 in 8e96af4
There also seems to be an issue with this
subjectfield, since they are all rendered "empty" in https://docs.ogc.org/DRAFTS/18-062r3.html (even when the subject is just a plain text, not a ref, likeWeb API).