I think what the original poster wants is not to display attributes and their values, but to suppress elements based on attributes and values. This should be possible with CSS, but to be generally useful, XXE would have to have allow you to turn a subset of the CSS on and off and refresh the document.
With profiling in docbook, you could have this in your document: <para vendor="wooga">Blah de blah</para> And then have that para removed or not removed (depending on what params you pass the xsl) during processing. For example, if you process the document passing in the param profile.vendor=foobar, then <para vendor="wooga">...</para> would be suppressed. I see that CSS2 lets you select elements based on attribute values and that these work in XXE: http://www.w3.org/TR/REC-CSS2/selector.html So if you wanted to see your document without <para vendor="wooga">Blah de blah</para>, you would need the following in your XXE css for docbook: *[vendor='wooga']{display:none} or better yet, if you have the rule *[foo~="wooga"]{display:none} would let you have a list as the value for the attribute: <para vendor="foobar wooga baz">Blah de blah</para>. The docbook profiling xsls let you have a list of values and to specify the separator with the profile.separator param. So I believe the feature request for XXE would be to allow the user to toggle css subsets off and on and to refresh the display of the document. Hope that helps, David > -----Original Message----- > From: xmleditor-support-admin at pixware.fr > [mailto:xmleditor-support-admin at pixware.fr]On Behalf Of Hussein Shafie > Sent: Tuesday, March 09, 2004 5:21 AM > To: Damien Fitzpatrick > Cc: xmleditor-support at xmlmind.com > Subject: Re: [XXE] Support for profiling > > > Damien Fitzpatrick wrote: > > By "profiling attributes" I am referring to those > attributes that you > > normally use to profile DocBook documents. There is an > article on this at > > SourceForge: > > > http://docbook.sourceforge.net/release/xsl/current/doc/tools/p rofiling.html > > For example, in our documentation, we use the attribute "vendor" to specify > which product we are documenting and then the attribute "arch" to specify > what platform we are referring to. We then pass the document through an > XSLT in our build process which ensures, via profiling, that only the > relevant documentation is included for a particular product and platform > combination. There are several other attributes which are commonly used for > profiling, including "os", "conformance" and "userlevel". Thank you for the reference, I'll read Jirka Kosek's article. XXE can render any attribute visually, suffice to specify this in the CSS style sheet (colors, fonts, generated content such as text and icons, etc). We cannot modify the bundled DocBook CSS style sheet to support profiling attributes because we don't use these attributes ourselves, here at XMLmind, and therefore we'll probably come up with something dumb and useless for you. This means that you'll need to that yourself, to your needs and taste. -- XMLmind XML Editor Support List xmleditor-support at xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
