From cc7fe93f4451ab54899a91637731f8e6029b357a Mon Sep 17 00:00:00 2001 From: Steve Moyer Date: Mon, 5 Aug 2024 18:53:01 -0400 Subject: [PATCH] fix(policy): add line terminator so ABNF compiles (#14) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e470c0f..52ebca2 100644 --- a/README.md +++ b/README.md @@ -146,7 +146,7 @@ connective = "[" DQUOTE "not" DQUOTE "," statement "]" ; Ne / "[" DQUOTE "and" DQUOTE ",[" statement *("," statement) "]]" ; Conjuction / "[" DQUOTE "or" DQUOTE ",[" statement *("," statement) "]]" ; Disjunction -quanitifier = "[" DQUOTE "every" DQUOTE "," selector "," policy "]" ; Universal +quantifier = "[" DQUOTE "every" DQUOTE "," selector "," policy "]" ; Universal / "[" DQUOTE "some" DQUOTE "," selector "," policy "]" ; Existential ;; COMPARISONS @@ -429,7 +429,7 @@ null [jq] is a much larger language than UCAN's selectors. jq includes features like pipes, arithmatic, regexes, assignment, recursive descent, and so on which MUST NOT be supported in the UCAN Policy language. -jq produces streams of values, in contract to UCAN argument selectors which return an IPLD value. This introduces the primary difference between jq and UCAN argument selectors is how to treat output of the try (`?`) operator: UCAN's `try` selector operator MUST return `null` for the failure case. +jq produces streams of values, in contrast to UCAN argument selectors which return an IPLD value. This introduces the primary difference between jq and UCAN argument selectors is how to treat output of the try (`?`) operator: UCAN's `try` selector operator MUST return `null` for the failure case. ## Validation