W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2004

JSA's comments on XSL

From: Paul Grosso <pgrosso@arbortext.com>
Date: Tue, 19 Oct 2004 16:44:05 -0400
Message-ID: <F13E1BF26B19BA40AF3C0DE7D4DA0C03010559B2@ati-mail01.arbortext.local>
To: <komachi@y-adagio.com>, <xsl-editors@w3.org>

Komachi-san,

Thank you for your comment on XSL recorded at
http://lists.w3.org/Archives/Public/xsl-editors/2004JanMar/0011
about extensions to XSL.

Regarding document meta data (document-info), one can use namespaced
elements--perhaps even those from Dublin Core--to give document meta
data, most likely inserting them into fo:declarations (see 6.4.3). We
plan no further work in this area in 1.1 because the mechanism is
already there, and we don't want to get into standardizing meta-data.

We have added Bookmarks to XSL 1.1. As far as outline-order, the
bookmark order in our XSL 1.1 fo:bookmark feature is determinable by the
XSLT code.

The XSL FO SG has decided not to add footnote-position and
suppress-duplicate-footnote extensions to XSL 1.1, but to record them as
possible post 1.1 features.

We have added to XSL 1.1 a change bar feature that covers the revision
bar requirement.

The XSL FO SG has decided not to add a column rule feature to XSL 1.1,
but to record it as a possible post 1.1 feature.

Background color/image on simple-page-master has been determined to be
post 1.1 potential feature.

physical-page-number aka ordinal-page-number (but perhaps by a different
name) has been determined to be post 1.1 potential feature. We would
probably address this requirement by adding a property to page-number
and page-number-citation.

The requirement for suppress-duplicate-page-numbers is addressed by our
XSL 1.1 indexing feature.

Text treatment a la CSS3 text module is a potential post 1.1 feature.

Allowing a list-item-label position of inside/outside is a potential
post 1.1 feature.

The way to affect relative URIs would be by use/incorporation of
xml:base (which would presumably affect all attribute of typ
<uri-specification>). The actual request is to affect the
external-destination of fo:basic-link, but we don't think this is really
what would be wanted. ACTION to Paul: Ask what is really wanted.

Incorporation of xml:base into XSL would presumably affect all
attributes of type <uri-specification>. The actual request is to affect
the external-destination of fo:basic-link, but use of xml:base would
affect the absolutization of external-destination at FO processing time,
and that does not address the use case of being able to relocate the
result of an XSL-FO run. After much discussion, the XSL FO SG decided
not to do anything about xml:base in XSL 1.1.

Regarding soft-hyphen-treatment, our experts tell us that this is a
misuse of the Unicode soft hyphen character. There should be no glyph
assigned to U+00AD as the semantics for this Unicode character is that
of a soft hyphen.

We have added clear/float values of inside/outside to XSL 1.1.

Floats of type after, in-column, mid-column are potential post-1.1
features.

The "extra" writing mode values (and more) are listed in Appendix A of
the XSL specification.

Paul Grosso
for the XSL FO SG
Received on Tuesday, 19 October 2004 20:45:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:48 UTC