- From: Alex Russell <notifications@github.com>
- Date: Tue, 26 Jun 2018 11:39:17 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 June 2018 18:39:42 UTC
Hey all, We discussed again today, and given the new example of the structure that @mnot posted, it seems like JSON is indeed the only available, largely appropriate choice at the moment. Other designs require pre-guessing how to de-structure common, deep data with flat names or a new convention (not part of the SH design) to enable re-construction based on some sort of naming convention. The alternatives (Base64-encoding nested structured) seem just as bad. Would love to see the issues filed get addressed, but don't see much need to hold this train for the use of JSON modulo previously raised points. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/195#issuecomment-400420078
Received on Tuesday, 26 June 2018 18:39:42 UTC