W3C home > Mailing lists > Public > public-i18n-its@w3.org > October to December 2005

Constraints and CSS

From: Lieske, Christian <christian.lieske@sap.com>
Date: Mon, 19 Dec 2005 15:08:58 +0100
Message-ID: <0F568FE519230641B5F84502E0979DD1043F9E87@dewdfe12.wdf.sap.corp>
To: <public-i18n-its@w3.org>
Dear all,

During the F2F in Abingdon, I took away the action item to come up with
some text about "external" constraint information.

Looking forward to your feedback.

Best regards,

A look at vocabularies which can work with Cascading Stylesheets (e.g.
and XML) reveals that they already have a means for capturing at least
of the constraints we have been discussing. To be specific, the CSS
"max-width" constrains box widths to a certain range.

Accordingly, with CSS we have the case were we may not want to
enforce an ITS-specific representation of max-width but rather use
what is already part of the native XML application (in the sense of
the combination of  XHTML instance and CSS). Of course, we need
to make sure that the semantics and domain (in the sense of allowed
values) of the ITS data category for constraints, and the are

Once we principally have come to the conclusion that the CSS
"max-width" covers the ITS data category, we need to take care that
the CSS representation makes sense to ITS aware applications. This
may require:

1. a mapping declaration (see our discussion at
2. possibly special locator processing

With 'locator processing' I refer to the situation in which a linking
mechanism is
used in order to associate a vocabulary with a stylesheet. Examples:

A. Via special element: <LINK REL=StyleSheet HREF="style.css"
B. Via processing instruction: <?xml-stylesheet type="text/css"
href="style.css" media="all"?>

Obviously, in these case, processing expectations related to the mapping
declaration are
different from the ones where "internal" styling (ie. either with the
"style" element or the "style"
attribute) is used: Actual values are not related in the XML instance
but rather externally.
Received on Monday, 19 December 2005 14:09:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC