Path: utzoo!attcan!uunet!samsung!usc!orion.oac.uci.edu!ucivax!gateway
From: hrs1@cbnewsi.att.COM
Newsgroups: comp.protocols.iso.x400
Subject: Re: X.400 APIs
Summary: a unified API for telematic services
Message-ID: <1990Sep26.224525.24933@cbnewsi.att.com>
Date: 27 Sep 90 00:13:22 GMT
References: <173*eskovgaa@uvcw.UVic.ca> <175*eskovgaa@uvcw.UVic.ca>
Organization: AT&T Bell Laboratories
Lines: 17
Approved: usenet@ICS.UCI.EDU
x-attn: jns
X-Previously-To: mhsnews-usenet@ICS.UCI.EDU
ReSent-To: mhsnews@ICS.UCI.EDU

> I cannot say I am totally in agreement with the APIA and X/Open in
> the way they keep standards confidential until they have been approved, but
> it does allow you to produce a standard much faster when you do not
> have the world breathing down your neck.  In any case, I cannot
> change that - it is just the way they work.
>
CCITT Study Group VIII has started work on an API for facsimile and document
communication services.  This API will probably based on a French/German
development called COM/APPLI.  The aim is to have a common application interface
for all user-to-user document communication services.  Study Group I has
requested thsi work from SGVIII and SG VII, which is responsible for X.400
and X.500. Thus far, these folks have not yet agreed to work on a common API.
It certainly would make sense to have one API which could provide access to
fax as well as synchronous and asynchronous document communication.

Herman Silbiger
hsilbiger@ATTMAIL.COM