Colleagues - Haruyuki suggests the following renaming ...
regexp-rfc822Name-match -> rfc822Name-regexp-match
regexp-x500Name-match -> x500Name-regexp-match
For consistency with other function name structures.
All the best. Tim.
-----Original Message-----
From: Haruyuki Kawabe [mailto:]
Sent: Wednesday, November 10, 2004 7:25 PM
To: Tim Moses
Subject: Re: [xacml-comment] Public Comment
Dear Tim,
I omitted the CC for ''
<>
since I'm not a member of the mailing list and sending mails to the list
will be failed. You may forward my mail to the mailing list.
Tim Moses wrote:
>Haruyuki - Your observation is correct. Thank you. In addition,
>
>regexp-rfc822Name-match and
>regexp-x500Name-match
>
>Were introduced in Version 2.
>
>In the interests of consistent naming, perhaps we should change the
>name
>
>regexp-uri-match to
>regexp-anyURI-match
>
>Any objections? All the best. Tim.
>
>
Most of functions have a name like <datatype>-<functionality>, so It seems
to me that rfc822Name-regexp-match and x500Name-regexp-match are suitable
than the current naming..
Haruyuki Kawabe
>-----Original Message-----
>From: [mailto:]
>Sent: Tuesday, November 09, 2004 9:54 PM
>To:
>Subject: [xacml-comment] Public Comment
>
>
>Comment from:
>
>Following datatypes and functions are introduced since XACML 2.0:
> - dnsName
> - ipAddress
> - regexp-dnsName-match
> - regexp-ipAddress-match
> - regexp-uri-match
>They are defined in the namespace
>"urn:oasis:names:tc:xacml:1.0:data-type"
>and "urn:oasis:names:tc:xacml:1.0:function" respectively. They should be
>defined in the XACML 2.0 namecpase "urn:oasis:names:tc:xacml:2.0" as same
as
>string-concatenate and uri-string-concatenate.
>
>
