- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 10 Dec 2018 01:30:13 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 10 December 2018 09:30:35 UTC
I think it would be better if we started with the high-level goals for this syntax and then see what kind of schema language would be the most appropriate fit. * Parsing always uses https://infra.spec.whatwg.org/#parse-json-from-bytes. (Otherwise the processor returns failure.) * A https://mimesniff.spec.whatwg.org/#json-mime-type is required. (Otherwise the processor returns failure.) * There needs to be a way to declare types for fields. (It probably makes sense for these types to match IDL types.) * A type-mismatch is equal to the field being set to undefined. Things I'm unclear on: * Is the top-level value always an object? * Do we need to be able to require fields? * Only top-level or also nested fields? * Is such a field is undefined, does it mean the processor returns failure? Are there other requirements here? -- 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/611#issuecomment-445748219
Received on Monday, 10 December 2018 09:30:35 UTC