[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] outputclass on map elements
Hi, France:
Your concern makes sense -- it creates a problem if
writers use the outputclass attribute for presentation, as in:
<p
outputclass="Palatino12pt">...</p>
It is also possible, however,
to use the outputclass attribute for informal semantic extension, as
in:
<p outputclass="background">...</p>
Making such
informal extension available to adopters seems pragmatic (though, in retrospect,
the attribute name would be better if it prompted this approach).
In
passing, that's a good way to mock up and evaluate a potential specialization -
by creating an instance in the base type with outputclass attributes indicating
the proposed specialized elements.
Hoping that's
useful,
Erik Hennum
ehennum@us.ibm.com
"France Baril"
<France.Baril@ixiasoft.com>
06/13/2006 08:53 AM |
|
Hi, Paul:
To clarify, the outputclass attribute is
available on the topic elements in DITA 1.0. The attribute should have been
provided on the DITA map elements as well -- hence the bug fix.
The
outputclass attribute really fills a role similar to the DocBook role attribute.
Where the output format has a concept of class or role (as with HTML), the
outputclass can be copied into the output, but its primary purpose is to provide
informal semantic extension rather than stuff names into the HTML class
attribute.
The attribute could have a better name.
Erik
Hennum
ehennum@us.ibm.com
"Grosso, Paul"
<pgrosso@ptc.com>
06/07/2006 07:24 AM |
|
Hi, Esteemed Technical Committee:
The 1.1 bug list
(http://wiki.oasis-open.org/dita/Bug_fixes_for_DITA_1%2e1#preview) has an item that never received final disposition -- adding the
outputclass attribute to the map elements (<map>, <topicref>,
<navref>, <anchor>, and <reltable>):
http://lists.oasis-open.org/archives/dita/200602/msg00082.html
To recap, the outputclass attribute assigns an informal role to
an element. As such, outputclass is quite useful for extending the semantic
without formal specialization. For instance, you can use outputclass to mock up
a specialization in the base document type or to create handles for custom
processing. Typical output processing for HTML copies the outputclass into the
class attribute so users can create custom CSS styling.
Currently,
outputclass is only available on topic elements and not on map elements. As a
result, you can't easily mock up a map specialization or provide handles for
custom map processing.
The main implication of map outputclass for the
base output processing would seem to be to collect the outputclass values for
the topicref and provide them on the outermost wrapper of the HTML content for
the topic. The latter enhancement would let users style a topic in CSS based on
the role played by a topic within a map.
The outputclass attribute is
close to being a universal attribute -- it applies to a similarly large list of
elements and merits similar treatment. I'd like to request that we finalize this
bug fix at the next meeting.
Thanks,
Erik
Hennum
ehennum@us.ibm.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]