I do not recall the reasons why we ended up with the current syntax, but
changing it would break compatibility with v1.
Personally I am not seeing a good reason to do that at this time.
----- Forwarded by Rich Thompson/Watson/IBM on 09/20/2007 11:01 AM -----
Nathan E Lipke <nli...@bea.com> To wsrp...@lists.oasis-open.org
09/12/2007 01:00 PM Subject [wsrp-comment] 10 User Information:
P3P Names do not match JSR286 or P3P
The naming convention used in section 10 do not match the names used in
either the P3P spec or JSR168/JSR286.
All of the other specs refer to P3P elements like:
However WSRP uses:
The differences are:
* Use '.' instead slash as a seperator
* Prefix or user.
* Use '-' instead of camel case for multi-word fields.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual or
entity named in this message. If you are not the intended recipient, and have
received this message in error, please immediately return this by email and
then delete it.