NiXPS
Thursday, December 24, 2009
Sunday, December 13, 2009
EXI
I've been tied up with a lot of work the last couple of weeks, resulting in too much blog radio silence for my liking.
We have released a v2.6.5, which I will blog about more the coming days.
And we're working heavily on our next major SDK release v3, which will feature some impressive technological advancements.
All new v2.6 SDK customers will receive the v3 for free. All existing v2.6 SDK customers will receive the v3 for free if they are under maintenance.
One thing caught my attention this week: 'Efficient XML Interchange' gets W3C green light. Efficient XML Interchange. First time I heard about that one. This appears to be a binary representation of an XML document, the spec is being drafted by the W3C. I've browsed it lightly, and it seems to be a binary representation that reduces the overhead for XML, and facilitates SAX parsing.
I find it a bit of an odd thing. XML is verbose, but this verbosity helps humans reading, writing and understanding it. And a computer can always zip it. Turning it into a binary format, kind of defeats the purpose, and makes it just another binary format.
I definitely need to study it further. Sharing the parser state, could be an interesting thing to have, but that would only matter for big XML files, I guess. And what if you do not want to be forced in a SAX style arrangement?
But it exists, so I assume it must be scratching an itch! ¶ 13:36 0 Comments
We have released a v2.6.5, which I will blog about more the coming days.
And we're working heavily on our next major SDK release v3, which will feature some impressive technological advancements.
All new v2.6 SDK customers will receive the v3 for free. All existing v2.6 SDK customers will receive the v3 for free if they are under maintenance.
One thing caught my attention this week: 'Efficient XML Interchange' gets W3C green light. Efficient XML Interchange. First time I heard about that one. This appears to be a binary representation of an XML document, the spec is being drafted by the W3C. I've browsed it lightly, and it seems to be a binary representation that reduces the overhead for XML, and facilitates SAX parsing.
I find it a bit of an odd thing. XML is verbose, but this verbosity helps humans reading, writing and understanding it. And a computer can always zip it. Turning it into a binary format, kind of defeats the purpose, and makes it just another binary format.
I definitely need to study it further. Sharing the parser state, could be an interesting thing to have, but that would only matter for big XML files, I guess. And what if you do not want to be forced in a SAX style arrangement?
But it exists, so I assume it must be scratching an itch! ¶ 13:36 0 Comments
