ren@kowande.bu.oz.au (Renato Iannella) (09/21/90)
--
I would like to find out more information about the X.400 API developed
by the X.400 Application Program Interface Association and X/Open Co.
Ltd.
When will it be available and how etc.
Also I have read(1) that Rapport Communications Inc will be publishing a
white paper on this X.400 API. How can one obtain this?
Many ThanXs,
Renato Iannella
---
(1) "Closeup on APIs for X.400, a First Look", R. Miller et al.,
DATA COMMUNICATIONS, June 21 1990, Pp 47-56.
---------------
Information & Computing Sciences Internet: ren@kowande.bu.oz.au
Bond University, AUSTRALIA, 4229 Phone: +61 75 953381rothstein@nutmeg.enet.dec.COM ("Lee Rothstein, 603-884-0039") (09/23/90)
============= >From: ren@kowande.bu.oz.au (Renato Iannella) >Newsgroups: comp.protocols.iso.x400 >Subject: X.400 APIs >Date: 21 Sep 90 01:28:22 GMT >Organization: Bond University >I would like to find out more information about the X.400 API >developed by the X.400 Application Program Interface Association >and X/Open Co. Ltd. There are three XAPIA specs: Object Management, Application API (includes UAs), and Gateway API. Gateway API includes details on interfacing Group III and Group IV fax, telex and teletex. >When will it be available and how etc. >Also I have read in: > "Closeup on APIs for X.400, a First Look", R. Miller et al., > DATA COMMUNICATIONS, June 21 1990, Pp 47-56. >that Rapport Communications Inc will be publishing a white paper >on this X.400 API. How can one obtain this? Rich Miller and Rapport are located in Silicon Valley--either 408 or 415 area code. >Many ThanXs, >Renato Iannella NETLAND ANSWERS: ================ >Information & Computing Sciences Internet: ren@kowande.bu.oz.au >Bond University, AUSTRALIA, 4229 Phone: +61 75 953381 ]From: newsbytes@clarinet.com ]Newsgroups: clari.nb.telecom ]Subject: X.400 and X/Open Announce New Open E-Mail Specifications ]Date: 13 Sep 90 05:01:01 GMT ]DALLAS, TEXAS, U.S.A., 1990 SEP 11 (NB) -- The X.400 ]Application Program Interface Association and X/Open, the ]international open systems organization, jointly announced new ]specifications for electronic messaging applications ]development. ]The new specs will let software developers write electronic mail ]applications based on international standards which can operate ]independently of operating systems. The approved specs involve ]both X.400 messaging and X.500 directory standards. The two ]organizations will jointly submit their Application Program ]Interface, or API, to the IEEE and other international bodies, ]hoping to make it a certified international standard. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ]The API specifications can be ordered from Omnicom, at 115 Park ]St. SE, Vienna, VA 22180. The phone number is 703-281-1135. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ](Dana Blankenhorn/19900910/Press Contact: David Whitten, X.400 ]API Association, 603-884-0753; Jeff Hansen, X/Open, ]415-773-5383) +---------------------------------------------------------+ | Lee Rothstein * UUCP: {purdue,ucbvax,hplabs,labrea,sun, | | pyramid,gryphon,angelo}!decwrl!nutmeg.dec.com!rothstein| | * Arpa/Domain Address: rothstein@nutmeg.enet.dec.com | +---------------------------------------------------------+
enag@ifi.uio.no (Erik Naggum) (09/25/90)
In article <173*eskovgaa@uvcw.UVic.ca>, Erik Skovgaard writes:
The second version has not yet formally been released but is
available only as an internal (and confidential) X/OPEN document.
Are you serious? Is it a _secret_ what they are going to virtually
"spring on the developers and the public"? Even CCITT and ISO are
willing to let you (me, anyhow) get draft standards and even minutes
from their meetings. Maybe I should try to look and learn and cease
to be amazed at how so-called "standards" are developed.
Thus, you should be careful which spec you implement.
How? Only thanx to this comparativly random comment from you, we get
to know there is a new version coming up, and all development based on
the older version has to be stopped, because we will not be able to
know what the next version will bring.
If this is indicative of X/OPEN, I say boycott X/OPEN and their
documents.
ISO is _nice_ compared to this.
--
[Erik Naggum] Naggum Software; Gaustadalleen 21; 0371 OSLO; NORWAY
I disclaim, <erik@naggum.uu.no>, <enag@ifi.uio.no>
therefore I post. +47-295-8622, +47-256-7822, (fax) +47-260-4427eskovgaa@uvcw.uvic.ca (Erik Skovgaard) (09/26/90)
Well, it may get worse yet.
The X.400 APIA is going to be working on a "simplified" API for
X.400.
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.
The X/Open X.400 APIs are aligned with the X.500 API ("XDS") and an
Object Management API (OM API). All will, as far as I know, be published
jointly.
I would not stop the development of the Gateway API (once you have deceided
to undertake it) to the current spec. The new spec is mostly going
to be an extension of the version 1 spec, but it would certainly be
useful to have the version 2 spec to take the Object Management into
account.
Note that the version 1 spec of the Gateway API does not support
ISO 6939 body parts, so some European versions of X.400 may have
a slight problem.
I hope we can fix some of the problems in the "simplified" API.
Please let me have any comments you may have to version 1 of the
spec.
....Erik.RE_Sonneveld@pttrnl.nl ("R.E. Sonneveld, +31 70 332 5362, PTT Research, NL") (09/26/90)
Hello, all
One of my colleagues (who doesn't have the ability to post this
newsitems himself) asked me to post the following question:
I have heard about the X.400 API specifications developed
collaboratively by the X.400 API Association and X/Open Co. Ltd.
I would like to know whether APIA and/or X/Open Co. Ltd. did also
specify an API occuring at the X.400 User Agent (UA) level
producing P7-formatted information. Analogous to the X.400
Applications API producing P3-formatted information.
Many ThanXs,
Hans Maatman
--
Phone: +31 50 82 10 69
Fax: +31 50 12 24 15
E-mail: maatman@pttrtl.nl
400 address: C=NL/ADMD=400Net/PRMD=PTT Research/
OU=Telematics Laboratory/SN=Maatman
--
Posted by: R.E. Sonneveld
RE_Sonneveld@pttrnl.nlkhiem@hpinddm.cup.hp.COM (Khiem Ho) (09/26/90)
> I have heard about the X.400 API specifications developed > collaboratively by the X.400 API Association and X/Open Co. Ltd. > I would like to know whether APIA and/or X/Open Co. Ltd. did also > specify an API occuring at the X.400 User Agent (UA) level > producing P7-formatted information. Analogous to the X.400 > Applications API producing P3-formatted information. > > Many ThanXs, > > Hans Maatman The P7-based API was not included in Version 2. As announced at the press conference in Dallas, APIA and X/Open will (possibly) take up this work in the next phase. If you are interested to participate, pls send me mail, I will forward to the right person. Khiem Ho Hewlett Packard
hrs1@cbnewsi.att.COM (09/27/90)
> 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
ENAG%IFI.UIO.NO@cunyvm.cuny.edu (10/01/90)
RFC-822-Headers:
X-Attn: jns
Newsgroups: comp.protocols.iso.x400
Path: enag
Organization: Naggum Software, Oslo, Norway
Lines: 27
BODY TYPE: IA5TEXT
In article <173*eskovgaa@uvcw.UVic.ca>, Erik Skovgaard writes:
The second version has not yet formally been released but is
available only as an internal (and confidential) X/OPEN document.
Are you serious? Is it a _secret_ what they are going to virtually
"spring on the developers and the public"? Even CCITT and ISO are
willing to let you (me, anyhow) get draft standards and even minutes
from their meetings. Maybe I should try to look and learn and cease
to be amazed at how so-called "standards" are developed.
Thus, you should be careful which spec you implement.
How? Only thanx to this comparativly random comment from you, we get
to know there is a new version coming up, and all development based on
the older version has to be stopped, because we will not be able to
know what the next version will bring.
If this is indicative of X/OPEN, I say boycott X/OPEN and their
documents.
ISO is _nice_ compared to this.
--
[Erik Naggum] Naggum Software; Gaustadalleen 21; 0371 OSLO; NORWAY
I disclaim, <erik@naggum.uu.no>, <enag@ifi.uio.no>
therefore I post. +47-295-8622, +47-256-7822, (fax) +47-260-4427ESKOVGAA%UVCW.UVIC.CA@cunyvm.cuny.edu (10/01/90)
Health warning!
The Gateway API spec that was done jointly between the X-APIA and
X/OPEN is very different from the first version of this spec which
was released in June '89. Omnicom carries this first release and
not, to my knowledge, the second version.
The second version has not yet formally been released but is
available only as an internal (and confidential) X/OPEN document.
Thus, you should be careful which spec you implement.
....Erik.