Re: [ubl-cmsc] Context Rule Syntax

[Eduardo Gutentag <eduardo.gutentag@sun.com>]

My apologies, this was supposed to be a response to (8) "Issues with ebXML Document".

Please delete this message from your inbox, I will replace it with the appropriate one
shortly.


Eduardo Gutentag wrote:
> 
> Matthew Gertner wrote:
> >
> > 7) Syntax of the context rules in general. Assuming that we decide to use a
> > canonical syntax language (probably XSD), should we align the names of the
> > context tags so they match the tags in the schema language? Can we handle
> > all of the various constructs (global types, local types, local elements,
> > etc.) that are retained by the Naming and Design subcommittee? Are any of
> > the constructs redundant (e.g. what is the different between "CreateElement"
> > and an "Add" tag containing and "Element" tag)?
> 
> I think the first think we should take a hard look at is the <Condition> element.
> Originally this was an empty element, contained in <Rule>. That is, for each
> <Rule> there was one <Condition>. A way to order the rules, so that different
> conditions were applied in a pre-determined sequence, was needed, so the order
> attribute to <Rule> was added. Later on <Condition> became a true container, and
> there was no indication that a <Rule> could not contain more than one <Condition>
> or that a <Condition> could not contain another <Condition>.
> 
> It seems to me that the first method had the advantage of simplicity and
> modularity (in that you could actually copy and paste rules from one document
> to another without having to worry too much about unintended consequences).
> However, there was no way to express hierarchies or sequence of actions
> other than through the "order" element.
> 
> The second method, while allowing the direct expression of hierarchies through
> document hierarchy, has the distinct disadvantage of presenting obstacles to
> simple copy and paste. I'm not convinced, however, that this is a practical
> disadvantage (as opposed to theoretical). But if we are to retain this second
> method, then we have to re-examine the need for the "apply" attribute as well as
> "order".
> 
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> --
> Eduardo Gutentag               |         e-mail: eduardo.gutentag@Sun.COM
> XML Technology Center          |         Phone:  (510) 986-3651 x73651
> Sun Microsystems Inc.          |
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

-- 
Eduardo Gutentag               |         e-mail: eduardo.gutentag@Sun.COM
XML Technology Center          |         Phone:  (510) 986-3651 x73651
Sun Microsystems Inc.          |