Would be useful to give all requirements unique numbers

[jonblower]

... that can be explicitly referenced in test code and validator error messages

[letmaik]

I think we can do something like that but in a subtle way so that it doesn't disturb much, similar to law texts. So, each requirement gets a local number, meaning instead of bullet points we use numbers. Then you can refer to a requirement as "Requirement 4.1(4)".

[letmaik]

Do you still think this is a good idea? Doesn't seem common in W3C recs for example.

[jonblower]

If it's not common practice in W3C then I don't mind too much. It's a bit easier to refer to individual requirements (and therefore test them). Also, it's possible that the OGC will need this ultimately.

I wonder if Phil Archer could give guidance on this, also the OGC reps on the SDWWG? If we do have to do this, it might be easier to do it now than later. One possible downside is that it might affect readability - but perhaps the cookbook is more useful as a training tool than the spec.

[letmaik]

Closing this as it will be handled in the OGC repo one way or another as part of editing.