ABNF has a spec: https://www.rfc-editor.org/rfc/rfc5234.txt
Yes, let's use ABNF for describing low-level machine-parsable grammars.
However, that's really low-level implementation specification. There's a higher level that brings more value: the Ubiquitous Language.[1]
The Ubiquitous Language helps us discover the high-level Resources[2] within our Domain. When we're thinking about Resources, we're too high-level to use ABNF...which is a good thing.
tl;dr - What high-level Resource(s) do we need to eliminate confusion in our Ubiquitous Language? (Hint: right now, we're conflating at least two.)
JSA
[1] http://martinfowler.com/bliki/UbiquitousLanguage.html
[2] https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm, Section 5.2.1.1
|
|
martinfowler.com
Ubiquitous Language is the term Eric Evans uses in Domain Driven Design for the practice of building up a common, rigorous language between developers and users.
|
|
(Thread trimmed.) 