• To: Arjun Ray <aray@n...>, xml-dev@l...
• Subject: Re: xml:namespace
• From: Dave Pawson <dpawson@n...>
• Date: Fri, 09 May 2003 17:37:14 +0100
• In-reply-to: <c5cmbvkcgobkomvegrvvddtufd3v86p6r5@4...>
• References: <5.2.0.9.2.20030508141644.00aea4d8@p...><5.2.0.9.2.20030507181836.00af5d40@p...><5.2.0.9.2.20030507181836.00af5d40@p...><f7jibvogorhif66ed6bvs8utkv1mn7r3gf@4...><5.2.0.9.2.20030508141644.00aea4d8@p...>

At 04:39 09/05/2003 +0000, Arjun Ray wrote:
>Dave Pawson <dpawson@n...> wrote:
>
>| I'm curious if there are alternatives... that have been tried
>| for the problem of element discrimination.  Deployed or not.
>
>Mapping via attributes.  See, e.g.
>
>  http://groups.google.com/groups?selm=01bc90ae$6fa19160$3219c1cf@w...

<grin/> AF was suggested in the corridor too... or at least AF without the 
baggage
(needs a jargon free re-write perhaps?).

<quote>
Note, however, that it's *ALWAYS* up to the creator of a document to
resolve any semantic conflicts among the various architectures used, just
as its up to a programmer to combine object libraries correctly in the
programs they write. </quote>

Duly noted.

regards DaveP

• Follow-Ups:
  • Re: xml:namespace
    • From: Arjun Ray <aray@n...>

• References:
  • Re: xml:namespace
    • From: Dave Pawson <dpawson@n...>
  • xml:namespace
    • From: Dave Pawson <dpawson@n...>
  • Re: xml:namespace
    • From: Arjun Ray <aray@n...>
  • Re: xml:namespace
    • From: Arjun Ray <aray@n...>

• Prev by Date: Re: Clumping of W3C Specifications
• Next by Date: RE: Ten new XQuery, XSLT 2.0 and XPath 2.0 Working
• Previous by thread: Re: xml:namespace
• Next by thread: Re: xml:namespace
• Index(es):
  • Date
  • Thread