Proprietary extensions of the manifest

[xfq]

The Web App Manifest allows adding new proprietary manifest members using vendor prefixes: https://www.w3.org/TR/appmanifest/#proprietary-extensions

We probably need something similar.

[zhangyongjing]

Good point.
According to the current way that the JSON Schema is defined, MiniApp manifest is by default is non-exclusive. That means implementors can add their proprietary extensions as they want. (unless a particular implementation intends to put constraints on the manifest by defining a more strict schema, e.g. 'additionalProperties'=false.)

The question is more about whether we would like to maintain a vendor extension list. If so, some guildlines (like the naming convension) could be defined in the spec.

I'd like to hear more comments on that.

[zhangyongjing]

As now MiniApp manifest itself is an extension to WebApp Manifest, allowing for vendor extension is a logical deduction. We could add a few more sentences in the spec to address it.

[espinr]

Should we create a registry for the extensions? There is one at the WebApp Manifest level, but we can maintain the specific list of the MiniApp extensions to centralize the information in the group's repository. Of course we would sync to the WebApp Manifest Extensions Registry and include some pointers there.

[espinr]

Based on my proposal, I've created a new wiki page to host these extensions: https://github.com/w3c/miniapp-manifest/wiki/MiniApp-Manifest-Extensions-Registry

[espinr]

Closing after meeting discussion.