Article View: comp.protocols.iso.x400
Article #952Re: O/R name component ordering (was: Report from X.400 development
From: Neil Koorland
Date: Mon, 24 Jun 1991 23:21
Date: Mon, 24 Jun 1991 23:21
23 lines
1448 bytes
1448 bytes
> More to the point of the problem with changing things at this point, > there are service providers and vendors with hundreds and thousands of > systems in the field that will need upgrading one way or another over > time. As a vendor, HEAR, HEAR ! > While I am in here -- Does anyone have any idea as to how much use > will be made of the Terminal Identifier and the User Agent Numeric > Indentifier atributes of the ORADdress? > the work of enabling their entry now, or not. One problem I see is > that a user interface that prompts for all the odd attributes is going > to drive the users crazy! The regular atributes are more than enough > already! We have never come across users that use these attributes, but I don't think that supporting it means having to prompt for them every time. What about configurable products and user profiles ? Unfortunately, even leaving them out of the prompt won't stop your users from going crazy when they still have to provide input values for all the other attributes. Neil Koorland
Technical Details
Message-ID:
<9106241376*koorland@vancouver.osiware.bc.ca>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!ucivax!gatewayShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!ucivax!gateway From: koorland@vancouver.osiware.bc.ca (Neil Koorland) Newsgroups: comp.protocols.iso.x400 Subject: Re: O/R name component ordering (was: Report from X.400 development Message-ID: <9106241376*koorland@vancouver.osiware.bc.ca> Date: 24 Jun 91 23:21:37 GMT Lines: 23 Approved: usenet@ics.uci.edu