[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-672) Use a JSON Schema
[ http://tools.oasis-open.org/issues/browse/CMIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23725#action_23725 ]
Gregory Melahn commented on CMIS-672:
-------------------------------------
A positive reply back from Lloyd on inclusion of Orderly in our Appendix.
Notice that he wants comments/questions on his mailing list orderly@librelist.com , which is fine.
Sorry for the delay, I've been a bit under the weather. Responses inline.
On Nov 30, 2010, at 9:34 AM, Gregory Melahn wrote:
>
> First, just to clarify, I don't propose to use any of the code though of course any of the vendors that implement or use the spec may be interested. But that is not really a spec issue.
>
> As far as the design, what I would like us to do is just copy the description of Orderly into our specification, so for example we would have an Appendix A including the text from http://orderly-json.org/docs copied into it. Then, elsewhere in the specification we would use Orderly as a way of describing the details of the binding and we would even include an Orderly file downloadable from the OASIS site containing our schema. I am still having a conversation with the OASIS general counsel about this concept and maybe he will find some flaw in this idea but so far he thinks it is doable assuming you are in agreement of course. And of course we would want to include in our specification the right attribution of Orderly The reason for including the text in the spec itself and not just referring to http://orderly-json.org/docs is to make the specification self contained and not dependent on another document that is itself not (yet) a standard. Would you find such a way of using Orderly acceptable? Or do you have another idea?
copying the description of orderly into the spec sounds fine.
> Also, in the course of creating our schema we would want to bounce questions off you, or ideas for extending Orderly. For example, one of the committee members thought it would be useful to have a construct of map, and had a proposed syntax for that. Would you be agreeable to members of the subcommittee contacting you with such questions or ideas? We want to respect your time and how you would like such a conversation to work (using a mailing list for example?).
orderly@librelist.com is the orderly mailing list, any ideas for extending orderly could be discussed there.
> Finally, I would like to ask you to review our proposed schema from time to time and give us ideas for improvement.
Time permitting, I'd be willing to do this.
> To give you an idea on our timeline, the browser binding extension to CMIS is part of the CMIS 1.1 work and the expectation is that we would turn the proposal over to the editors by roughly March 2011 and then it goes into the OASIS spec editing and review cycle which will take most of 2011. So we would want our work on the description of Orderly and the schema complete by March 2011.
ok.
> So how does all this sound?
In general, all of this sounds fine. There has been a lot of flux in the JSONSchema proposal upon which orderly is built, and at some point in the future I hope to re-engage the JSONSchema spec and give orderly a thorough update. It will be interesting to see if orderly as is is sufficiently expressive for your application.
very best,
lloyd
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]