Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122)

@mgiuca commented on this pull request.



> @@ -859,13 +858,26 @@ <h3>
           application, it SHOULD treat that manifest as a description of a
           distinct application, even if it is served from the same URL as that
           of another application. When the user agent sees a manifest where
-          |manifest|["id"] is [=url/equal=] with [=URL serializer/exclude
-          fragment|exclude fragment true=] to the [=identity=] of an
-          already-installed application, it SHOULD be used as a signal that
+          |manifest|["id"] is [=url/equal=] (OPTIONAL: with

@marcoscaceres input needed: I rewrote it as "(with exclude fragments OPTIONALLY set to true)". Is this sufficient to capture RFC 2119's keyword "OPTIONAL"? (Note that Respec doesn't italicize the word "OPTIONALLY" nor does this adverbial form appear in RFC 2119)

Otherwise if it has to exactly use those words, I think the best phrasing is the somewhat verbose: "(the user agent MAY set exclude fragments to true)".

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1122#discussion_r1609451763
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1122/review/2070382406@github.com>