Berin Loritsch wrote:
The only real difference between the two proposals are the use of @avalon.type
vs. @avalon.component. Both sides have valid points, but in the end it boils
down to what the community as a whole would rather see.
@avalon.type Pro | Con
----------------------------------+-------------------------------------------
1) No overloading of an existing | 1) Forces deprecation of existing tag tag. | 2) Required attributes are more | easily enforced. |
+1
@avalon.component Pro | Con
----------------------------------+-------------------------------------------
1) No cruft from deprecated tags. | 1) Defaults can often times cause
-1
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
