Thursday, January 13, 2005, 1:34:24 AM, you wrote:
> On 13 Jan 2005, at 1:28 am, David Powell wrote: >> It needs to be like this: (because namespace defaults don't apply to >> attributes.) >> >> <feed xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-04";> >> ... >> <entry> >> <ex:note atom:notation="structured>...</ex:note> >> </entry> >> </feed> > That's not valid either, since the atom: namespace hasn't been > declared. Sorry, I meant to say: <feed xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-04"; atom:xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-04";> ... <entry> <ex:note atom:notation="structured>...</ex:note> </entry> </feed> > Relying on fixed Q-names causes problems for some software > and is generally bad practice. I agree - I wasn't implying that the atom namespace prefix is fixed. See Section 1.4, it applies here too: > This specification uses XML Namespaces [W3C.REC-xml-names-19990114] > to uniquely identify XML elements and attribute names. It uses the > following namespace prefixes for the indicated namespace URIs; > > "atom": http://purl.org/atom/ns#draft-ietf-atompub-format-04 > > Note that the choice of any namespace prefix is arbitrary and not > semantically significant. > I actually prefer your wrong example: > <ex:note notation="structured">...</ex:note> I prefer it to look at, but I don't think we should be defining the meaning of un-namespaced attributes in somebody elses element. It seems more appropriate to use a namespaced attribute for this. -- Dave
