[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces

• To: "J.Pietschmann" <j3322ptm@y...>
• Subject: Re: Namespaces
• From: Jeni Tennison <jeni@j...>
• Date: Wed, 16 Oct 2002 22:21:06 +0100
• Cc: Mike Champion <mc@x...>, xml-dev <xml-dev@l...>
• In-reply-to: <3DADCE5C.8010905@y...>
• Organization: Jeni Tennison Consulting Ltd
• References: <B82ZJH1V7264QKOID00GFNIRMJILKLJ.3dad88e0@MChamp><116545153118.20021016172602@j...> <3DADCE5C.8010905@y...>
• Reply-to: Jeni Tennison <jeni@j...>

Hi Joerg,

> I missed:
>     5. Outlaw declaring namespaces in DTDs as fixed attribute values.

Yep -- we get that kind of thing happening because namespaces are
declared using attributes. If you separate out namespace declarations
for *content* (which you would do with attributes) from namespace
declarations for *markup* (which you wouldn't), then it stops being an
issue. The namespace-declarations-for-content could be defaulted if
that's something that's appropriate for the application (for example,
there's a default default-function-namespace in XQuery). Since
namespace-declarations-for-markup *wouldn't* be declared through
attributes, there'd be no way of defaulting them within the
DTD/schema, so the problems with doing that wouldn't arise.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/

• References:
  • Re: Namespaces
    • From: Mike Champion <mc@x...>
  • Re: Namespaces
    • From: Jeni Tennison <jeni@j...>
  • Re: Namespaces
    • From: "J.Pietschmann" <j3322ptm@y...>

• Prev by Date: Invitation to a Technology Preview for Sun ONE Integration Server,Secure Trading Agent
• Next by Date: Re: Quick Review of XML 1.1 Candidate Recommendation
• Previous by thread: Re: Namespaces
• Next by thread: Re: Namespaces
• Index(es):
  • Date
  • Thread