Re: [xacml] Bags of structured type

[Polar Humenn <polar@syr.edu>]

I think you can replace "primitive type(s)"  with "datatype(s)" in that
paragraph. The notion of "primitive" is kind of vague anyway, since you
can introduce new 'primitive' types, which are data types.

I think it just meant that bags are of types that are "representable", and
a bag is not repesentable. The notion was to retrict a data type from
representing a bag as a primitive type. That is, you cannot have an
<AttributeValue> that represents a bag directly. You would need to apply
one of the "*-bag"  functions, or apply an <AttributeDesignator>.

Unfortunately our Bag function(s) are defined for only primitive types.
So, when you introduce a new data type, you must introduce all functions
that deal with it, such as any "*-set"  operations, or any other
"primitive" functions dealing with the types.


Cheers,
-Polar


On Fri, 5 Mar 2004, Tim Moses wrote:

> Colleagues - Our current text says that bags can only be formed of
> collections of primitive type (see extract below).  Is this a mistake?  Is
> there some reason why we would outlaw bags of structured types?  All the
> best.  Tim.
>
> "XACML defines implicit collections of its primitive types.  XACML refers to
> a collection of values that are of a single primitive type as a bag.  Bags
> of primitive types are needed because selections of nodes from an XML
> resource or XACML request context may return more than one value."
>
> -----------------------------------------------------------------
> Tim Moses
> 613.270.3183
>
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php.
>