W3C home > Mailing lists > Public > public-ws-policy@w3.org > August 2006

New Issue: Policy framework should document extensibility points using {any} and @{any} in xpath-like expressions, and define these in Notational Conventions section

From: David Orchard <dorchard@bea.com>
Date: Tue, 15 Aug 2006 16:27:08 -0700
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C021AE305@repbex01.amer.bea.com>
To: <public-ws-policy@w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3590 

(content follows)

Policy framework defines a number of elements that have extensibility
points
for attributes and elements.  In a few places, such as were <assertion>s
can
occur, the extensibility point is documented.  

Every place where extensibility can occur, such extensibility should be
documented.  The places are:
/wsp:Policy/@{any}
/wsp:Policy/.../wsp:PolicyReference/@{any}
/wsp:Policy/.../wsp:PolicyReference/{any}
/wsp:Policy/wsp:ExactlyOne/@{any}
/wsp:Policy/wsp:ExactlyOne/wsp:All/@{any}

Note the first 2 cases have the elipses notation already in the pseudo
schema. 
The remaining places may not be extensibible by design.  

The description of attribute extensibility from attachments is
typically:
Additional attributes MAY be specified but MUST NOT contradict the
semantics of
the owner element; if an attribute is not recognized, it SHOULD be
ignored.

Though I do think the "ignoring" part is redundant with the
extensibility
processing model text.

I propose that:
1. the same notation conventions from the attachment document be
included in
framework
2. the agreed upon extensibility points are documented.

Cheers,
Dave
Received on Tuesday, 15 August 2006 23:28:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:40 GMT