xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Putting the final touches to the JSON representation
HI all, As it stands, I think the XACML/JSON representation may well be complete.
I have a couple of questions outstanding.
1. Ray, what did you have in mind for the IANA registration section?
You asked me to add this as a section but I don't know what you have in mind exactly.
2. With respect to section 7, transport, I currently have a short statement: The XACML request represented in its JSON format MAY be carried from a PEP to a PDP via an HTTP POST request.
It does not define mandatory headers that an HTTP request would contain such as the media-type.
Should we leave that up to the REST profile and reference it?
3. With respect to acknowledgements, who should I put down there?
The main contributors have been Ray and Danny.
But everyone did chip in at some point.
Hal, is there a list of users / names we typically use?
Cheers, David.
--
David Brossard, M.Eng, SCEA, CSTP Product Manager +46(0)760 25 85 75 Axiomatics AB Skeppsbron 40 S-111 30 Stockholm, Sweden http://www.linkedin.com/companies/536082 http://www.axiomatics.com http://twitter.com/axiomatics
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]