[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]


  • From: Matthew Gertner <matthewg@p...>
  • To: "xml-dev@i..." <xml-dev@i...>
  • Date: Tue, 24 Jun 1997 17:38:46 +0200

> [Jonathan Robie]
> >
> >Is there really an advantage to defining it in IDL first? The IDL could 
> >created after the specification is finished in Java, and the Java-based
> >specification is probably easier to create, understand, and test. I 
> >making things language independent, but at this stage, I'm leery of 
> >complexity that doesn't add any new conceptual power.
> Hmmm. IDL == Language independent spec of an API....might this be better
> approached
> as an XML application? I.e. a DTD for the XML API spec. A doc conforming 
> that spec.
> that can be down-translated to Java, C++, Python  and (gasp) IDL!
> APIs are stuctured docs. Let's practice what we are preaching and capture 
> API in XML. Unless there are compelling reasons why this does not make 
> Just thinking out loud and looking forward to a discussion on the issue.
> Sean

If I may be so bold, this sounds like a great idea to me. Producing an API 
in Java is a valid approach and is more than defensible considering the 
current Internet climate. However, there is also an argument to be made for 
a language-independent approach (as evidenced by the discussion in this 
thread). If this approach is to be favored, it seems to me to make far more 
sense to develop a generalized DTD for API specifications and make the 
specification itself in XML. This would have the following advantages:

1) Make a truly language-independent spec which conforms to the XML 
philosophy. (I am not going to talk about the "spirit of XML". :-)
2) Produce a reusable DTD which would have significant value in its own 
3) Provide the perfect basis for generating documentation directly from the 
API specification.
4) Ensure that every "user" has the necessary expertise to understand the 
formulation of the spec. I am not sure how many people really master IDL. 
Presumably anyone using XAPI will be able to read and understand XML.
5) Provide a demonstration to the outside world as to how XML can be used 
to facilitate language/application independence and information reuse.

It couldn't be that hard to write a DSSSL app to produce a concrete 
language implementation from the XML-based spec, right?



Matthew Gertner
Project Manager/Architect, Internet/Document Management
POET Software GmbH

Tel: +49 (40) 609 90254
Fax: +49 (40) 609 90115
E-mail: matthewg@p...

xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@i... the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa@i...)


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.