Matthew Gertner wrote... 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: ------------------------ I think the concern was that this kind of overhead might hold up the API development (some were already arguing that it is too early to think about a grove API at all). I agree that Java may be too web-orientated but would rather see the API take shape in this language than not at all. Having said that, the people doing the API work should try to make it easy to get the structures/methods/documentation into other formats and should certainly minimise any language specific areas (I guess Java is a good environment in this respect?!). Alfie. 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...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format