I think there's precedence for translation between systems, as seen in the difference between CSS style property names and their JavaScript counterparts.
I would prefer that the XML be all-lowercase/hyphenated and the JSP be camel case, to maintain consistency with other styles in their respective domains. However, I am not in a position to put a ton of time into either implementing or debating... Joe On 2/14/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
2007/2/10, Antonio Petrelli <[EMAIL PROTECTED]>: > Do you think that the kind of refactoring that you suggested can be > done also for JSP tags? I think that if the names are the same, the > user will understand better their meaning. That's strange, it seems that JSP tag names prefer camel case and not dashes. So now I am asking myself if: * we should stick with the old JSP tags, though the names of XML elements are different to JSP tags; * we should change the JSP tags names, though it breaks the "standard"; * rollback the changes for the XML elements to go back to camel case, though it breaks another "standard". This is really an hamletic question... Please help! Antonio
-- Joe Germuska [EMAIL PROTECTED] * http://blog.germuska.com "The truth is that we learned from João forever to be out of tune." -- Caetano Veloso
