- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 20 Apr 2016 21:17:10 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc:
Received on Thursday, 21 April 2016 04:17:40 UTC
> @marcoscaceres: if, hypothetically, the manifest spec had a registry associated for those extension values to be registered and discovered, would you be ok with that draft simply adding its own processing model for them (without changing any behavior for the core ones, which of course would need to be disallowed), registering them, and that would be how the webapp spec could be used as a foundation? I'm not sure I fully understand the question above, but I'm in favor or adding a registry. However, I want it to be super light weight. I've created https://github.com/w3c/manifest/wiki/Extensions-Registry I'm sending a PR now that points to the registry from the spec. --- 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/issues/452#issuecomment-212732420
Received on Thursday, 21 April 2016 04:17:40 UTC