Re: [w3c/manifest] chore: refactor and export scope terms (#882)

@marcoscaceres commented on this pull request.



> @@ -437,11 +437,11 @@ <h2>
         Navigation scope
       </h2>
       <p data-link-for="WebAppManifest">
-        A <dfn data-export="">navigation scope</dfn> is a <a>URL</a> that
-        represents the set of URLs to which an <a>application context</a> can
-        be navigated while the manifest is <a>applied</a>. The <a>navigation
-        scope</a> of a manifest <var>manifest</var> is
-        <var>manifest</var>["<a>scope</a>"].
+        The {{WebAppManifest/scope}} member of a [=processed manifest=] is the

> applied to it.

I wanted to avoid "it", as "it" is ambiguous. Will try to rephrase... 

> We should be able to cut out steps 3 and 4. I think this can be achieved by navigation scope continuing to be a property of a manifest, not an application context.

Yes, that could work... although an application context is formed by the applied processed manifest.  

> We could also define "navigation scope of an application context" and "within scope of an application context", but I think that's overkill.

Agree. 

-- 
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/manifest/pull/882#discussion_r437872541