Feature/operations handling, Business Rules

[mprorock]

Corrects some formatting on HTML.
Reorders sections for better readability.
Adds section around business rules handling for identifiers and common operations performed using external systems with data receiving or analyzing data presented using this spec

[mprorock]

Full understanding that there is a fair amount of re-ordering, etc with this PR, and that it will take time to review. Given how out of order several sections were, e.g. vocab pointers buried below other sections in the spec, i would request that the spec is read top to bottom to ensure correct ordering of sections, per specification norms, etc.

new additions to the spec are confined to the section starting at line 358 "Rules for Processing Data"

[OR13]

this is the primary challenge for us to define... assuming a stream of presentations where credentials may be "replayed" or "replaced" or "updated"... what is the current state of the instance, and which credentials are most authoritative for satisfying the requirements of the definition.

[mprorock]

suggest we build on this, after it is merged

[OR13]

Overall looks good, let me know when its out of draft, and I will review again.

[nissimsan]

Nice, Mike! Thank you.

[TallTed]

For future, separating radical re-ordering from pretty much any other change(s) makes reviewing much easier. This melange is gonna take a while to digest/understand, even if I review commit-by-commit...

[mkhraisha]

can you run npm run format:docs? it'll make reviewing much easier, as I assume it won't override the current lint.

[OR13]

Only blocking feedback is related to "conversion to github issues" or "creating an issue"

[TallTed]

174 comments. 45 commits. and counting. Most if not all without specific issues behind them.

This PR has gone past my ability to usefully review, largely because GitHub doesn't know how to highlight text changes of this variety or magnitude, and, so far as I can tell, there's no PR Preview.

I can't think of how to best proceed at this point. Maybe someone else has a good idea.

[mprorock]

Only blocking feedback is related to "conversion to github issues" or "creating an issue"

I believe we now have issues open on everything

[OR13]

A few additional issues need to be linked in respec, see:

https://respec.org/docs/#data-number

[OR13]

@mprorock sorry, I should have been more clear, opening issues is good, but for "new things" they also need to be linked in the spec, I have left comments on those, and left the rest of your resolutions resolved.

[mprorock]

@mprorock sorry, I should have been more clear, opening issues is good, but for "new things" they also need to be linked in the spec, I have left comments on those, and left the rest of your resolutions resolved.

last issue that did not have a data-number has been added in 3ae7a99

[OR13]

I am merging this, its massive, and we need to start addressing follow up items.