From dsmith@clark.net Mon Feb 24 14:59:40 1997 Return-Path: Received: from ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id OAA29411; Mon, 24 Feb 1997 14:59:39 -0500 Received: from sw-eng.falls-church.va.us (ns1.sw-eng.falls-church.va.us) by ida.org (4.1/SMI-4.1) id AA29489; Mon, 24 Feb 97 14:59:59 EST Received: from mail.clark.net by sw-eng.falls-church.va.us (8.7.1/) id TAA10882; Mon, 24 Feb 1997 19:53:17 GMT Received: from clark.net (root@explorer.clark.net [168.143.0.7]) by mail.clark.net (8.8.5/8.6.5) with ESMTP id OAA02009; Mon, 24 Feb 1997 14:50:27 -0500 (EST) Received: from [168.143.24.1] (dsmith.clark.net [168.143.24.1]) by clark.net (8.8.5/8.7.1) with ESMTP id OAA24264; Mon, 24 Feb 1997 14:50:40 -0500 (EST) Date: Mon, 24 Feb 1997 14:50:40 -0500 (EST) X-Sender: dsmith@clark.net (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: ASIS-comment@sw-eng.falls-church.va.us From: Doug Smith Subject: Specific Comments Cc: jbitto@gsg.eds.com Content-Length: 8232 Status: OR !topic Implementation Permissions !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.