Steven Noels wrote: > > <snip/> > You're absolutely right, we should be careful not to create *too* many > different DTD's. Furthermore, a Cocoon pipeline has no access to the DTD > declaration so it can't modify processing flow depending of the doctype > of a document. > > > Though, if having so many formats is not contradictory to the > > Forrest vision > > then I am +1 for it. > > We could do a simple document consisting of a table, of course. Having a > specific DTD however ensures we have a common information structure > across all XML Apache sub-projects, which is part of the Forrest vision. > I think we should simply use the usual dtd. It available, can be used immediatly and offers all possibilites we need.
> <snip/> > > validating documents similar to this: > > <?xml version="1.0" encoding="ISO-8859-1"?> > <!DOCTYPE contributors > PUBLIC "-//APACHE//DTD Project Contributors V1.0" "contrib-v10.dtd"> > <contributors title="Contributors"> > <category title="Active Committers"> > <contributor> > <person name="Carsten Ziegeler" email="[EMAIL PROTECTED]"/> > <bio> > <p>Carsten is release manager for Cocoon2, and tries to avoid > cutting his hands while doing so.</p> :) - good joke! > </bio> > </contributor> > </category> > <category title="Emeritus Committers"> > <contributor> > <person name="Stefano Mazzocchi" email="[EMAIL PROTECTED]"/> > <bio> > <p>Know what? Sometimes he wonders why he bothers keeping > himself > subscribed to this mail list: you people do an incredible > job even without his guidance ;-)</p> > </bio> > </contributor> > </category> > </contributors> > > Would this make sense? And what about the active developers and emeritus committers? I still believe a simple <s2 title="Active committers">, <s2 title="emeritus committers"> is sufficient. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
