- From: Erik Wilde <notifications@github.com>
- Date: Thu, 14 Apr 2016 05:06:44 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Thursday, 14 April 2016 12:07:23 UTC
The current draft has a very useful extension point that is supposed to catch properties that are not specified in the draft itself. One possible way to make this a bit more managed would be to establish a registry where new properties can be registered and then become well-known. This way other specs extending what can be represented in a webapp manifest could do that in a more managed way. https://tools.ietf.org/html/draft-wilde-registries talks about the general pattern of having a registry, and if there were such a registry, then the nect question would be how to establish one. There are several design options for this, but this issue is simply about the question of whether having a registry would be a useful thing to do. --- 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
Received on Thursday, 14 April 2016 12:07:23 UTC