[OASIS Issue Tracker] Commented: (CMIS-672) Use a JSON Schema

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23156#action_23156 ] 

Florian Mueller commented on CMIS-672:
--------------------------------------

A few more things:

- A map instead of an array for the properties would be nice. Access by property id makes it much more usable. We talked about that in the last call.

- I think we need inheritance support in the schema. The current approach blows up the JSON messages for no good reason and makes it difficult to use.

- We have to decide how we want to transport properties. Is it a simple map "property id -> value"? Then we need an easy way to incorporate type information as described in spec draft (includeTypeInformation parameter). Or should the property map point to a struct that contains more than just the value. The schema draft is closer to the latter. Both have advantages and disadvantages. 


> Use a JSON Schema 
> ------------------
>
>                 Key: CMIS-672
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-672
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Browser Binding
>    Affects Versions: Browser Binding Proposal
>         Environment: All
>            Reporter: Gregory Melahn
>            Assignee: Gregory Melahn
>             Fix For: Browser Binding Proposal
>
>
> Use a JSON  schema to define the Browser Binding.   
> Candidates include ...
> 1.  Orderly: http://orderly-json.org/
> 2.  JSON Schema http://json-schema.org/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira