> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 08, 2001 7:24 AM > You say there is an element named project, that may contain either a > target, taskdef or property element by (omitting data types for > brevity): > > <!ELEMENT project (target | property | taskdef)*> > > This doesn't say anything about the parent element of project. If you > have a task that contains a project child element, this DTD would > allow you to nest targets into them. > > Likewise you define the attributes for project (name, default and > basedir attribute) without any reference to a context: > > <!ATTLIST project > name CDATA #REQUIRED > default CDATA #REQUIRED > basedir CDATA #IMPLIED> > > So you cannot have a <project> tag with any other attribute than these > three - no matter where you put it.
Ahh, I stand corrected... there *is* a DTD! :) > > > Wich tags should be reserved? Only <project> and <target>? > > Right now we have elements for project, target, all defined tasks, all > defined datatypes and all nested elements they know of. > > Don't confuse "elements" with "attributes". You can have "name" > attributes in several elements meaning totally different things for > example. > > That we should use the same names for attributes that have the same > meaning and different attribute-names for things that do different > things is a separate issue 8-) Good explanation!
