Speaking of "_path syntax_" - which would require separate definition, I believe.
Why can't we use JSON Pointer ([RFC 6901](https://tools.ietf.org/search/rfc6901)) it already covers all the rules for escaping, characters allowed by JS, etc.
The downside of that would be the syntax for expressions that would look alien {{foo(/a/b, /c/d/e)}}, but expressions and dot-syntax could be delegated to libraries and frameworks.
But we would not have to bother about specing it and re-inventing the wheel.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/682#issuecomment-342992192