> At 11:56 PM 6/2/2002 -0700, Ronald Bourret wrote: > > > How about: > > > 1) The qName parameter is renamed "rawName", and documentation explains > > > that this is both the Qualified Name in namespace-aware processing and the > > > Name in namespace-unaware processing. > > > >-1. rawName doesn't mean anything. qName does. > > Sure. Just "name" would be fine by me. Less meaning may be good in this case.
What if we transfer the Expat approach in a compatible way: We define one parameter as the "Name". It contains whatever the element's name is, regardless of NS processing on/off, regardless of the element name belonging to a namespace or not (this means: if Prefix has a meaning, it is not part of the name!). Whether the element name belongs to a namespace is determined by the URI parameter being non-empty. If there is a prefix, we have it in the remaining parameter. Now, if we just have the prefix there, this would be like Expat, and not conmpatible - so we should use prefix+':'+name. Let's map localName to Name, and qName to the prefix parameter. This would then mean: - localName is always present, and reports whatever the name is, depending on the context (e.g. if NS processing is on, a prefix would not be part of the name, if the element is not in a namespace, localName contains the full name, ...) - URI means what it used to mean. Empty URI means: no namespace. - qName is present as prefix+':'+name when there is a prefix/namespace, otherwise it is optional. This could be changed to making it required, if that is better for compatibility with existing applications. Karl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
