[occi-wg] JSON Rendering

[Gary Mazz]

Hi,

I've been looking at the details of the JSON and noticed the use of 
"rel", "kind",  "related", "actions" and "scheme".

These tags are all using XSD schemes as values. XSD has no meaning to JSON.

I think this is a defect. I'm proposing three  (3) options:

Option 1)  adopt JSON schema
Option 2) adopt JSON-LD (linked data) that will permit us to move into 
the semantic web.
Option 3) adopt JSON schema & adopt JSON-LD (linked data).

With Option 1, JSON schema is in flux right now, and they are just 
thinking about proposing draft 4. There may be some risk with the scheme 
changing out from underneath us. But, it does buy us a validation 
strategy that we need. There are a few JSON schema validators (two ?) 
out there already.

With Option 2, the scheme value becomes a JSON object with 2 properties: 
@id and @context. @id becomes the name and @context is a semantic 
definition on a server or in a  knowledge base. We do not get validation 
with this option.

Option 3 combines Option 1 and Option 2. There are really two concerns 
proposed to address a problem. A more robust solution would be 
incorporate both options

cheers,
gary

On 5/2/2012 9:25 PM, Michael Behrens wrote:
> In reviewing the latest sent out...here a few nit-noids...which Gary 
> may have already corrected....
>
> -    In section 5.1, I see two JSON examples....looks like a second 
> one starts on line 113.  Perhaps a description of the second one would 
> help separate the two. Or am I reading it wrong?
> -    in that JSON, there are some extra spaces showing up after "http: 
> ".  Lines 88, 90, 91, 97
> -    Line 106, missing comma at end of line (I think)
> -    Looks like the JSON in section 5.2 is split up - perhaps the 
> tables should follow the JSON - presumably.
>
> I like the usage of the pattern attribute...that will help with client 
> side validation :)
>
> - Michael B.
>