OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [docbook-tc] align common elements?


No, in DocBook, a listitem must have a para child, it cannot take #PCDATA. So if we changed the tag names, DocBook would still require <ul><li><p>Item 1</p></li></ul> and just <ul><li>Item 1</li></ul> (as is expected in HTML) would still be invalid in DocBook.
 
I think that is what Steve is saying.
 
And I agree that this whole idea of aligning DocBook element names with HTML or DITA is a bad idea. The whole idea of SGML and XML is to allow arbitrarily named vocabularies.
 
paul


From: Nancy P Harrison [mailto:nancyph@us.ibm.com]
Sent: Friday, 2006 July 21 13:31
To: Steven Cogorno
Cc: docbook-tc@lists.oasis-open.org; Scott Hudson; Steven.Cogorno@Sun.COM
Subject: Re: [docbook-tc] align common elements?


Steve,

I must be missing something, but if there were an equivalence between

ul         unorderedlist
li         listitem

why wouldn't <ul><li>Item 1</li><li>Item 2</li></ul> work in DocBook?

Or are you saying that in HTML,

<ul><li>Item 1</
li><li>Item 2</li></ul>


with the split </ li> tag (with an extra space in it, no less), will work, even though it won't work in DocBook?

BTW, While DITA uses <p>, <ul> etc. for paragraph, list etc. elements, it certainly also has restrictions on them that HTML doesn't; new DITA users just have to learn them.  It doesn't seem to have been a real problem.

just a thought.

____
Nancy Harrison
IBM Rational Software
Phone: 781-676-2535
nancyph@us.ibm.com



Steven Cogorno <Steven.Cogorno@Sun.COM>
Sent by: Steven.Cogorno@Sun.COM

07/21/2006 01:49 PM

To
Scott Hudson <scott.hudson@flatironssolutions.com>
cc
docbook-tc@lists.oasis-open.org
Subject
Re: [docbook-tc] align common elements?






On Jul 21, 2006, at 10:42 AM, Scott Hudson wrote:

> That is something that may need to be worked out in the  
> interoperability forum, but I think even Norm has lamented in the  
> past about the decision to use "para" instead of "p"...
>
> I imagine some of the alignment would be more along the HTML/DITA  
> line, such as:
> para = p
> itemizedlist = ul
> orderedlist = ol
> listitem = li


Oh no -- I definitely oppose changing them to HTML names.  This gives  
people the impression that a DocBook <p> would let them do the same  
things that an HTML <p> would do.  Example:  <ul><li>Item 1</
li><li>Item 2</li></ul>  Obviously that isn't going to work.

Since the elements can't work the same way as HTML elements, what  
would be the advantage of using the same names? It wouldn't make  
interop any easier anyway because of the content model differences.

-Steve

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]