Re: XHTML2 - let's do it!
David Crossley wrote: The two example XHTML2 instances in that plugin now validate (index.html and samples/xhtml2_subset.html). WooHoo! Thanks David. Ross
Re: XHTML2 - let's do it!
Nicola Ken Barozzi wrote: > > IMHO we should eventually support every xhtml2 module, but it's not > strictly needed. Ok to leave it out for now, and see later to include it > via an input module, as it's just a (legacy induced) substitute for > . Today i added the complete XHTML2 RELAX NG schema (main/webapp/resources/schema/relaxng/WD-xhtml2-20050527) and a driver for Forrest (xhtml2-forrest.rng) that uses just the modules that we decided so far. There is a demonstration of using the new Jing transformer in whiteboard/plugins/org.apache.forrest.plugin.internal.xhtml2 Just uncomment the transformer in structurer.xmap and/or add similar transformers to any other parts of the sitemaps. The two example XHTML2 instances in that plugin now validate (index.html and samples/xhtml2_subset.html). -David
Re: XHTML2 - let's do it!
Ross Gardler wrote: > Nicola Ken Barozzi wrote: > > >> 10. XHTML Hypertext Module >> http://www.w3.org/TR/xhtml2/mod-hypertext.html >> * 10.1. The a element > > > We don't need this, it's use is deprecated in XHTML2 by allowing an href > attribute on any element: IMHO we should eventually support every xhtml2 module, but it's not strictly needed. Ok to leave it out for now, and see later to include it via an input module, as it's just a (legacy induced) substitute for . -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: XHTML2 - let's do it!
Nicola Ken Barozzi wrote: 10. XHTML Hypertext Module http://www.w3.org/TR/xhtml2/mod-hypertext.html * 10.1. The a element We don't need this, it's use is deprecated in XHTML2 by allowing an href attribute on any element: "Linking: In HTML 3, only a elements could be the source and target of hyperlinks. In HTML 4 and XHTML 1, any element could be the target of a hyperlink, but still only a elements could be the source. In XHTML 2 any element can now also be the source of a hyperlink, since href and its associated attributes may now appear on any element. So for instance, instead of Home, you can now write href="home.html">Home. Even though this means that the a element is now strictly-speaking unnecessary, it has been retained." - http://www.w3.org/TR/2005/WD-xhtml2-20050527/introduction.html#s_intro_differences I understand that we will, most likely, want to support this within our input formats, but I propose we don't support it internally, it only serves to add more complexity to our stylsheets since we will have to support the @href attribute anyway (it is part of 13. XHTML Hypertext Attributes Module - http://www.w3.org/TR/xhtml2/mod-hyperAttributes.html) Ross
Re: XHTML2 - let's do it!
David Crossley wrote: CAUTION: I have only skim read the recommendations, I do not consider myself "clued in" yet. Internationalisation: - Do we also need the i18n? 14. XHTML I18N Attribute Module In our current sitemap, the i18n text is being handled towards the end of the process, so we need to carry the i18n attributes all the way through. I think that we will need this, probably not to support what we have at present, but we are getting an increasing number of requests for i18n support. We may as well consider the future now and reuse what XHTML2 gives us. Entity references: -- Entity references (e.g. ö and ™) in the input are resolved and expanded by the xml parser, so i don't think that the internal mechanism needs to carry them around and know how to resolve them. Does anyone see it differently? I see it as you do. Ross
Re: XHTML2 - let's do it!
Internationalisation: - Do we also need the i18n? 14. XHTML I18N Attribute Module In our current sitemap, the i18n text is being handled towards the end of the process, so we need to carry the i18n attributes all the way through. Entity references: -- Entity references (e.g. ö and ™) in the input are resolved and expanded by the xml parser, so i don't think that the internal mechanism needs to carry them around and know how to resolve them. Does anyone see it differently? -David
Re: XHTML2 - let's do it!
Nicola Ken Barozzi wrote: > > First of all, we need a sample XHTML2 document that we will use to > render. It will contain all the module elements and attributes that we > will use and should be regularly updated to keep the new ones as we > progress. The content should be a description of the tags being used, so > to keep the documentation and the test in one page. > > Basically, an XHTML2 version of the following, without any feature > missing and with extra XHTML2 features: > > http://forrest.apache.org/dtdx/document-v20.html > > Probably we should do a simpler page that is divided in sections as in > the XHTML2 modules document. > > It shall validate with the RelaxNG scheme that the spec provides: > > http://www.w3.org/TR/xhtml2/xhtml20_relax.html > > Any takers? > > Eventually, we will provide support for all the XHTML2 tags and > attributes except the presentational ones, but we can start with a base > subset that should encompass all we do now: I suppose that we look at our current DTD v2.0 for what is needed as a base. We have some things like an "imagemap" demo contributed to our seed-sample site. So we would we need: 20. XHTML Image Map Attributes Module I agree with these below, but will look again to see if we missed any. [ snip module list ] > Note also this module's role collection: > > 25. XHTML Role Access Module > http://www.w3.org/TR/xhtml2/mod-role.html#col_Role > * 25.2. Role Collection > > It nicely defines page section names. IMHO we should use this to define > a page layout. It does not have sufficient structure for our full layout using just the standard attributes, so we would use those and define some additional ones. It seems ideal. I presume that this is the " When the above is agreed on and done, I will mail the second step. The first version of the sample document can define our decided list of modules. -David
XHTML2 - let's do it!
First of all, we need a sample XHTML2 document that we will use to render. It will contain all the module elements and attributes that we will use and should be regularly updated to keep the new ones as we progress. The content should be a description of the tags being used, so to keep the documentation and the test in one page. Basically, an XHTML2 version of the following, without any feature missing and with extra XHTML2 features: http://forrest.apache.org/dtdx/document-v20.html Probably we should do a simpler page that is divided in sections as in the XHTML2 modules document. It shall validate with the RelaxNG scheme that the spec provides: http://www.w3.org/TR/xhtml2/xhtml20_relax.html Any takers? Eventually, we will provide support for all the XHTML2 tags and attributes except the presentational ones, but we can start with a base subset that should encompass all we do now: 7. XHTML Document Module http://www.w3.org/TR/xhtml2/mod-document.html * 7.1. The html element * 7.2. The head element * 7.3. The title element * 7.4. The body element 8. XHTML Structural Module http://www.w3.org/TR/xhtml2/mod-structural.html * 8.1. The address element * 8.2. The blockcode element * 8.3. The blockquote element * 8.4. The div element * 8.5. The heading elements * 8.6. The p element * 8.7. The pre element * 8.8. The section element * 8.9. The separator element 9. XHTML Text Module http://www.w3.org/TR/xhtml2/mod-text.html * 9.1. The abbr element * 9.2. The cite element * 9.3. The code element * 9.4. The dfn element * 9.5. The em element * 9.6. The kbd element * 9.7. The l element * 9.8. The quote element * 9.9. The samp element * 9.10. The span element * 9.11. The strong element * 9.12. The sub element * 9.13. The sup element * 9.14. The var element 10. XHTML Hypertext Module http://www.w3.org/TR/xhtml2/mod-hypertext.html * 10.1. The a element 11. XHTML List Module http://www.w3.org/TR/xhtml2/mod-list.html * 11.1. Definition lists: the dl, di, dt, and dd elements * 11.2. The nl element * 11.3. The ol and ul elements * 11.4. The li element * 11.5. The label element * 11.6. Issues 12. XHTML Core Attributes Module http://www.w3.org/TR/xhtml2/mod-core.html 13. XHTML Hypertext Attributes Module http://www.w3.org/TR/xhtml2/mod-hyperAttributes.html 17. XHTML Embedding Attributes Module http://www.w3.org/TR/xhtml2/mod-embedding.html 22. XHTML Metainformation Module http://www.w3.org/TR/xhtml2/mod-meta.html 23. XHTML Metainformation Attributes Module http://www.w3.org/TR/xhtml2/mod-metaAttributes.html 29. XHTML Tables Module http://www.w3.org/TR/xhtml2/mod-tables.html Note also this module's role collection: 25. XHTML Role Access Module http://www.w3.org/TR/xhtml2/mod-role.html#col_Role * 25.2. Role Collection It nicely defines page section names. IMHO we should use this to define a page layout. When the above is agreed on and done, I will mail the second step. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
