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

Re: XML API specification

• From: Peter Newcomb <peter@t...>
• To: xml-dev@i...
• Date: Sat, 1 Mar 1997 13:44:18 -0500

> References: <v03007803af3cbf484983@[128.148.19.149]>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Date: Fri, 28 Feb 1997 13:50:22 -0500
> From: dgd@c... (David Durand)
> Sender: owner-xml-dev@i...
> Precedence: bulk
> Reply-To: dgd@c... (David Durand)
> 
> At 11:53 AM -0600 2/28/97, Len Bullard wrote:
> >David Durand wrote:
> >>
> >> I see XML-groves and XML-API as parallel and needing to be in synch. I
> >> don't see either as having to depend on the other, though, and frankly,
> >> given the relative penetration of groves and Java into the "global
> >> developer consciousness", I don't see groves as that high a priority.
> >
> >If relative penetration is important, spec it in COBOL or C.
> >
> >This kind of argument went on in VRML and was wisely rejected.
> >The commitment to a CORBA IDL is a commitment to a syntax for the spec
> >and not a lot else.
> 
> If Gavin's information is correct (and I assume it to be so) this is false.
> IDL means that we get language-specific bindings for several languages
> including Java and C++, simply by applyiing an automated tool. So there are
> concrete technical advantages to using IDL, though we must apply those
> tools for the programmers, so that I don't have to find an IDL tool to use
> XML with my Java codebase.

Grove schemas (property sets) can also be automatically
translated/compiled to provide interface declarations in any language.
We do this at TechnoTeacher to create documentation-compatible
interfaces to groves stored in different ODBMSs, as well as to be able
to provide access to those groves from different languages and
environments.  IDL, Java, and C++ can all be generated easily from the
same property set.

It is not necessary that developers using these APIs (in IDL, Java,
C++, etc.) know about groves or property sets.  However, if there is
one canonical form of the API (the property set), a developer that
learned his way around the API in C++ will not be confused if he is
subsequently required to use the API in Java, Scheme, SQL, etc.

-peter

--
Peter Newcomb                           TechnoTeacher, Inc.
233 Spruce Avenue                       P.O. Box 23795
Rochester, NY 14611-4041 USA            Rochester, New York 14692-3795 USA
+1 716 464 8696 (home)                  +1 716 464 8696 (direct)
+1 716 755 8698 (cell)                  +1 716 271 0796 (main)
+1 716 529 4304 (fax)                   +1 716 271 0129 (fax)
peter@p...       peter@t...
http://www.petes-house.rochester.ny.us  http://www.techno.com

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...)

• Prev by Date: Re: Simple approaches to XML implementation
• Next by Date: MIME
• Previous by thread: Re: XML API specification
• Next by thread: Re: XML API specification
• Index(es):
  • Date
  • Thread