atom feed19 messages in org.oasis-open.lists.xacmlRe: [xacml] Multiple Decison Request ...
FromSent OnAttachments
Hal LockhartJan 13, 2009 10:11 pm 
Erik RissanenJan 14, 2009 6:47 am 
Hal LockhartJan 14, 2009 9:17 am 
Erik RissanenJan 14, 2009 10:05 am 
Hal LockhartJan 14, 2009 10:23 am 
Rich.LevinsonJan 14, 2009 8:23 pm 
Hal LockhartJan 15, 2009 6:29 am 
Hal LockhartJan 21, 2009 11:21 am 
Erik RissanenJan 21, 2009 10:03 pm 
Rich.LevinsonJan 21, 2009 11:29 pm 
Erik RissanenJan 22, 2009 12:42 am 
Hal LockhartJan 22, 2009 1:05 pm 
Erik RissanenJan 23, 2009 1:06 am 
Rich.LevinsonJan 23, 2009 8:19 pm 
Erik RissanenJan 26, 2009 5:46 am 
Rich.LevinsonJan 26, 2009 6:35 am 
Erik RissanenJan 26, 2009 6:59 am 
Erik RissanenJan 26, 2009 7:06 am 
Rich.LevinsonJan 26, 2009 8:11 am 
Subject:Re: [xacml] Multiple Decison Request Proposal
From:Erik Rissanen (er@axiomatics.com)
Date:Jan 14, 2009 10:05:54 am
List:org.oasis-open.lists.xacml

Hi Hal,

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.

Regards, Erik

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php