Sylvain Wallez wrote: > > > Neither do I, so maybe a solution is to have an additional constraint on > > XML configuration documents : local attribute names must be unique, even > > if their namespaces are different. This isn't really restrictive and can > > easily be checked by SAXConfigurationHandler. We could then use local > > names for attributes also. > > Berin, > > You didn't gave your thoughts about the above. Attribute names are > prefixed if they do not belong to the namespace of the current > configuration element. And since it's a different namespace, the > Namespace object attached to the current element won't help to know the > namespace URI of the attribute. I admit few people will have mixed > attribute namespaces in confing files, but this is a potential problem.
In a config file, all attributes should belong to the same namespace as the element to which they belong. Otherwise there is too much complexity in the configuration file. > So, should attributes names be kept prefixed, even if it makes it > difficult to use them because we cannot get the URI from the prefix ? Or > should a restriction on XML configuration documents be enforced, like > the one proposed above ? Another restriction could be to forbid > attributes from a different namespace than the one of the element > they're attached to. +1 on the last thing. If you forbid other namespaces than the element namespace, you simplify your life tremendously. We don't need to do XLink or anything like that. There *might* be some container clues that we would want to add to a component definition--but I am not convinced we want to get namespace information for Configuration objects. It would just make them more difficult to use. > > Sylvain. > -- > Sylvain Wallez > Anyware Technologies - http://www.anyware-tech.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
