You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Jeff Turner <je...@apache.org> on 2003/04/19 13:36:26 UTC

document-v12

Hi,

A while back Steven made some changes to document-v11.mod:

+  20030320 Make @href required for link elements. (SN)
+  20030320 Allow paragraphs (p|source|note|warning|fixme) inside li. (SN)
+  20030320 Allow paragraphs (p|source|note|warning|fixme) and lists (ol|ul|dl) inside dd. (SN)
+  20030320 Allow links (link|jump|fork) and inline elements (br|img|icon|acronym) inside title. (SN)

There was an unresolved versioning issue here, that I'd like to now
address.

I propose we:

 - Revert above changes to document-v11.mod
 - Declare document-v11 finished
 - Start document-v12 (new public id, document-v12.{dtd,mod} files), and
   apply above changes to document-v12.mod.
 - Convert all Forrest's doco to the doc-v12 public id


As for future DTD evolution, I think we should keep two branches:

 - Use 1.x for (mainly) backwards-compatible changes.  I say "mainly",
   because there's some bug fixes like disallowing <ul><ul> that I think
   belong in the 1.x series.
 - Start a 2.x branch for large changes that bring us closer to XHTML 2.
   Most recent mail listing the proposed changes is
   http://marc.theaimsgroup.com/?l=forrest-dev&m=104826206624343&w=2
   discussed at:
   http://marc.theaimsgroup.com/?l=forrest-dev&m=104852236506680&w=2


Then once doc-v12 has settled, it would be a good idea to do a 0.5
release, before any major menu/metadata/tabs work happens.  There's quite
a decent number of changes since 0.4, and things seem fairly stable.

Thoughts?


--Jeff

Re: document-v12

Posted by Jeff Turner <je...@apache.org>.
Hi,

I've finished adding document-v12, which removes most of the annoying
structural limitations in document-v11 and makes the content model more
HTML-like.  The changes are listed on the sample page:

http://xml.apache.org/forrest/document-v12.html

There are new DTDs for document-v12, faq-v12, howto-v12, changes-v12 and
todo-v12, which all use document-v12.mod.  I have converted the Forrest
docs and seed site to use these.

A bit of technical background..

Previously, our DTD defined 'inline' and 'block' entities, and elements
like li, tr and dd used 'inline' with ad-hoc extensions (most recently,
Steven's DTD commit).  Examining the xhtml1-strict DTD (which is very
clean and readable), I found they define a third type, 'flow', which
merges inline and block:

<!ENTITY % flow "%content.mix;|%blocks;">

So I copied the xhtml DTD, and now 'flow' is used in document-v12 by dd,
li, td and th.  This fixes most issues mentioned in
etc/DTD_DEFICIENCIES.txt, as well as Stephan Schlierf's request for lists
(ol|ul|dl) inside <td>.

The DTD changelog summarizes the changes since document-v11 as:

[Version 1.2]
  20030320 Make @href required for link elements. (SNS)
  20030320 Allow links (link|jump|fork) and inline elements (br|img|icon|acronym) inside title. (SNS)
  20030419 Allow inline content (strong|em|code|sub|sup|br|img|icon|acronym|link|jump|fork) in strong and em. (JT)
  20030419 Allow paragraphs (p|source|note|warning|fixme), table and figure|anchor inside li. (JT)
  20030419 Allow paragraphs (p|source|note|warning|fixme), lists (ol|ul|dl), table, figure|anchor inside dd. (JT)
  20030419 Allow paragraphs (p|source|note|warning|fixme), lists (ol|ul|dl), table, figure|anchor inside tables (td|dh). (JT)


The only change I didn't make was fix the bug that allows <li><li>, which
is invalid HTML.  I left this because:
 - having 100% backwards-compatibility in the 1.x DTD series is a very
   valuable thing, even if only from a marketing POV.
 - we can render this bug harmless with some stylesheet cleverness.

So apart from the possibility of fixing @title in the FAQ and Howto DTDs,
I think DTDs are in order for a 0.5 release.


--Jeff

Re: document-v12

Posted by Steven Noels <st...@outerthought.org>.
On 19/04/2003 13:36 Jeff Turner wrote:

> Hi,
> 
> A while back Steven made some changes to document-v11.mod:
> 
> +  20030320 Make @href required for link elements. (SN)
> +  20030320 Allow paragraphs (p|source|note|warning|fixme) inside li. (SN)
> +  20030320 Allow paragraphs (p|source|note|warning|fixme) and lists (ol|ul|dl) inside dd. (SN)
> +  20030320 Allow links (link|jump|fork) and inline elements (br|img|icon|acronym) inside title. (SN)
> 
> There was an unresolved versioning issue here, that I'd like to now
> address.
> 
> I propose we:
> 
>  - Revert above changes to document-v11.mod
>  - Declare document-v11 finished
>  - Start document-v12 (new public id, document-v12.{dtd,mod} files), and
>    apply above changes to document-v12.mod.
>  - Convert all Forrest's doco to the doc-v12 public id

+1

> As for future DTD evolution, I think we should keep two branches:
> 
>  - Use 1.x for (mainly) backwards-compatible changes.  I say "mainly",
>    because there's some bug fixes like disallowing <ul><ul> that I think
>    belong in the 1.x series.

+1

>  - Start a 2.x branch for large changes that bring us closer to XHTML 2.
>    Most recent mail listing the proposed changes is
>    http://marc.theaimsgroup.com/?l=forrest-dev&m=104826206624343&w=2
>    discussed at:
>    http://marc.theaimsgroup.com/?l=forrest-dev&m=104852236506680&w=2

+1

> Then once doc-v12 has settled, it would be a good idea to do a 0.5
> release, before any major menu/metadata/tabs work happens.  There's quite
> a decent number of changes since 0.4, and things seem fairly stable.

+1

> Thoughts?

+1 :-)

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org