Title: RE: New Name ! (A new suggestion)
How
about dropping the Access part, and call it XCES (perhaps a bit xcessive though
:-).
One
problem with the name is that it's not as much about credential exchange as
results of credential exchanges.
Dave
-----Original Message-----
From: Jeremy Epstein
[mailto:]
Sent: Friday, January 26, 2001 9:06
AM
To: Carlisle Adams; 'Eve L. Maler'; OASIS SSTC
List
Subject: RE: New Name ! (A new suggestion)
Great suggestion! Perhaps almost as
importantly, a quick search didn't find any significant products that already
use this acronym. (There are several companies, etc., but nothing that
should cause confusion.) Perhaps most telling, feeding the words Active
XML Credentials Exchange Specification into Google hit several pages related
to this effort near the top of the list... so it must be at least related to
what we're doing at a buzzword level :-)
--Jeremy
-----Original Message-----
From: Carlisle Adams
[mailto:]
Sent: Friday, January 26, 2001
11:53 AM
To: ; 'Eve L.
Maler'
Subject: RE: New Name ! (A new
suggestion)
Hi,
I believe that the
group has (rough) consensus that "S2ML" should be changed as the overall
name of this OASIS TC spec because "Security Services" is too broad.
I, for one, would not want to be in the shoes of the PR spokesperson
(currently Eve!) trying to explain to some analyst or press representative
why XKMS -- which is clear a security service -- is not within the scope of
this TC.
Perhaps not
surprisingly, I have no objections to "A2ML", but I can understand the
hesitation on the part of some who either feel that "Authentication" implies
too much, or that "Authentication and Authorization" may be too narrow in
scope.
Therefore, I will offer
another name for consideration (if only so that we have some competition for
SEX-ML!). It seems to me that what this group would like to do is
create a specification for the exchange of credentials. These
credentials (today covering both authentication credentials and
authorization credentials, but open in the future to other kinds of
credentials that we may choose to embrace) will be expressed in XML.
Furthermore, I think it is fair to say that the payload to be exchanged will
always include at least one "active" -- that is, currently valid --
credential (name assertion, entitlement assertion, whatever).
Thus, my suggestion
is: "Active XML Credentials Exchange Specification", which has the
intuitive and somewhat appropriate acronym "AXCES" (pronounced
"access").
Carlisle.
