[occi-wg] Simple JSON rendering for OCCI

Alexander Papaspyrou alexander.papaspyrou at tu-dortmund.de
Fri May 15 06:15:44 CDT 2009


Sam,

Am 15.05.2009 um 13:02 schrieb Sam Johnston:

> On Fri, May 15, 2009 at 11:29 AM, Alexander Papaspyrou <alexander.papaspyrou at tu-dortmund.de 
> > wrote:
> JSDL has shown that extensions work fine even (sigh) with XML  
> namespaces, without breaking interop.
>
> Leaving extension points with xsd:any with namespace #other and lax  
> content allows for easy interop by just ignoring vendor-specific  
> stuff.
>
> However you slice it, namespaces are almost certainly going to be a  
> necessary evil for extensibility. Even for our own stuff namespaces  
> are useful for differentiating between resource types rather than  
> throwing everything in one bucket. I've already seen a  
> "vx_au.net.aos" namespace option proposed for JSON extensibility  
> based on a similar monstrosity I suggested earlier for XML - at the  
> end of the day all markup ends up looking like XML anyway.
>
> Also playing nice with other standards includes OGF standards of  
> course... is it safe to say these are mostly/soley done in XML?

yes. OGF is XML for data representation and WS* for service  
interfaces. While I agree that we should stay clean from the latter, I  
see no reason for rebuilding the features of the former just for the  
sake of avoiding to use it.

-Alexander
-- 
Alexander Papaspyrou
alexander.papaspyrou at tu-dortmund.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Alexander Papaspyrou.vcf
Type: text/directory
Size: 498 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/occi-wg/attachments/20090515/6dbde502/attachment.bin 
-------------- next part --------------




More information about the occi-wg mailing list