OASIS eXtensible Access Control Markup Language (XACML) TC

 View Only
  • 1.  Where to put todos for next TC revision cycle?

    Posted 05-18-2012 19:30
    Where is the best place to put suggestions for work items for the TC to consider in the next revision of the XACML spec?  It doesn’t need to be addressed in the current 3.0 release but I don’t want to lose track of it.   The item is:  We need to provide more definition around the use of the Policy/Set version string.  The current spec defines what a version string looks like, but not how it is to be tested in equality and less than / greater than comparisons.  I would guess that all current implementations are probably doing the same “common sense” handling of version strings, but the semantics of version comparisons are not actually defined in the spec.     Per side discussion with Remon, another topic for future discussion is whether semantic versioning can be defined in the spec.   -Danny   Danny Thorpe Product Architect Quest Software - Now including the people and products of BiTKOO www.quest.com  


  • 2.  RE: [xacml] Where to put todos for next TC revision cycle?

    Posted 05-29-2012 20:12
    The place to put stuff like this is in the active issues section of the wiki.   There is some definition of this in section 5.13. Perhaps it can be imporved.   Hal   From: Danny Thorpe [mailto:Danny.Thorpe@quest.com] Sent: Friday, May 18, 2012 3:30 PM To: xacml@lists.oasis-open.org Subject: [xacml] Where to put todos for next TC revision cycle?   Where is the best place to put suggestions for work items for the TC to consider in the next revision of the XACML spec?  It doesn’t need to be addressed in the current 3.0 release but I don’t want to lose track of it.   The item is:  We need to provide more definition around the use of the Policy/Set version string.  The current spec defines what a version string looks like, but not how it is to be tested in equality and less than / greater than comparisons.  I would guess that all current implementations are probably doing the same “common sense” handling of version strings, but the semantics of version comparisons are not actually defined in the spec.     Per side discussion with Remon, another topic for future discussion is whether semantic versioning can be defined in the spec.   -Danny   Danny Thorpe Product Architect Quest Software - Now including the people and products of BiTKOO www.quest.com