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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

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


Subject: Re: [dita-comment] Consider adding an attribute "numeration" to "ol"'s


Hi Michael,

Very nice analysis. The original use case reported to us from which this idea started:

http://www.oxygenxml.com/forum/post30713.html#p30703

was for numbering OL's inside a figure with letters probably because the image above had letters and not numbers drawn on various regions from it. Possibly this could have also been solved with an XSLT customization which would have numbered with letters all OL
s inside FIG's.

On the other side, I prefer as much flexibility as possible built into the vocabulary and allow others to add constraints using Schematron or a DITA specialization which removes certain elements which should not be used by the writer.

Docbook for example also allows a number of processing instructions in the XML which can be used to control output styling:

http://www.sagehill.net/docbookxsl/ProcessingInstructions.html

For example from what I remember they have a processing instruction which instructs the PDF processor to break the page when it is encountered. But such constructs are probably not specified in the standard but just sometimes convenient ways for someone to control the output styling from the XML.

Maybe indeed instead of allowing numeration as an attribute on OLs by modifying the specification the DITA OT stylesheets could support by default looking for certain specific @outputclass attribute values on certain elements and provide some styling based on them.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 9/2/2014 5:12 PM, Michael Priestley wrote:
It depends on whether you, as a publishing organization, want this to be
something that is controlled by the author on a list-by-list basis, or
something that is controlled at publishing time based on the type of list.

For example, in a training course, do you really want a mix of numbering
schemes depending on the preference of the original author? Should it be
ok for tutorials to switch from alpha to numeric to Roman from one
exercise to the next?

If you are in an organization that has a "house style" that includes
guidance on numbering, why wouldn't you move that control into the
output rules?

You might also want to change your numbering choices based on output
device. For example, roman might have been appropriate for your PDF and
print deliverables, but is it still appropriate for mobile display,
where horizontal space is at a premium?

Michael Priestley, Senior Technical Staff Member (STSM)
Enterprise Content Technology Strategist
mpriestl@ca.ibm.com
http://dita.xml.org/blog/michael-priestley



From: "Julio Vazquez" <jvazquez@vasont.com>
To: "'Radu Coravu'" <radu_coravu@sync.ro>,
<dita-comment@lists.oasis-open.org>,
Date: 09/02/2014 09:41 AM
Subject: RE: [dita-comment] Consider adding an attribute "numeration" to
"ol"'s
------------------------------------------------------------------------



If I can throw in my humble opinion, controlling the type of numbering is
not as much presentation as the style of the numbering. It makes sense to
specify whether Arabic, roman or alphabetic numbers be used in an ordered
list for the levels of an ol with a default being roman.

Julio J. Vazquez
Senior Content Analyst
Vasont Systems
+1 717-793-3895
A TransPerfect Company

www.vasont.com
The information in this email is confidential and intended for those to whom
it is addressed.


-----Original Message-----
From: Radu Coravu [mailto:radu_coravu@sync.ro]
Sent: Tuesday, September 02, 2014 9:33 AM
To: dita-comment@lists.oasis-open.org
Subject: Re: [dita-comment] Consider adding an attribute "numeration" to
"ol"'s

Hi Kristen,

Thanks for discussing this. A couple of our users wanted this and so I
considered that if Docbook does it, why shouldn't we do it as well :)

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com <http://www.oxygenxml.com/>


On 9/2/2014 3:27 PM, Kristen James Eberlein wrote:
 > Hi, Radu.
 >
 > The DITA TC discussed your e-mail at the TC meeting last week.
 >
 > The TC was quite split on this idea, with some people thinking that it
 > would be a useful addition to the specification, and others strongly
 > stating that it was inappropriate and something that should be handled
 > as formatting.
 >
 > We will add this to list of items to consider for DITA 2.0.
 >
 > Best,
 > Kris
 >
 > Kristen James Eberlein
 > Chair, OASIS DITA Technical Committee
 > Principal consultant, Eberlein Consulting www.eberleinconsulting.com
 > +1 919 682-2290; kriseberlein (skype)
 >
 > On 6/25/2014 3:50 AM, Radu Coravu wrote:
 >> Hi,
 >>
 >> In Docbook ordered lists <orderedlist> elements have a "numeration"
 >> attribute which can be set to "arabic", "loweralpha", etc. This helps
 >> users better control the numbering in the output.
 >> Right now for DITA you need to make XSLT customizations based on the
 >> "outputclass" attribute in order to control in the output the
 >> numeration of an ordered list.
 >>
 >> Regards,
 >> Radu
 >>
 >> Radu Coravu
 >> <oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
 >> http://www.oxygenxml.com <http://www.oxygenxml.com/>
 >>
 >
 >



--
This publicly archived list offers a means to provide input to the
OASIS Darwin Information Typing Architecture (DITA) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: dita-comment-subscribe@lists.oasis-open.org
Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/dita-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita
Join OASIS: http://www.oasis-open.org/join/



--
This publicly archived list offers a means to provide input to the
OASIS Darwin Information Typing Architecture (DITA) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: dita-comment-subscribe@lists.oasis-open.org
Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/dita-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita
Join OASIS: http://www.oasis-open.org/join/






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