You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Steven Noels <st...@outerthought.org> on 2003/03/24 17:12:02 UTC
Preparing DTD changes (was: Re: Steven's Terrible Commit (Re: cvs
commit: xml-forrest/src/resources/schema/dtd document-v11.mod))
On 21/03/2003 16:53 Nicola Ken Barozzi wrote:
> Here's the list I'd like to see Steven commit ;-)
Let me see...
> -------------------------------------------
> -> means make the change
> nothing means it's already the same
> X means let's change later
> ? means ok id done now or later
> -------------------------------------------
>
> '-----------------'---------------------------------------'
> | XHTML2 WD2 | current document11 DTD |
> '-----------------'---------------------------------------'
> *XHTML Structure Module*
>
> X html document
> -> head header
Any reason?
> title title
> body body
>
>
> *XHTML Text Module*
>
> ? abbr * (requested by users via dictionary links)
OK.
> acronym acronym
> ? address * (requested by users)
> ? blockquote *
> ? cite *
4 * OK
> br (deprecated) br
> code code
> ? dfn * (requested by users via dictionary links)
> X div footer, legal (requested by skinners)
We have sections already... where should they be 'hung up'? At the
block-level (paras, lists, etc)
> em em
> X h title
Nope, please not.
> ? kbd * (needed, currently we misuse "code" instead)
OK - although I would support them both...?
> X line br
> p p
> X | fixme (with class attribute)
> X | note (with class attribute)
> X | warning (with class attribute)
What do we do here? I like these.
> -> pre source
Hm...
> ? quote *
You want quote or blockquote? How about cite?
> ? samp * (needed, currently we misuse "source" instead)
> section section
> X span * (requested by skinners)
And pass-through
> strong strong
> ? var * (needed, currently we misuse "code" instead)
OK.
> *XHTML Hypertext Module*
>
> -> a link (already decided to reduce)
> -> | jump (already decided to reduce)
> -> | fork (already decided to reduce)
> -> | anchor
Yep, will do some clean-up.
> * XHTML List Module*
>
> dl dl
> dt dt
> dd dd
> X nl * (makes multilinks possible, very cool)
> X name * (part of nl spec)
> ol ol
> ul ul
> li li
>
>
> *XHTML Linking Module*
>
> link element book.xml
>
> Metainformation Module
>
> -> meta abstract (never used)
> -> | authors
> -> | person
> -> | subtitle (never used)
> -> | type (never used)
> -> | version
> -> | notice (never used)
Please clarify (I used abtract, subtitle, and notice in some docs already).
> *XHTML Object Module*
>
> X object img
> X | icon (never used)
> X | figure (never used)
I've been using figure already, and most of us did, I assume...
> *XHTML Presentation Module*
>
> X hr *
> sub sub
> sup sup
>
> Easy to add.
Yep.
> *XHTML Tables Module*
>
> caption caption
> table table
> -> tbody *
> td td
> th th
> -> thead * (needed, currently misusing caption)
> -> tfoot * (needed, currently misusing other tags)
> tr tr
Also OK.
Other comments?
</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
Re: Preparing DTD changes (was: Re: Steven's Terrible Commit (Re:
cvs commit: xml-forrest/src/resources/schema/dtd document-v11.mod))
Posted by Steven Noels <st...@outerthought.org>.
On 24/03/2003 17:47 Nicola Ken Barozzi wrote:
>
> Steven Noels wrote, On 24/03/2003 17.12:
>
>> On 21/03/2003 16:53 Nicola Ken Barozzi wrote:
<snip type="nodding"/>
OK. I've been playing around with stuff tonight and my plan of attack
looks more or less like this:
1) update DTDs with backwards-compatible changes in HEAD this week
2) postpone backwards-incompatible changes until we have some
grammar-evolution plan:
- I would like to keep grammars stable until after the 1.0 release
- for post-1.0, I'd like to see heavy refactoring of the pipelines &
skinning system so that we have xdocs, sdocbook and xhtml2 as input
grammars, and xhtml1 or 2 as the intermediate grammar
I plan to support the backwards-compatible changes in the skins, too.
How does this sound?
</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
Re: Preparing DTD changes (was: Re: Steven's Terrible Commit (Re:
cvs commit: xml-forrest/src/resources/schema/dtd document-v11.mod))
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Steven Noels wrote, On 24/03/2003 17.12:
> On 21/03/2003 16:53 Nicola Ken Barozzi wrote:
>
> > Here's the list I'd like to see Steven commit ;-)
>
> Let me see...
>
> > -------------------------------------------
> > -> means make the change
> > nothing means it's already the same
> > X means let's change later
> > ? means ok id done now or later
> > -------------------------------------------
> >
> > '-----------------'---------------------------------------'
> > | XHTML2 WD2 | current document11 DTD |
> > '-----------------'---------------------------------------'
> > *XHTML Structure Module*
> >
> > X html document
> > -> head header
>
> Any reason?
None other than getting nearer to HTML (ie no reason to keep the
difference).
> > title title
> > body body
> >
> >
> > *XHTML Text Module*
> >
> > ? abbr * (requested by users via dictionary links)
>
> OK.
>
> > acronym acronym
> > ? address * (requested by users)
> > ? blockquote *
> > ? cite *
>
> 4 * OK
>
> > br (deprecated) br
> > code code
> > ? dfn * (requested by users via dictionary links)
> > X div footer, legal (requested by skinners)
>
> We have sections already... where should they be 'hung up'? At the
> block-level (paras, lists, etc)
The Common collection:
http://www.w3.org/TR/xhtml2/mod-text.html#sec_8.17.
> > em em
> > X h title
>
> Nope, please not.
>
> > ? kbd * (needed, currently we misuse "code" instead)
>
> OK - although I would support them both...?
Of course, code is already included in the previous points.
> > X line br
> > p p
> > X | fixme (with class attribute)
> > X | note (with class attribute)
> > X | warning (with class attribute)
>
> What do we do here? I like these.
X == keep as-is for now.
> > -> pre source
>
> Hm...
We are misusing source as pre.
> > ? quote *
>
> You want quote or blockquote? How about cite?
? = dunno. quote is what is in XHTML2 draft.
> > ? samp * (needed, currently we misuse "source" instead)
> > section section
> > X span * (requested by skinners)
>
> And pass-through
X = let's defer.
I'd like to see both div and span with passthrough in the second pass.
> > strong strong
> > ? var * (needed, currently we misuse "code" instead)
>
> OK.
>
> > *XHTML Hypertext Module*
> >
> > -> a link (already decided to reduce)
> > -> | jump (already decided to reduce)
> > -> | fork (already decided to reduce)
> > -> | anchor
>
> Yep, will do some clean-up.
>
> > * XHTML List Module*
> >
> > dl dl
> > dt dt
> > dd dd
> > X nl * (makes multilinks possible, very cool)
> > X name * (part of nl spec)
> > ol ol
> > ul ul
> > li li
> >
> >
> > *XHTML Linking Module*
> >
> > link element book.xml
> >
> > Metainformation Module
> >
> > -> meta abstract (never used)
> > -> | authors
> > -> | person
> > -> | subtitle (never used)
> > -> | type (never used)
> > -> | version
> > -> | notice (never used)
>
> Please clarify (I used abtract, subtitle, and notice in some docs already).
http://www.w3.org/TR/xhtml2/mod-meta.html#s_metamodule
Example:
"
<html ... profile="http://www.acme.com/profiles/core">
<head>
<title>How to complete Memorandum cover sheets</title>
<meta name="author">John Doe</meta>
<meta name="copyright">© 1997 Acme Corp.</meta>
<meta name="keywords">corporate,guidelines,cataloging</meta>
<meta name="date">1994-11-06T08:49:37+00:00</meta>
</head>
"
> > *XHTML Object Module*
> >
> > X object img
> > X | icon (never used)
> > X | figure (never used)
>
> I've been using figure already, and most of us did, I assume...
X == keep as-is for now. We could maybe zap 'icon' though now that I
think of it.
> > *XHTML Presentation Module*
> >
> > X hr *
> > sub sub
> > sup sup
> >
> > Easy to add.
>
> Yep.
Note: easy to add later if we will need it. X = not for now.
> > *XHTML Tables Module*
> >
> > caption caption
> > table table
> > -> tbody *
> > td td
> > th th
> > -> thead * (needed, currently misusing caption)
> > -> tfoot * (needed, currently misusing other tags)
> > tr tr
>
> Also OK.
>
> Other comments?
>
> </Steven>
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Any body else getting a message like this?
Posted by Jeff Turner <je...@apache.org>.
On Tue, Mar 25, 2003 at 05:30:38PM +0300, Konstantin Piroumian wrote:
> From: "Jeff Turner" <je...@apache.org>
> > On Tue, Mar 25, 2003 at 09:01:51AM -0500, Berin Loritsch wrote:
> > > Berin Loritsch wrote:
> > > >Jeff Turner wrote:
> > > >
> ...
> > > >
> > > >:/ I am on Winblows. Does xmllint exist for Cygwin?
> > >
> > > Ok, xmllint DOES exist for Cygwin.
> >
> > That's good. Here's some tips on using xmllint to validate Forrest XML:
> >
> >
> http://xml.apache.org/forrest/validation.html#Case+study%3A+setting+up+xmlli
> nt
>
> It'd be also fine to explain what the vim settings mean and how to use them.
> We - Windows/Cygwin and eventual Linux users - would be very happy. ;)
au FileType xml set makeprg=xmllint\ --noout\ --valid\ --catalogs\ %
au FileType xml set efm=%A%f:%l:\ %.%#error:\ %m,%-Z%p^,%-C%.%#
Sets up two "autocommands" that trigger when an XML file is loaded.
First the 'makeprg' is set to the xmllint command, so typing ':make'
triggers xmllint, instead of GNU make. Then in order to jump to errors,
we set the errorformat (efm) to some cryptic string described by ':help
errorformat'.
Pretty obvious really.
:)
--Jeff
>
> --
> Konstantin
>
Re: Any body else getting a message like this?
Posted by Konstantin Piroumian <kp...@apache.org>.
From: "Jeff Turner" <je...@apache.org>
> On Tue, Mar 25, 2003 at 09:01:51AM -0500, Berin Loritsch wrote:
> > Berin Loritsch wrote:
> > >Jeff Turner wrote:
> > >
...
> > >
> > >:/ I am on Winblows. Does xmllint exist for Cygwin?
> >
> > Ok, xmllint DOES exist for Cygwin.
>
> That's good. Here's some tips on using xmllint to validate Forrest XML:
>
>
http://xml.apache.org/forrest/validation.html#Case+study%3A+setting+up+xmlli
nt
It'd be also fine to explain what the vim settings mean and how to use them.
We - Windows/Cygwin and eventual Linux users - would be very happy. ;)
--
Konstantin
>
> --Jeff
>
> > The problem was an invisible character that my text editors ignored.
> > It is Easily removed when you know where the problem is.
> >
> > Thanks for the xmllint hint!
> >
> >
>
>
Re: Any body else getting a message like this?
Posted by Jeff Turner <je...@apache.org>.
On Tue, Mar 25, 2003 at 09:01:51AM -0500, Berin Loritsch wrote:
> Berin Loritsch wrote:
> >Jeff Turner wrote:
> >
> >>
> >>Try running 'forrest -v validate', which prints out the file names as it
> >>goes. Perhaps you have an 8859-1 8-bit character (é or something) in
> >>your XML. If you're on Unix, try installing libxml2, which comes with a
> >>marvellous utility 'xmllint'. Its error messages are *much* better than
> >>Xerces.
> >
> >
> >:/ I am on Winblows. Does xmllint exist for Cygwin?
>
> Ok, xmllint DOES exist for Cygwin.
That's good. Here's some tips on using xmllint to validate Forrest XML:
http://xml.apache.org/forrest/validation.html#Case+study%3A+setting+up+xmllint
--Jeff
> The problem was an invisible character that my text editors ignored.
> It is Easily removed when you know where the problem is.
>
> Thanks for the xmllint hint!
>
>
Re: Any body else getting a message like this?
Posted by Berin Loritsch <bl...@apache.org>.
Berin Loritsch wrote:
> Jeff Turner wrote:
>
>>
>> Try running 'forrest -v validate', which prints out the file names as it
>> goes. Perhaps you have an 8859-1 8-bit character (é or something) in
>> your XML. If you're on Unix, try installing libxml2, which comes with a
>> marvellous utility 'xmllint'. Its error messages are *much* better than
>> Xerces.
>
>
> :/ I am on Winblows. Does xmllint exist for Cygwin?
Ok, xmllint DOES exist for Cygwin.
The problem was an invisible character that my text editors ignored.
It is Easily removed when you know where the problem is.
Thanks for the xmllint hint!
Re: Any body else getting a message like this?
Posted by Berin Loritsch <bl...@apache.org>.
Jeff Turner wrote:
>
> Try running 'forrest -v validate', which prints out the file names as it
> goes. Perhaps you have an 8859-1 8-bit character (é or something) in
> your XML. If you're on Unix, try installing libxml2, which comes with a
> marvellous utility 'xmllint'. Its error messages are *much* better than
> Xerces.
:/ I am on Winblows. Does xmllint exist for Cygwin?
The results (I am no closer):
validate-xdocs:
Using SAX2 reader org.apache.xerces.parsers.SAXParser
Validating index.xml...
Validating useage.xml...
Validating index.xml...
Validating faq.xml...
Validating features.xml...
Validating index.xml...
Validating index.xml...
Validating tabs.xml...
8 file(s) have been successfully validated.
...validated xdocs
validate-skinconf:
...validated skinconf
validate-sitemap:
...validated sitemap
validate-skins-stylesheets:
Fatal error: exception "java.io.UTFDataFormatException" thrown: Invalid
byte 1 o
f 1-byte UTF-8 sequence.
BUILD FAILED
file://D:/projects/xml-forrest/build/dist/shbat/forrest.build.xml:829:
Validatio
n failed, messages should have been provided.
at com.thaiopensource.relaxng.util.JingTask.execute(Unknown Source)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1331)
at org.apache.tools.ant.Project.executeTargets(Project.java:1275)
at org.apache.tools.ant.Main.runBuild(Main.java:614)
at org.apache.tools.ant.Main.start(Main.java:197)
at org.apache.tools.ant.Main.main(Main.java:235)
Total time: 16 seconds
Re: Any body else getting a message like this?
Posted by Jeff Turner <je...@apache.org>.
On Mon, Mar 24, 2003 at 01:23:35PM -0500, Berin Loritsch wrote:
> Using skin d-haven
> ____________________________________
> <snip/>
>
> validate-skins-stylesheets:
> Fatal error: exception "java.io.UTFDataFormatException" thrown: Invalid
> byte 1 of 1-byte UTF-8 sequence.
>
> BUILD FAILED
> file://D:/projects/xml-forrest/build/dist/shbat/forrest.build.xml:829:
> Validation failed, messages should have been provided.
>
> How do I know where this is happening? To my knowledge everything
> is in the proper encoding.
Try running 'forrest -v validate', which prints out the file names as it
goes. Perhaps you have an 8859-1 8-bit character (é or something) in
your XML. If you're on Unix, try installing libxml2, which comes with a
marvellous utility 'xmllint'. Its error messages are *much* better than
Xerces.
--Jeff
Any body else getting a message like this?
Posted by Berin Loritsch <bl...@apache.org>.
Using skin d-haven
____________________________________
<snip/>
validate-skins-stylesheets:
Fatal error: exception "java.io.UTFDataFormatException" thrown: Invalid
byte 1 of 1-byte UTF-8 sequence.
BUILD FAILED
file://D:/projects/xml-forrest/build/dist/shbat/forrest.build.xml:829:
Validation failed, messages should have been provided.
How do I know where this is happening? To my knowledge everything
is in the proper encoding.