On 1/3/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Joern Nettingsmeier wrote: > > [...] > > about: > > > > every *publication* can be used as a *template*, producing *derived > > publications* or *child publications*. templating is implemented using > > the *fallback* mechanism, a lenya-specific uri resolver that can be > > applied to any uri reference in xml files by using "fallback://" as a > > protocol specifier. > > the creation of a new child publication from a template is called > > *instantiation*. child publications can *inherit* > > Hmm, no idea if we should use the term "inheritance" here. It is > pre-occupied by the OOSD term, and people might get confused ... > I'd rather say "child publications can use features ...". > > -- Andreas > > > features from the > > template in two ways: by *copying* files from the template during > > instantiation, or by *referencing* those files. > > *copying* severs the link between child and template - later changes to > > the template will not affect the child. *referencing* implies that all > > changes to the template will immediately affect the child as well. > > > > is this consistent with the usage among developers? > > > > regards, > > > > jörn > >
As for comments within files, it might be worthwhile to more carefully consider how this is structured, rather than just putting plain text inside of comment tags. It would be nice to have the internal documentation in these files be extractable (someday) by a program, in the same way that javadoc documentation is easily extractable from java source code. See http://www.codeproject.com/soap/xsltdocumentor.asp an example of such a program for XSLT files in particular. Does anyone else have any suggestions in this area? We will need a syntax for documenting xslt and xmap files especially. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
