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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: [xacml] FW: [XACML Schema] 8-4-2002 minutes


Title: FW: [XACML Schema] 8-4-2002 minutes

Hi,

Looks like Ernesto is still having trouble posting to the list...

Here are the minutes from today's concall.

Carlisle.


----------
From:   ernesto damiani[SMTP:edamiani@crema.unimi.it]
Sent:   Monday, April 08, 2002 12:29 PM
To:     Carlisle Adams
Subject:        Fw: [XACML Schema] 8-4-2002 minutes

 
----- Original Message -----
From: ernesto damiani
To: xacml@lists.oasis-open.org
Sent: Monday, April 08, 2002 6:06 PM
Subject: [XACML Schema] 8-4-2002 minutes

People:
 
Anne
Carlisle
Tim
Ernesto
Michiharu
Simon

Minutes:

Prior to the concall, Ernesto had posted to the list a proposal for partitioning the current schema among task forces working in parallel. Tim later posted an amendment to that proposal, specifying five areas: 

 
Policy/rule
Obligations
Predicate expressions
Predicate
Functions

The above list of areas is accepted; Tim volunteers to provide a partition of the current schema elements according to those areas. It is agreed that possible extensions to SAML will be outlined when discussing each area. 

Simon proposes to call the areas "subjects" and to use them as topics for free discussion rather than as names for task-forces.

The proposal is accepted; Ernesto volunteers to assign the subjects to the next three concalls' agendas in order to keep the end of the month deadline.

Discussion on the mailing list about subjects other than those under discussion in the next concall is however encouraged.

 
It is also decided to leave some time on each concall for discussion of "strategic topics", i.e. general XML schema design issues that are of interest for XACML

 
For the current concall, a brief discussion identifies the following topics:
 
1 use of substitution groups vs type derivation in extensibility points
 
2 need for set-oriented operators
 
3 definition of an abstract type for each concrete type
 
4 definition of unique element names for schema each position, avoiding tag reuse.
 

Topic 1: While type derivation is favored, it is decided not to adopt a strict guideline of using substitution groups or type derivation as extensibility support. Current substitution groups in the schema are considered well justified.

 
Topic 2: Union and intersection operators will be added in the operators' substitution group
 
Topic 3 and 4: Simon volunteers to carry out an analysis of the current schema to pinpoint places where abstract type definitions could be made. Also, he will look into unique element names.

 
 



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


Powered by eList eXpress LLC