Bug #24927 for XML-Atom: Namespace of XML::Atom::Category should be independent from its parent element

Tue Feb 13 11:15:09 2007 takeru.inoue+perl [...] gmail.com - Ticket created

Subject:

Namespace of XML::Atom::Category should be independent from its parent element

I implemented XML::Atom::Service, that supports Service/Category Documents defined in Atom Publishing Protocol (APP). I found that the namespace of XML::Atom::Category is defined by its parent element, but it seems strange. In XML::Atom::Category ver.0.25, the parent namespace is inherited since XML::Atom::Category::element_ns returns undef. However, category and its parent (categories) must be different namespaces; category element is in http://purl.org/atom/ns# or http://www.w3.org/2005/Atom, while categories element is in http://purl.org/atom/app# . It's better that XML::Atom::Category::element_ns would return its namespace explicitly, as follows. sub XML::Atom::Category::element_ns { $XML::Atom::Util::NS_MAP{$XML::Atom::DefaultVersion} };

Fri Oct 05 18:06:15 2007 MIYAGAWA [...] cpan.org - Correspondence added

I'll make this change once I can confirm this is the right fix. Can you quote from Atom RFC spec confirming this is correct? A test patch for this would be nice too.

Fri Oct 05 18:06:18 2007 The RT System itself - Status changed from 'new' to 'open'

Sat Oct 06 06:27:37 2007 takeru.inoue+perl [...] gmail.com - Correspondence added

From:

takeru.inoue+perl [...] gmail.com

Thank you for your response. But now, I think there is no perfect solution for this issue and the current implementation is better. In XML::Atom, XML element must inherit the namespace from their parents. This is because XML::Atom handles two namespaces "http://www.w3.org/2005/Atom" and "http://purl.org/atom/ns#", and namespace of each XML element can't be defined statically. On the other hand, XML::Atom::Service uses just a single namespace "http://www.w3.org/2005/Atom" based on the Internet-Draft, and the namespace can be defined statically like: --- XML::Atom::Service --- sub XML::Atom::Category::element_ns { $XML::Atom::Util::NS_MAP{$XML::Atom::DefaultVersion}; } --- If XML::Atom defined namespace like this, it couldn't handle the other namespace.