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

Re: Proposed genx changes

• To: james.anderson@s...
• Subject: Re: Proposed genx changes
• From: Tim Bray <tbray@t...>
• Date: Fri, 12 Mar 2004 07:26:57 -0800
• Cc: "xml-dev@l... DEV" <xml-dev@l...>
• In-reply-to: <40517E17.D36D1659@s...>
• References: <97875058-73A9-11D8-A512-000A95A51C9E@t...> <40517E17.D36D1659@s...>

On Mar 12, 2004, at 1:09 AM, james anderson wrote:

>> 2. You can now say
>> genxDeclareNamespace(w, "http://example.com", "", &status)
>> to make this the default namespace whenever it's in effect.
>> IF there is a default namespace in effect and you try to insert an
>> element/attribute that's not in a namespace, that's an error.
>
> why is the consequence not to automatically undeclare and emit a 
> undeclaration
> of the default namespace? (with the possible consequence, that the 
> default
> declaration subsequently reappears in child elements as required?)

Yep, you're right, I was wrong.  A couple of people pointed this out 
already offline.

> what is the possible effect on attribute names which are "not in any 
> namespace"?

Attribute names can only be in a namespace if prefixed, so a non-issue.

>> 4. There's a new call genxAddAllNamespaces(genxWriter w) which makes
>> sure all the namespaces you've declared so far are in scope.  
>> Normally,
>> you'd do this on the root element.
>
> why is this necessary? given the namespace scoping rules, it is not 
> guaranteed
> to be sufficient. is it just a matter of convenience?

Some people think it's good practice to declare all your namespaces 
once on the root element.  This facilitates that.

> ? why is the GENX_DUPLICATE_PREFIX error necessary? if genx is already 
> capable
> of egnerating prefixes where they are not declared, why does that not 
> apply to duplicates?

It would add extra complexity and work to Genx to support a namespace 
with multiple different prefixes.  I don't think this work is worth 
doing. -Tim

• References:
  • Proposed genx changes
    • From: Tim Bray <tbray@t...>
  • Re: Proposed genx changes
    • From: james anderson <james.anderson@s...>

• Prev by Date: RE: Citations (WAS RE: W3C suckered by Micros oft?)
• Next by Date: RE: How does XML work with Linux
• Previous by thread: Re: Proposed genx changes
• Next by thread: RE: Citations (WAS RE: W3C suckered by Microsoft?)
• Index(es):
  • Date
  • Thread