[
Lists Home |
Date Index |
Thread Index
]
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
|
