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

Subject: RE: [xacml] Multiple Decison Request Proposal

> >> I think the <Request> element should be called something else, and this
> >> could have its own schema. Maybe "<MultiRequest>"?
> >>
> >>
> >
> > <Request> is the existing outer element of a Request context. My notion
> is that <DecisionsLists> is an optional element which appears prior to the
> first <Attributes> element.
> >
> Yes, but I thought that it would perhaps be better to not put this
> boxcarring stuff into the core schema, but in it's own schema. I think
> it would be neater if we have a "simple" core schema which defines the
> processing model. Additional preprocessing and transport formats would
> go into another schemas.
> But I don't feel too strongly about it, and importing schema files can
> be a bit of an annoyance to work with given the current state of XML
> parsers.

First of all as I have said several times, I only see this feature as being important when a remote PDP is used. (In fact I don't think an imbedded PDP should be using an XML Request Context at all.)

Given that, I have no strong preference for how we deal with the schemas. I would like to hear from implementers on this issue.


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