Re: [Zope-dev] SVN: z3c.pt/trunk/TODO.txt
Malthe Borch wrote: 2008/9/9 Philipp von Weitershausen [EMAIL PROTECTED]: +- Make e.g. tal:block tal:foo / and metal:foo metal:define-macro/ etc. + work Are we sure we want this? It's (afaik) not correct XML; It's not? How so? If the element belongs to some namespace, then attributes from this namespace should be native to it. But I couldn't find any documentation to support that this is a strict requirement. Perhaps it should be allowed, then. As far as I know in XML, attributes without an explicit namespace prefix are not in any namespace at all. Default namespaces don't apply to attributes. ZPT seems to have a different interpretation, perhaps. Though in the end the processor determines what to do with attributes, of course. It's just that XML processors shouldn't place an attribute into a namespace unless there is an explicit prefix. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: z3c.pt/trunk/TODO.txt
Martijn Faassen wrote at 2008-9-10 11:32 +0200: ... As far as I know in XML, attributes without an explicit namespace prefix are not in any namespace at all. Default namespaces don't apply to attributes. http://www.w3.org/TR/2006/REC-xml-names-20060816/#scoping-defaulting specifies: the interpretation of unprefixed attributes is determined by the element on which they appear. The tal/metal: elements have decided that unprefixed attributes are interpreted as belonging to this namespace. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: z3c.pt/trunk/TODO.txt
Chris McDonough wrote: Log message for revision 90974: Added: z3c.pt/trunk/TODO.txt === --- z3c.pt/trunk/TODO.txt (rev 0) +++ z3c.pt/trunk/TODO.txt 2008-09-09 00:03:08 UTC (rev 90974) @@ -0,0 +1,4 @@ +- Make e.g. tal:block tal:foo / and metal:foo metal:define-macro/ etc. + work Are we sure we want this? It's (afaik) not correct XML; but maybe an exception should be raised, rather than no interpretation. \malthe ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: z3c.pt/trunk/TODO.txt
On Tuesday 09 September 2008, Malthe Borch wrote: If the element belongs to some namespace, then attributes from this namespace should be native to it. But I couldn't find any documentation to support that this is a strict requirement. Perhaps it should be allowed, then. It's not strict. It's a shortcut. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: z3c.pt/trunk/TODO.txt
2008/9/9 Stephan Richter [EMAIL PROTECTED]: It's not strict. It's a shortcut. No it's other way around. tal:block for= / is the short-cut for tal:block tal:for= /. Previously only the short-cut was allowed; this has been changed in the most recent release of z3c.pt. \malthe ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
