Re: [w3c/manifest] Editorial: include JSON Schema into spec (#928)

> So are you planning to expand on this and make it the actual normative basis for parsing the manifest? Or will it continue to be a non-normative note?

Non-normative. 

> I don't really see the point of having this, 

I wanted to have a quick alternative to the IDL index - as way for seeing the types. 

> when we already have a link out to it. It kind-of endorses it more, which might be a bad thing if it routinely gets out of date. 

I've updated the PULL_REQUEST_TEMPLATE to prevent that from happening. It shouldn't get out of date as it's our responsibility to keep it updated.  

> It means there's a piece of spec that isn't controlled by this GitHub repo, and can be dynamically changed by a third party (even though it's in non-normative text). I'm weakly opposed to including it but OK with allowing.

We have a good working relationship with the schema folks - so we can ask those folks to always check with us first before updating it.  

-- 
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/928#issuecomment-662276144