RE: [ciq] xACML customer information not CIQ

Colin,

Yes, XACML knows about CIQ work and we did speak to them. But as usual, nothing

happened. Ths is where we have problems in the OASIS model. There is no mandate

within OASIS that TCs should leverage each others work. Though OASIS asks TCs to

do so, there is no monitoring on this.

Ram

Dear CIQ

I missed this one on its way through but looking through the schema fragments of xACML I see plenty of customer information elements being used.

I don't know if we talked to these guys or not, (its hard to cover every base in OASIS!) but I can see a definite potential need for alignment, especially given they have a SAML profile.

Another job for CAM, David!

Cheers

Colin
.............................................
OASIS members:

I am pleased to announce that the voting on XACML 2.0 from the OASIS
eXtensible Access Control Markup Language (XACML) TC has resulted in this
Committee Draft being approved as an OASIS Standard. The submission of the
approved standard can be found at
http://lists.oasis-open.org/archives/tc-announce/200412/msg00008.html.

The TC members and chairs, Hal Lockhart and Bill Parducci, are to be
congratulated on their work in developing and approving this specification.

Thanks to those OASIS members who reviewed the specifications and cast
ballots. The ballot and results of voting may be viewed by members at
http://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=674&

Mary

Mary P McRae
OASIS
Manager of TC Administration
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org

ciq message