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] normative elements,identifiers,algorithms and whether mandatory

Attached is a list of all schema elements (16f.xsd), identifiers,
and algorithms.  Within each list, items are in alphabetical
order.  Each item is labelled "M" or " ", meaning "Mandatory to
implement" or "normative, but not mandatory to implement",
respectively.  The list of identifiers includes Michiharu's

1. Should the following elements in the policy schema be mandatory?
   ?  xacml          AbstractDefaults  (abstract)
   ?  xacml          PolicyDefaults
   ?  xacml          PolicySetDefaults

2. Should we include xs: datatypes that we require to be
   supported, or do we assume all of them are mandatory?

3. Does flagging an attribute identifier as
   mandatory-to-implement mean that the corresponding attribute
   is mandatory-to-implement?  (I assume yes)

Please let me know if these are correct.  Tim, if you would like
to have these labelled by the section number in version 15 of the
spec, let me know.

Anne H. Anderson             Email: Anne.Anderson@Sun.COM
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311     Tel: 781/442-0928
Burlington, MA 01803-0902 USA  Fax: 781/442-1692

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

Powered by eList eXpress LLC