Re: [xri-editors] further thinking on mustUnderstand

[Peter C Davis <peter.davis@neustar.biz>]

On Monday 07 February 2005 01:56 pm, Dave McAlpin wrote:
> After discussing this internally, I'm supporting Gabe's option 3. It
> accomplishes what we're looking for while avoiding the problem of
> inappropriate MustUnderstand attributes on immediate children of XRID.
> It also has the nice effect of leaving the current schema intact. Can we
> agree to close this issue?
>

I am fine wrt option 3 as gabe described below i suppose...

--- peterd

>
> 3) We don't use mustUnderstand at all. We can actually get the same
> effect of mustUnderstand by requiring extensions to "wrap" other
> elements. So, for the example above:
>
> <XRIDescriptor>
>     <other:SuperAuthority>
>        <Authority>
>           ...
>           <other:ExtensionElement>...</other:ExtensionElement>
>        </Authority>
>      </other:SuperAuthority>
>      <Service>
>          ...
>      </Service>
> </XRIDescriptors>
>
> This would have the same effect, using *only* a mustIgnore rule, as the
> #1 option. It may make the combining of extension elements quite
> complicated.
>