Re: [PEPr] Comment on HTML::HTML_Element
| From: | Paul M Jones | Date: | Thu, 22 Apr 2004 16:24:19 +0000 |
| Subject: | Re: [PEPr] Comment on HTML::HTML_Element | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28268@lists.php.net to get a copy of this message | ||
On Apr 22, 2004, at 11:19 AM, Alan Knowles wrote:
An excellent point. I wish there was an easy and fair way to resolve it (to avoid something like the domain-name rush of the 90s.) Perhaps another RFC, to define reserved name spaces? ;-)Agreed that the HTML_Common API might use some updating. However, is it fair to use one developer's future plans as a reason to change a current proposed name from another developer? Under that model, I think it may become too easy to "squat" on a namespace indefinitely.I guess what I'm saying is that if we are to allow someone to such a prime real estate, then it should offer a good alternative.. (even if I didnt do it ;)
technically there is a bit of a precident for reserving names, or being carefull in allocating them....Being careful is all I'm thinking about, really, especially when it comes to reasons. Perhaps PEAR group can define and clarify a position on this kind of sticky issue. -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and HTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: a collaborative online documentation system. http://wiki.ciaweb.net/yawiki/index.php?area=Yawiki