- From: Peintner, Daniel (ext) <daniel.peintner.ext@siemens.com>
- Date: Wed, 16 Mar 2016 15:13:58 +0000
- To: Takuki Kamiya <tkamiya@us.fujitsu.com>, "public-exi@w3.org" <public-exi@w3.org>
Hi Taki, The https changes were introduced right before publication and I thought I fixed them. Thanks for finding a remaining issue. I think the targetNamespace was ok but the XML schema namespace still contained https. I fixed this issue in the latest editor draft. Please let me know whether that resolves your issue. Thanks, -- Daniel ________________________________ Von: Takuki Kamiya [tkamiya@us.fujitsu.com] Gesendet: Mittwoch, 16. März 2016 03:37 An: public-exi@w3.org Betreff: Target namespace for EXI for JSON Hi, Target namespace used in the spec [1] starts with "https:" while the schema file [2] linked from the spec still seems to use "http". This mismatch causes the generated EXI for JSON stream to use built-in grammar. [1] https://www.w3.org/XML/EXI/docs/json/exi-for-json.html#schema-for-json<&smime=14.3.123.2https://www.w3.org/XML/EXI/docs/json/exi-for-json.html#schema-for-json> [2] https://www.w3.org/XML/EXI/docs/json/schema-for-json.xsd<&smime=14.3.123.2https://www.w3.org/XML/EXI/docs/json/schema-for-json.xsd> Thank you, Takuki Kamiya Fujitsu Laboratories of America
Received on Wednesday, 16 March 2016 15:14:29 UTC