identifiers for Requirements per OGC ModSpec

[rob-metalinkage]

Sections such as 5.5.2.2 have a list of requirements with a local informal list numbering - these are virtually impossible to cite reliably when implementing solutions.

It would be preferable to follow the OGC ModSpec which requires URIs for requirements classes and individual requirements throughout the document.

This could possibly be done as a final editorial step against a final draft. Or introduced in a PR in order to facilitate change tracking later.

If requirements are based on section number they may be hard to maintain.

[dr-shorthair]

Can we merge the expectations or styles of OGC vs W3C standards/recommendations? Are the term definitions the 'requirements'? Are the module definitions the 'requirements classes'? 

There are two sets of identifiers for the individual terms 

1. the IRI for each term from the ontology itself
   e.g. http://www.w3.org/ns/sosa/hasUltimateFeatureOfInterest
2. the link to the definition in the recommendation document
   e.g. https://w3c.github.io/sdw-sosa-ssn/ssn/#dfn-sosa-hasultimatefeatureofinterest 

(Note that the #dfn-* IRIs are auto-generated for each term which were added in https://github.com/w3c/sdw-sosa-ssn/pull/340 .)

For the modules,

1. IRIs for the files in the RDF distribution are listed here: https://w3c.github.io/sdw-sosa-ssn/ssn/#distribution 
   e.g. http://www.w3.org/ns/sosa/act/ 
2. The sections in the recommendation document have IRIs like https://w3c.github.io/sdw-sosa-ssn/ssn/#Actuation

Can these be re-purposed as OGC ModSpec element identifiers?

(Noting that w3c.github.io/sdw-sosa-ssn/ssn/ will be replaced by www.w3.org/TR/vocab-ssn-2023/ in the published edition)

[dr-shorthair]

Modules are effectively a profiling model for standards.

Perhaps 'conformance tests' and 'conformance class' matches better to SHACL?

[dr-shorthair]

Ping @rob-metalinkage
We will need a pragmatic solution here.
There are URIs available for pretty much everything.
Perhaps an additional annex to classify these into requirements and requirements-classes?

As mentioned, I'm not sure we can do tests until we get to SHACL.