!ASIS Issue #038
!topic  Implementation permission issues
!reference  ASIS 95-1.1.4 Implementation permissions
!from  Doug Smith 97-02-22
!keywords  implementation permission issues
!discussion

"The ASIS Application Program Interface (API) may be implemented through a
 variety of approaches. Approaches permitted by this standard are based on
 the traditional approach and the client /server approach. These
 implementation permissions are depicted in Figure 1-1 and described below:

1.1.4.1		Traditional approach (permission 1)...
1.1.4.2		Client / server approach (permission 2)...
1.1.4.2.1		ASIS API server...
1.1.4.2.2		ASIS API client tool...
1.1.4.3		Distributed traditional approach (permission 3)...
1.1.4.4		ASIS dynamic client approach (permission 4)..."

This section seems to lack any real issues about implementation.
The discussion revolves around candidate implementations without
presenting any unresolved issues not addressed by this standard.
At face value, this section seems to be limiting what kinds of
implementations are acceptable by discussing likely architectures.
It would probably be better to say there are no implementation
limitations imposed by this specification.

Recommend the section be empty, or real issues addressed.

!resolution  Accepted, with Modifications.
!date 97-03-26
!Notes

Sections 1.1.4.2.1 and 1.1.4.2.2 were moved to Annex C.  The section
now only addresses implementation permissions.

References to CORBA were eliminated in Clause 1 in preference to the
generic client/server and IDL terminology.

Changes were made to ASIS version 2.0.M.