• From: Nicolas LEHUEN <nicolas.lehuen@u...>
• To: "'francis@r...'" <francis@r...>,"'Fuchs, Matthew'" <matthew.fuchs@c...>
• Date: Fri, 31 Aug 2001 09:30:06 +0200

Francis wrote :

>"Fuchs, Matthew" wrote:
>>  
>> As I explain above, a "push program" based on valid XSDL 
>with local names is
>> not vulnerable if match statements to match global elements 
>are qualified,
>> and match statements to match local names are not and 
>include the parent in
>> the match path, is not fragile in the way you describe.  
>> 
>This is only sweeping the dust under a different corner of the carpet
>unless one can prescribe a reasonably efficient and productive way of
>building the correct match paths to disambiguate unqualified local
>elements, which can after all be nested indefinitely deep.

The correct match path is, to me, the one that goes at least up to the first
global parent element. Matching at least this global parent element is
required in order to have an idea of the semantic of the matched element,
which prevent your program from nonsense.

Regards,
Nicolas

• Follow-Ups:
  • Template matching (was RE: Enlightenment via avoiding the T-word)
    • From: Evan Lenz <elenz@x...>

• Prev by Date: RE: Suggested guidelines for using local types. (was Re: Enlightenment via avoiding the T-word)
• Next by Date: RE: Enlightenment via avoiding the T-word
• Previous by thread: RE: Enlightenment via avoiding the T-word
• Next by thread: Template matching (was RE: Enlightenment via avoiding the T-word)
• Index(es):
  • Date
  • Thread