Lists Home |
Date Index |
While true, my understanding is that non-technical influences impacted
on the decision to use W3C Schema and not even regard available
technologies such as RELAX-NG as viable candidates.
As I was not involved in the creation of the Navy XML Developer's Guide
(which is where I believe the section in question came from without
adjustment), I unfortunately cannot speak to that. In terms of
timeframes, it's possible that the version of the Navy XML Developer's
Guide that was used as a source was created before the RELAX NG OASIS TC
was started. Again, I was not involved in any way in making that
decision or any other one that you reference below - I simply
"federalized" the document and made some minor adjustments per requests
from various folks.
You could always provide feedback to the Department of Navy XML folks on
their XML Developer's Guide  if you'd like.
Booz | Allen | Hamilton
"G. Ken Holman" wrote:
> At 2003-11-25 13:49 -0500, Chiusano Joseph wrote:
> >Policy makers don't always understand the technical implications of the
> >policies they are developing.
> >I don't think that Betty was implying that the Federal XML Developer's
> >Guide is meant as policy;
> >I was the editor for the most recent version (2.0, published April
> >2002). The Federal XML Developer's Guide was created from the Department
> >of the Navy XML Developer's Guide, which was developed by folks that are
> >highly technically skilled (they are not policy-makers).
> While true, my understanding is that non-technical influences impacted on
> the decision to use W3C Schema and not even regard available technologies
> such as RELAX-NG as viable candidates.
> >The Federal XML
> >Developer's Guide was created by removing the Department of the Navy
> >references, and incorporating some adjustments due to feedback from
> >various folks (the adjustments had to do with other choices of
> >preferences, not errors in the Department of the Navy XML Developer's
> ... but without consideration for other viable technologies that may offer
> advantages over and above the use of W3C Schema.
> >I would also like to emphasize that the Federal XML Developer's Guide is
> >guidance, and not government policy.
> Regardless, it gets *treated* as policy (and they should have realized
> that, much of what the government calls guidance gets treated de facto as
> policy) and the ripple effect has been felt far and wide by such guidance
> not to consider alternatives.
> ................. Ken
> Next public European delivery: 3-day XSLT/2-day XSL-FO 2004-01-??
> Instructor-led on-site corporate, government & user group training
> for XSLT and XSL-FO world-wide: please contact us for the details
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/
> Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
> ISBN 0-13-065196-6 Definitive XSLT and XPath
> ISBN 0-13-140374-5 Definitive XSL-FO
> ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath
> ISBN 1-894049-11-X Practical Formatting Using XSL-FO
> Member of the XML Guild of Practitioners: http://XMLGuild.info
> Male Breast Cancer Awareness http://www.CraneSoftwrights.com/x/bc
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
fn:Joseph M. Chiusano