[w3c/manifest] `id` member reuse in MiniApps Manifest (no `document URL`) (Issue #1048)

[Bringing the discussion from w3c/miniapp-manifest#43]

We want to align the MiniApp identifier (`app_id`) with the [web app manifest's](https://www.w3.org/TR/appmanifest/#dfn-manifest) `id`. It would make sense to reuse it directly. It fits in terms of semantics ("a [string](https://infra.spec.whatwg.org/#string) that represents the identity for the application.") 

But there is a big difference, the (web app manifest's) [`id`](https://www.w3.org/TR/appmanifest/#dfn-identity) takes the form of a URL, which is the same origin as the start URL. MiniApps are packaged and can be distributed by different means, not only through the web (so not necessarily must have a start URL). In some cases the `app_id` follows the [Java package naming](https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html) (e.g., `org.example.app`). 

Since we are using the manifest [extension mechanism](https://www.w3.org/TR/appmanifest/#extensibility), is it possible to reuse the member but refine the [processing algorithm](https://www.w3.org/TR/appmanifest/#dfn-process-the-id-member)?  

Also, reviewing the main [algorithm](https://www.w3.org/TR/appmanifest/#dfn-processing-a-manifest), I see another relevant challenge, the `document URL` must not be null. Any idea how to relax or bypass this dependence?

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

Message ID: <w3c/manifest/issues/1048@github.com>