I reworked the text in question a bit while I was messing with explaining
the color-coding better yesterday. All of those changes are now on the live
site, so please review the new text to see if you think further changes are
required.
I notice the language on the "FOP Standards Compliance" page refers primarily to "conformance" instead of "compliance" as I would've expected. In fact, a search on the page lists two (2) instances of the word Compliance: In the Navigation menu on the side, and the page title at the top of the page (it's also in the <TITLE> element). I'm not sure whether or not this is incorrect, but it's something to consider. I remember a discussion some time ago about compliance and that: either there is compliance or there's not. Personally, I like the term Compliance as the title and topic of this page (I think it makes more sense as a Navigation menu item than conformance, as I believe "compliance" is more widely used when describing meeting the requirements of w3 specs). My vote, would be to use the term compliance wherever possible. In any case, it's something to consider.
Here're my changes to the text at the top (I'll leave the preference for the term conformance as it stands):
====
One of FOP's design goals is conformance to the W3C XSL-FO 1.0 standard, which specifies three levels of "conformance": basic, extended, and complete. Although FOP does not currently conform to any of these levels, it is nevertheless a useful work-in-progress for many applications (and is currently in use in production by many organizations worldwide!). The information presented here demonstrates FOP's progress toward the goal of conformance, which progress consists of implementation of specific objects and properties in the standard. The information presented is useful not only to the developers as a sort of "to do" list, but also for setting proper expectations for users and potential users.
NOTE (or one of those nifty WARNING boxes): If, in the use of FOP, you find it does not behave as you expect, check this page to ensure that FOP "should" behave as you'd expect, or whether the feature/property in question has been implemented.
In the tables below, "yes" indicates conformance, "no" indicates a lack of conformance, "partial" indicates partial conformance, and "na" indicates that the item is "not applicable" to FOP. The color-coding indicates conformance at a specific conformance level, with blue indicating conformance, red indicating non-conformance, and gray indicating partial conformance. So, for example, a given item may be blue either because it is not required at the conformance level indicated, or because FOP supports this feature, or both.
====
On the subject of color coding, I like the idea of switching to the traffic light system to help indicate conformance/compliance. These colors have been engrained in us all to know that yellow means "caution".
---
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
