• From: James Fuller <james.fuller.2007@g...>
• To: "Costello, Roger L." <costello@m...>
• Date: Tue, 11 Aug 2009 21:57:35 +0200

> Conversely, if I use a QName:
>
> <Example xmlns:aquarium="http://www.aquarium.org">
>    <Object>aquarium:tank</Object>
> </Example>
>
> and take the data out of context I get this:
>
>    aquarium:tank
>
> This appears to be richer.

I have not been following this (other other namespace related
threads), but it occurs to me if you take aquarium:tank out of context
it fundamentally loses its link to the  namespace e.g.
xmlns:aquarium="http://www.aquarium.org".

Prefixes are just prefixes, nothing more then a hint/reference to
something important (and hopefully specifically unique) ... once we
start thinking there is a shared dictionary of what prefixes are,
instead of a namespace URI isn't this where problems start creeping in
?

Jim Fuller

• Follow-Ups:
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Costello, Roger L." <costello@m...>

• References:
  • Lesson Learned: Use namespaces for both markup and data
    • From: "Costello, Roger L." <costello@m...>
  • Re: Lesson Learned: Use namespaces for both markup and data
    • From: Uche Ogbuji <uche@o...>
  • Re: Lesson Learned: Use namespaces for both markup and data
    • From: Kurt Cagle <kurt.cagle@g...>
  • RE: Lesson Learned: Use namespaces for both markup and data
    • From: Michael Kay <mike@s...>
  • Re: Lesson Learned: Use namespaces for both markup anddata
    • From: Evan Lenz <evan@e...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Costello, Roger L." <costello@m...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: Amelia A Lewis <amyzing@t...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Costello, Roger L." <costello@m...>