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] | [List Home]


Subject: Proposed Agenda 4/21/2003 PSTC Committee Con-call


CONFERENCE ID
=============
Dial-in Number: 888-742-8686
Conference ID: 5250215
Date: 4/21/2003
Time 10 AM CST

Proposed Agenda
===============
1 - 10:05 Order and role-call
-----------------------------
Roll-call

2 - 10:07 Accept meeting minutes from 7/14/2003  
-----------------------------------------------
Minutes available at [1]
 
3 - 10:15 New Type for RequestID
--------------------------------
There is a proposal in the SAML group to make some of their ID 
elements of type xsd:ID instead of string. The advantage is that those 
IDs can now be used directly in XPath and XML Signatures without 
having to add a parallel ID via the Open Content Model (which we now 
support in SPML).
 
The only restriction that this imposes is that the request ID conform 
to the xsd:ID restrictions. That means that the ID must start with an 
alpha, and the could contain alphanumeric and certain punctuations 
(".", "-", and "_").

JeffB wishes to put forward a motion to change the type of 
the Request ID element from xsd:string to xsd:ID.

4 - URN ID Forms
----------------
The id schema currently in place for both operationID and schemaID
allows for a two point ID with providerID, all of which can be URN's.
When a URN based identifier is used for both elements one can go from a
provider and schema ID to a urn, but not vice-versa. This makes the
referencing of objectClassDefinitions, attributeReferncces and extended
requests complex.  A solution is to either limit the schemaID and
operationID's to simple strings, or always refer to both the providerID
schemaID/operationID explicitly in any reference.

To simplify this we could:

1) Require that the provider ID is always in the form of a URN.
2) Require that the schema ID is always in the form of a simple ID
3) Require that the operation ID is always a simple ID

4 - 10:30 Spec Update
---------------------
Friday's draft; comments back by Thursday please.  Discuss dates &
timelines as discussed in [3].
 
5 - 10:40 Interop
-----------------
- Discuss proposed dates for the glue party
- Discuss possible location
- Updates on participants
- Next steps
                 
6 - 10:45 Other business
------------------------
As required.

7 - 11:00 Motion to Adjourn
---------------------
To reconvene 4/28/2003.

[1]
http://www.oasis-open.org/apps/org/workgroup/provision/download.php/1600
/pstc-minutes-04142003.html
[2]
http://www.oasis-open.org/apps/org/workgroup/provision/ballot.php?id=51&;
[3] http://www.oasis-open.org/archives/provision/200304/msg00028.html

=========================================================
Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
512) 657 8360                     
=========================================================




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