• To: xml-dev@l...
• Subject: Re: There is a meaning, but it's not in the data alone
• From: Sean McGrath <sean.mcgrath@p...>
• Date: Wed, 30 Jan 2002 09:09:39 +0000
• In-reply-to: <E16VeQs-0006nP-00@s...>
• References: <3C56F1C3.50504@r...><DC3ZNKPNNI4YPN8RQ73URHBSKE775.3c56e3aa@MChamp><3C56F1C3.50504@r...>

>[Gavin Thomas Nicol]
>Yep. I still believe that local processing always wins. From a
>practical perspective, the namespace prefix is usually a lot more
>useful than the namespace itself.

And its positively *scary* the number of apps out there in the real world
that have wired the processing to the prefix - not the fully qualified
name.

Sean

• Follow-Ups:
  • Re: There is a meaning, but it's not in the data alone
    • From: Gavin Thomas Nicol <gtn@r...>
  • Re: There is a meaning, but it's not in the data alone
    • From: Tim Bray <tbray@t...>

• References:
  • Re: There is a meaning, but it's not in the data alone
    • From: John Cowan <jcowan@r...>
  • Re: There is a meaning, but it's not in the data alone
    • From: Mike Champion <mc@x...>
  • Re: There is a meaning, but it's not in the data alone
    • From: Gavin Thomas Nicol <gtn@r...>

• Prev by Date: RE: XLST 'DISTINCT' Equivalent
• Next by Date: RE: QNames in attribute values
• Previous by thread: Re: There is a meaning, but it's not in the data alone
• Next by thread: Re: There is a meaning, but it's not in the data alone
• Index(es):
  • Date
  • Thread