OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [provision] Scope of SPML -- Identities and Resources

If we are going to have interoperability, we need to both come up with the
interchange standards and also identify the standards for the information
about resources which is being exchanged.  I think a better metaphor than a
highway is a telephone call.  Using this metaphor, we need to standardize
how the call is made, but we need also to specify the language spoken at
each end if true information interchange is to occur.  So I think we need
to identify a relevant set of schemas for resources (which does not mean
that we do them ourselves!)  as well as a standard means for provisioning
services to exchange data -- both with other provisioning services and with
the resources themselves in some cases.

Karl Gottschalk
tie 441-9611
ext. 919-543-9611

                    Edward D.            To:     "'provision@lists.oasis-open.org'"                                
                    (OSED)"               <provision@lists.oasis-open.org>                                         
                    <OSED@chevront       cc:                                                                       
                    exaco.com>           Subject:     RE: [provision] Scope of SPML -- Identities and Resources    
                    12:37 PM                                                                                       

Darren, you hit the nail on the head!  The "value-add" here is not in
defining Yet Another Set of Schema (after all, we have the excellent work
various NAC, OSI, IETF, DMTF, other standards groups, and vendor committees
to take advantage of in this space - besides which, I think every end-user
organization has their own schema they have lovingly cultivated and won't
want to give up), but in defining a standard means for the various
components operating in the provisioning service space to exchange the data
needed to make the transaction work.  In this regard, we are like the
designers of a highway.  We aren't determining what the cars that use it
will look like, we want to make sure that the road will allow all to use it
in a manner that is safe and efficient.  By "overloading" the types of
things that may be provisioned, we force ourselves to take a step back
and get our heads out of the weeds.

Edward D. (Ed) Truitt
Systems Analyst
Global Infrastructure Delivery / Global IT Delivery
ChevronTexaco  Information Technology Company
Ph# +1 281.596-3246 Fax# +1 281.596-2714
Cell phone / Pager # +1 832.443-7283
"Got IT?"

-----Original Message-----
From: Darran Rolls [mailto:Darran.Rolls@waveset.com]
Sent: Thursday, December 06, 2001 10:00 PM
To: Truitt, Edward D. (OSED); provision@lists.oasis-open.org
Subject: RE: [provision] Scope of SPML -- Identities and Resources


This position puts SPML as the structure and framework for the
request/response flow not the prescription of the schemas that can flow
it. This enables the desirable things re RBAC that Edward mentions but does
not sign us up for a 4 year schema design course.

I'm at Disney World Orlando right now so telling me I'm on another planet
this would be somewhere near the truth ;-)

Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com
(512) 657 8360                    PGP  0x8AC67C6F

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC