Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
Ross Gardler wrote: David Crossley wrote: I revised the list, taking the replies into account and adding some new queries. I've now put these into Jira as sub-tasks. Thanks for your input. http://issues.apache.org/jira/browse/FOR-184 So are we still going to attempt to make some progress on this at our first ForrestTuesday 6 September? -David
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
David Crossley wrote: Ross Gardler wrote: David Crossley wrote: I revised the list, taking the replies into account and adding some new queries. I've now put these into Jira as sub-tasks. Thanks for your input. http://issues.apache.org/jira/browse/FOR-184 So are we still going to attempt to make some progress on this at our first ForrestTuesday 6 September? +1, I created the sub tesks in preparation. Ross
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
David Crossley wrote: I revised the list, taking the replies into account and adding some new queries. - agree the subset of XHTML2 to be used and document that via example. See other thread. - create DTD's Why do we need DTDs for use with internal structure? For using XHTML2 as an input format. In fact it will be a modularization of XHTML2 via RelaxNG validation. - Decide how to make the pipeline process. Now we have body-*.html and stuff, but a simpler process should be devised. - Convert all sitemaps and transformers to utilise that new process. - add a sitemap that processes *.xhtml2 files in a parallel section Does this refer to XHTML2 as input source files? It refers to all processing. What processing is needed? That's what has to be decided ;-) Whoever does it gets to try a simpler pipeline (without the body, header, etc doc matches, but just a single transformation). - convert all forrest:contracts to accept XHTML2 as input rather than XDoc while keeping the old ones in the meantime - convert forrest:views to work with XHTML2 and make them work in the extra pipeline. Here we should be able to accept XHTML2 input and produce the usual output. For legacy: - xdoc to XHTML2 stylesheet and create XDoc input plugin - document migration process -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
Nicola Ken Barozzi wrote: David Crossley wrote: I revised the list, taking the replies into account and adding some new queries. - agree the subset of XHTML2 to be used and document that via example. See other thread. - create DTD's Why do we need DTDs for use with internal structure? For using XHTML2 as an input format. For that part i did understand the need. If the xml instances declare them, then the parser needs to resolve them locally. Same with any document type. Of course there are no DTDs yet at Appendix F or G. However, we are discussing internal processing, and i was wondering what is the need for DTDs there. Is there any need? Or am i misunderstanding something about XHTML2 and DTDs? In fact it will be a modularization of XHTML2 via RelaxNG validation. - Decide how to make the pipeline process. Now we have body-*.html and stuff, but a simpler process should be devised. - Convert all sitemaps and transformers to utilise that new process. - add a sitemap that processes *.xhtml2 files in a parallel section Does this refer to XHTML2 as input source files? It refers to all processing. Okay, then i will ask parallel to what? Do you mean keep the existing pipelines and starting this new one so that old and new can work side-by-side until the new stuff is ready. -David What processing is needed? That's what has to be decided ;-) Whoever does it gets to try a simpler pipeline (without the body, header, etc doc matches, but just a single transformation). - convert all forrest:contracts to accept XHTML2 as input rather than XDoc while keeping the old ones in the meantime - convert forrest:views to work with XHTML2 and make them work in the extra pipeline. Here we should be able to accept XHTML2 input and produce the usual output. For legacy: - xdoc to XHTML2 stylesheet and create XDoc input plugin - document migration process -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
Nicola Ken Barozzi wrote: David Crossley wrote: Nicola Ken Barozzi wrote: David Crossley wrote: I revised the list, taking the replies into account and adding some new queries. I've now put these into Jira as sub-tasks. Thanks for your input. Ross
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
I revised the list, taking the replies into account and adding some new queries. - agree the subset of XHTML2 to be used and document that via example. See other thread. - create DTD's Why do we need DTDs for use with internal structure? - Decide how to make the pipeline process. Now we have body-*.html and stuff, but a simpler process should be devised. - Convert all sitemaps and transformers to utilise that new process. - add a sitemap that processes *.xhtml2 files in a parallel section Does this refer to XHTML2 as input source files? What processing is needed? - convert all forrest:contracts to accept XHTML2 as input rather than XDoc while keeping the old ones in the meantime - convert forrest:views to work with XHTML2 and make them work in the extra pipeline. Here we should be able to accept XHTML2 input and produce the usual output. For legacy: - xdoc to XHTML2 stylesheet and create XDoc input plugin - document migration process
