>>> On 04/12/2009 at 12:37, in message
<[log in to unmask]>, Rhys Smith
<[log in to unmask]> wrote:
> A simple <PermitValueRule xsi:type="basic:AttributeValueString"
> value="E-ResourcesAdmins" ignoreCase="true" /> should do the trick I think.
> (i.e. no child <Rule>s)
Yep, thanks, that works fine.
>
> I think the format is obtuse because allowing arbitrary nested XML tags
> (i.e. the boolean logic) around the "real" XML tags (i.e. the individual
> rules) will necessitate horrible XML schema with an obtuse format... So it's
> an undesirable but necessary side effect of having the flexibility required
> by people to build the rules.
It's clearer now that I see that you can start with the simple situation of one value (not documented) and then where you have a more complex situation where you want to release one of several values you move to the next level nested syntax. This is where I have issues yet again with the way its documented; rather than building up logically taking you from the "known" to the "unknown" it just dives in at the "complex" level, but omits the simple case which would make it all clear. :-( Going back to it now and re-reading it with _what I know now_ its easy enough, its just "getting there from here" that's the problem.
Andy
The University of Dundee is a registered Scottish charity, No: SC015096
|