Re: "so-called" keyword and layer 3

YangWoo Ko <newcat@spsoft.co.kr> Wed, 05 December 2001 16:48 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNV00604QOU3P@eListX.com> (original mail from newcat@spsoft.co.kr); Wed, 05 Dec 2001 11:48:30 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNV00601QOU3N@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 11:48:30 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNV00601QOT3M@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 11:48:29 -0500 (EST)
Received: from spsoft.co.kr ([211.254.82.194]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GNV00434QOSNT@eListX.com> for ietf-irnss@lists.elistx.com; Wed, 05 Dec 2001 11:48:29 -0500 (EST)
Received: (from newcat@localhost) by spsoft.co.kr (8.10.0/8.10.0) id fB5Gjso17050 for ietf-irnss@lists.elistx.com; Thu, 06 Dec 2001 01:45:54 +0900
Date: Thu, 06 Dec 2001 01:45:54 +0900
From: YangWoo Ko <newcat@spsoft.co.kr>
Subject: Re: "so-called" keyword and layer 3
In-reply-to: <05b501c17d97$f49406c0$1719d73d@jamessonyvaio>
To: ietf-irnss@lists.elistx.com
Message-id: <20011206014554.C16357@spsoft.co.kr>
MIME-version: 1.0
Content-type: text/plain; charset=euc-kr
Content-disposition: inline
User-Agent: Mutt/1.3.23i
References: <7FC3066C236FD511BC5900508BAC86FE4364AC@trestles.internal.realnames.com> <09de01c17d1b$c072c2e0$1119d73d@jamessonyvaio> <20011205155021.C8623@spsoft.co.kr> <05b501c17d97$f49406c0$1719d73d@jamessonyvaio>
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

On Wed, Dec 05, 2001 at 08:20:18PM +0800, James Seng/Personal wrote:
> I believe there is also a korean user requirements document. Is it
> possible to share that document with this group? It would certainly help
> to give some insight to why this is so.

Dear James Seng and other,

I copied and pasted some portion of our user requirement document.
We are using the term "name lookup service" to avoid unnecessary
confusion with existing keyword services.

* * *
3 List of Service Requirements

3.1 Return 0 or 1 result
Since the name lookup service is based on the lookup repository 
that is defined in [1], the result to a successful lookup is a 
single group of information.

3.2 Input is a word or a phrase
One of the main purposes of the name lookup services is to allow 
users to use more intuitive and familiar names. In this sense, 
the services should permit the use of phrases as well as 
the words. These names can be in all languages. Further discussion 
includes the maximum words in a phrase, the length of a phrase, 
whether permitting special characters (i.e., slash, comma, 
blank space, parenthesis, and so on) as part of the input.

3.3 No explicit attribute
Users provide only the naming attribute of the object that they 
want to find.  No other attributes of the object are required 
explicitly from users. Instead, the implicit use of attributes 
of the name is permitted for the sake of efficiency and flexibility.

3.4 User profile may be provided (optional)
As mentioned in Section 3.2, some attributes are used to efficiently 
handle the name lookup services. For instance, the following 
attributes could be used in user's profile. 

* The language
* The locality (or preference location)
* The name lookup service provider

In addition to the attributes listed above, the current location 
of mobile terminal might be an important attribute in mobile 
Internet environments. Consequently, the name lookup services 
can provide a context-sensitive service that can enhance user's 
convenience.  Moreover the name lookup services can enlarge the 
limitation of the DNS naming space by using context- ensitive 
naming scheme. 

3.5 Auto completion (optional)
In order to reduce the query error by typing incorrect names, 
the service can complete the full names by matching them partially 
even before finishing typing while users type names.

3.6 Optional link to keyword search
The keyword search [3] , CNRP[5] and Directory systems [6] are 
different from the name lookup service in that the former three 
schemes return 0 or more results while the last one returns 0 or 1 
result. The keyword search can be effectively used with the name 
lookup in cases that the name lookup fails to find the name or 
user wants to see different results.

3.7 List of applications
Service should be designed independent of any applications so 
that any application can use this name lookup service if it 
wants to do.

3.8 Input
The name lookup service allows such inputs as business names, 
brand names, personal names, telephone numbers, or even barcodes. 
It should include as many forms as possible for the input.

* * *

Regards

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
------------------------------------------------*/