[Openicc] 0.9.0 release of IccXML

[Chris Murphy]

My understanding is that JSON is not as extensible as XML, and therefore while JSON might be appropriate for metadata (very simple), it might not be able to handle mluts?

If JSON is adequate for fully describing both primary ICC profile data, as well as metadata, and yet it is simpler than XML, then I'm in favor of simpler. The ICC profile format is not a document, while XML is a document oriented language. But ICC profiles contain data (and metadata), which seems to be exactly what JSON is directed at addressing, including being self-described data. But again, it might be too simple for the guts of ICC profiles: the LUTs.

In any event, the binary ICC profile format means that it's not at all well equipped to handle metadata because it requires a parser that's constantly being updated to account for new optional metadata tags. It's way too specialized and is in a sense almost user hostile. So I'm totally supportive of making the profile format human readable.

BTW, WCS profiles are also XML based.


Chris Murphy

On Sep 2, 2010, at 1:02 AM, Guy K. Kloss wrote:

> On Thu, 02 Sep 2010 17:18:20 Kai-Uwe Behrmann wrote:
>> Well and you know, the industry goes XML ;-)
> 
> I thought XML was on the way out and JSON on the way in? After all, RESTful 
> web services with JSON are displacing the XML heavy SOAP (XML) ones.
> 
> Guy
> 
> -- 
> Guy K. Kloss
> Institute of Information and Mathematical Sciences
> Te Kura Pūtaiao o Mōhiohio me Pāngarau
> Massey University, Albany (North Shore City, Auckland)
> 473 State Highway 17, Gate 1, Mailroom, Quad B Building
> voice: +64 9 414-0800 ext. 9266   fax: +64 9 441-8181
> G.Kloss at massey.ac.nz http://www.massey.ac.nz/~gkloss
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc