> From: Steven Noels [mailto:[EMAIL PROTECTED]] > > From: Piroumian Konstantin [mailto:[EMAIL PROTECTED]] > > > > > > I propose that we split up the rather long list of > > > committers in the > > > > > hall of fame document into "active committers" and > > > > "Emeritus Committers" > > > > > like many other projects (e.g. Axis or Struts) do. > > > > > > > > > In addition we could add a short bio/note from each > > > > committer as well > > > > > or at least a link to a page containing this. > > > > > > > > > > What do you think? > > > > > > > > I think it's an excellent idea. > > > > > > Can we (Forrest) make a DTD for it? > > > > Isn't it too specific thing to have a special DTD for it? Why > > not reuse > > document DTD? If we create a DTD for the 'Who we are', then > > we definitely > > will need another DTD for the 'xml.apache.org' front-page > > description, > > the new xml.apache.org frontpage should not be too dependent on a > manually authored XML document, but be the aggregation of a lot of > information snippets from all the various projects. In any case, the > frontpage will be special, i.e. perhaps we would need to create a > separate DTD for it, too. > > > a > > third one for 'Project samples', etc. > > 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.
It was discussed and there were proposed several solutions to this. But is that really needed? We can simple setup separate pipelines for different types of documents. > > > 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. > > In terms of a DTD, I would go for something in the lines of: > > <?xml version="1.0" encoding="UTF-8"?> > <!ENTITY % document PUBLIC > "-//APACHE//ENTITIES Documentation V1.1//EN" > "document-v11.mod"> > %document; > > <!ELEMENT contributors (header?, (category)+)> > <!ATTLIST contributors %common.att; > %title.att;> > > <!ELEMENT category (contributor+) > > <!ATTLIST category %title.att; %common.att;> > > <!ELEMENT contributor (person, img?, bio)> > <!ATTLIST contributor %common.att;> > > <!ELEMENT bio (%blocks;)*> > <!ATTLIST bio %common.att;> > > 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> > </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? Not sure about the text, but the structure is Ok. ;) Only I would change 'contributors' to 'developers'. (Btw, see change.xml - it already contains the list of developers). Konstantin > > </Steven> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
