|Subject:||RE: [xacml] REST Profile - General Plan|
|Date:||May 16, 2012 2:25:13 pm|
-----Original Message----- From: xac...@lists.oasis-open.org [mailto:xac...@lists.oasis-open.org] On Behalf Of Hal Lockhart Sent: Wednesday, May 16, 2012 10:15 PM To: xac...@lists.oasis-open.org Subject: [xacml] REST Profile - General Plan
I have a number of different kinds of comments about the REST Profile and Media types which will post separately to allow the discussion to take place in distinct threads.
I am not clear on what the general plan for this work is.
My proposal was the following: http://lists.oasis-open.org/archives/xacml/201205/msg00006.html
First, Robin Cover noted that the IANA submission must refer to a document that is either an IETF RFC or an OASIS Standard (in our case). I assume that we are not doing an RFC, so we must bring the Media Types doc to Oasis Standard before doing the IANA submission. Agreed?
Actually, I'm leaning more towards an RFC: http://lists.oasis-open.org/archives/xacml/201205/msg00006.html
Second, I assume the Media types document should refer to a document which has at least some level of approval. Does everyone agree on this? Is CD sufficient? CS?
Per Robin's statement above it should be OS, right?
Next question is, do we plan to put the JSON material and everything else related in the REST Profile doc, or have a separate doc for some of it?
Current consensus seems to be a separate document. David Brossard proposed his
'JSON over HTTP' profile: http://lists.oasis-open.org/archives/xacml/201205/msg00012.html But we may have to rename it?
Assuming a single doc, are we planning to complete it and then move it to CS and OS or attempt to standardize a preliminary doc which is missing some of the material?
I vote we complete it and then move it forward.
Assuming we will complete it and then move it forward, is there any necessary ordering between reaching any particular stage of the REST and media Profiles?
The JSON profile is independent of anything else, as is the registration of the
The REST profile needs a representation (and would ideally reference the JSON
and XML formats), but the meat of the profile can move forward without knowledge
of the details of any such representation. So we may need to wait until the XML
and JSON stuff is "done" to finalize the REST profile, but we can surely work on
it in the mean time.
Is there anything else we need to agree on with respect for the work plan?
Don't think so.