Switch to XHTML2

• Key: FOR-184
• Type: New Feature
• Status: Open
• Priority: Major
• Assignee: Unassigned
• Reporter: Nicola Ken Barozzi
• Component/s: Core operations
• Affects Version/s: 0.8

Description

Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations, new sitemap pipelines, new stylesheets, new input/output for "views". See the steps in thread: http://marc.theaimsgroup.com/?t=112512735800002

Comments

[David Crossley]

Grabbing some email threads (there are more still).

[PLAN] Move to XHTML2 in V0.7
http://marc.theaimsgroup.com/?t=107321479800003

Documentv20 --> XHTML
http://marc.theaimsgroup.com/?t=107262813800001

XHTML2 I have read it and I like it... GO READ IT!
http://marc.theaimsgroup.com/?t=102892953700005

XHTML 2 intermediate format (Re: Letting through raw HTML)
http://marc.theaimsgroup.com/?t=104340305700003

[RT] Instead of XHTML 1.0, why don't we implement a subset of the
http://marc.theaimsgroup.com/?t=102884182300009

RelaxNG vs DTDs for forrest validation
http://marc.theaimsgroup.com/?t=107706185900003

[David Crossley]

[PLAN] Move to XHTML2 in V0.7
http://marc.theaimsgroup.com/?l=forrest-dev&m=107321479223106

[Ross Gardler]

Suggested route map from Dave Brondsema (from dev mail list):

Current:
html --\ /-> html
docbook--\ /----> pod
jspwiki ------> document-v12 ------> pdf
document-v12--/
openoffice--/

XHTML (iteration 1):
html --\ /-> html
docbook--\ /----> pod
jspwiki -----> document-v12 --> xhtml2 ------> pdf
document-v12--/
openoffice--/

Then we format by format, start going directly to xhtml2:
html --\ /-> html
docbook---------------------------\ /----> pod
jspwiki -----> document-v12 --> xhtml2 ------> pdf
document-v12--/
openoffice--/


Eventually we get:
html --\ /-> html
doc---------\ /----> pod
jspwiki -----> xhtml2 ------> pdf
document-v12--/
openoffice--/


Skinconfig variables get used in all arrows after the intermediate format. To be more accurate in the diagram, the html output format should probably be split in to one for each skin available.

[Ross Gardler]

We also need to provide:

Eventually we get:
html4 --> XHTML2 (internal) -> output
xhtml1 --> XHTML2 (internal) -> output
xhtml2 --> XHTML2 (internal) -> output

[Gavin]

This has been mentioned again.

Additional comment by Ross:

We have agreed in principle that we make the move whilst restructuring for forrest:views, the question is how?

Additional comment by me (Gavin):

How many people are working on this?

This issue comment is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-

http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"

[David Crossley]

Discussion started again:

Planning the move to XHTML2
http://marc.theaimsgroup.com/?t=112392915600001

XHTML2 - let's do it!
http://marc.theaimsgroup.com/?t=112489497100007

XHTML2
http://marc.theaimsgroup.com/?t=112487264000004

[David Crossley]

Subtasks were added as aresult of this thread:
Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2))
http://marc.theaimsgroup.com/?t=112512735800002

[David Crossley]

See the description of the processing pipeline in trunk/site-author/content/xdocs/TR/2004/WD-forrest10.html

[David Crossley]

A couple more discussion threads re-kindled in 2008:

Re: Focus of org.apache.forrest.plugin.internal.xhtml2
http://markmail.org/message/ttv65i23quvrkzks

XHTML2 as forrest internal
http://markmail.org/message/kawjxjp4ij3j63xk