search

ietf-wg-jsonpath / draft-ietf-jsonpath-base

Development of a JSONPath internet draft
https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/
Other
59 stars 20 forks source link

Processing model section not necessary #199

Closed gregsdennis closed 2 years ago

gregsdennis commented 2 years ago

In a previous issue, I suggested the idea of adding a processing model description to the specification. So Section 3.2 was added.

However, in re-reading the current document, I found that the process is repeated (albeit with less detail) in Section 3.4.

I think that the language in 3.4 may be sufficient to explain how the path is expected to operate, making the processing model (or at least one of them) somewhat redundant. Can we combine these sections in some way instead of repeating ourselves?

glyn commented 2 years ago

I agree that we could combine these sections and avoid some repetition. I'm inclined to keep the Semantics section and do away with the Processing Model section since I think the term "Processing Model" is a little obscure compared to "Semantics".