Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://libranet.de/objects/0b6b25a8-1665-5ee8-67ca-b84299344309">clacke (clacke@libranet.de)'s status on Thursday, 23-Nov-2023 15:07:19 JST</a><a href="https://libranet.de/profile/clacke" title="clacke@libranet.de"><img src="https://gnusocial.jp/theme/gnusocialjp/default-avatar-stream.png" width="48" height="48" alt="clacke" style="position: absolute; left: 0; top: 0;">clacke</a><div><a href="https://libranet.de/display/0b6b25a8-6961-1547-38ba-8f9325215960" rel="in-reply-to">in reply to</a></div></section><article><p>I returned briefly to this topic ( <a href="https://libranet.de/display/0b6b25a8-2765-5ee4-e0bb-92a402093890" rel="noreferrer">libranet.de/display/0b6b25a8-2…</a> ) and started thinking of what attempts exist to use a subset of some existing Infoset (XML) binary encoding for the JSON datamodel subset of the Infoset datamodel.</p><p>I already mentioned Fast Infoset here at the top, but the W3C Recommendation for "binary XML" is EXI, Efficient XML Interchange, which I have not yet mentioned in this thread, and:</p>&gt; EXI4JSON is a specification developed by the same working group to use the same format for JSON documents.[7]<p><br><a href="https://en.wikipedia.org/wiki/Efficient_XML_Interchange#Uses" rel="noreferrer">en.wikipedia.org/wiki/Efficien…</a></p><p>[7] <a href="https://www.w3.org/TR/exi-for-json/" rel="noreferrer">w3.org/TR/exi-for-json/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2367051#notice-4673354">In conversation</a><time datetime="2023-11-23T15:07:19+09:00" title="Thursday, 23-Nov-2023 15:07:19 JST">Thursday, 23-Nov-2023 15:07:19 JST</time> <span>from <span><a href="https://libranet.de/display/0b6b25a8-1665-5ee8-67ca-b84299344309" rel="external" title="Sent from libranet.de via ActivityPub">libranet.de</a></span></span><a href="https://libranet.de/display/0b6b25a8-1665-5ee8-67ca-b84299344309">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/628068">Untitled attachment</a></label><br></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1870676">Untitled attachment</a></label><br></li><li><article><header><div>Domain not in remote thumbnail source whitelist: www.w3.org</div><h5><a href="https://www.w3.org/TR/exi-for-json/">W3C standards and drafts</a></h5><div></div></header><div>The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
clacke (clacke@libranet.de)'s status on Thursday, 23-Nov-2023 15:07:19 JST clacke
in reply to
I returned briefly to this topic ( libranet.de/display/0b6b25a8-2… ) and started thinking of what attempts exist to use a subset of some existing Infoset (XML) binary encoding for the JSON datamodel subset of the Infoset datamodel.
I already mentioned Fast Infoset here at the top, but the W3C Recommendation for "binary XML" is EXI, Efficient XML Interchange, which I have not yet mentioned in this thread, and:
> EXI4JSON is a specification developed by the same working group to use the same format for JSON documents.[7]

en.wikipedia.org/wiki/Efficien…
[7] w3.org/TR/exi-for-json/
In conversationThursday, 23-Nov-2023 15:07:19 JST from libranet.depermalink
Attachments
1. Untitled attachment
2. Untitled attachment
3. Domain not in remote thumbnail source whitelist: www.w3.org
  W3C standards and drafts
  The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.

Public

Embed Notice

HTML Code

Corresponding Notice