Hi,
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-
list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of Howard Stearns
Sent: Monday, July 21, 2003 6:02 PM
I didn't follow how this would work any number of levels deep.
It's ok if we only have us-gaap-ci-2html.xsl doing the basic
transformations, and a CSS stylesheet based on @class to handle things
that need to be different. Very cute.
But in fact ci is part of us-gaap which is part of the basic financial
reporting taxonomy. Acme Corp may have many operating levels
(subsidiaries, divisions, etc.). There may be more industry specific
levels between us-gaap-ci and individual companies like Acme. A
stylesheet any of these levels should be able to define behavior that
applies to all the more specific levels.
I'm not very familiar with real CSS, and maybe there's a way to inherit
behavior. But I would guess the inheritance behavior would have to be
generated somehow. How would CSS know which elements (which @classes)
inherit from each other?
div .class1 .class2 .classN {}
Or, perhaps a simple example (not content, per se):
#nav .title, #nav c\:title {
font-weight:bold;
padding:0px;
margin:0px 0px 5px 0px;
font-size : 95%;
}
Handles:
<div id="nav">
<div class="title">My Nav title</div>
</div>
Or:
<div id="nav">
<c:title>My Nav title</c:title>
</div>
FWIW, I believe XSLers (going to XHTML or HTML) should have a good
understanding of how to separate concerns regarding what are the bones
(XHTML) and what is the skin (CSS). XSL, thought about this way, is the the
&deity; :)
Sidenote related to the table-modulus thread: tables not used for tabular
data are &evil;
Besides, I actually want the .xsl to be generating results for
conformance testing. It won't necessarilly be XHTML output subject to CSS.
That is why I did not reply to your first post. I didn't think you were
going through all this just to get (X)HTML.
Best,
-Rob
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list