1. Requirements for Keyword Systems
Nicolas Popp
Chief Technology Officer
RealNames Corporation
October 2001

2. 1. Unique Names
Keyword: Hooker’s Street Rods
Names as unique identifiers: includes numbers and codes
Printable names (the business card problem)
Direct navigation as important application

3. Internationalized Domain Names
2. Above DNS
Keywords (삼성)
Internationalized Domain Names (
Domain Name System (
IP Addressing System ( )
New names require a new naming layer (layered approach)
A Keyword hides a URI (resource physical address)

4. 3. In all languages Cartões Bradesco 삼성 AlloCiné
ームズ・米国本社 삼성
AlloCiné
String equivalence issues
localized rules
standardized versus service differentiator
client or server side

5. 4. Context based Cartões Bradesco Cartões Bradesco 삼성 AlloCiné
KEYWORD
COUNTRY
LANGUAGE
SERVICE TYPE (see #5!) …
ームズ・米国本社
ームズ・米国本社
Cartões Bradesco 삼성
Global identifier syntax (expressing context)

6. 5. For all applications & devices
WEB
kw: pé pé le pue
kw:
Service Type
URI
country
lang
PHONE
tel
Tel: us
en-us
http us
en-us
mail us
en-us
http.wap us
en-us
MOBILE

7. 6. With multiple interoperable namespaces
Differentiated
context (language, country, service type…)
syntax (e.g. numbers, idn.idn, codes, prefixes…)
Interoperable
One standard resolution protocol (CNRP++)
One standard registration protocol (PROVREG)
Ubiquitous
Cross-platform client libraries implementing the protocols

8. 7. Layered resolution (bridging the past & the future syntaxes)
ALL syntaxes means that this is the last resolution layer
Express & Recognize a namespace specific syntax (past: DNS, IDN, present: Keyword, enum, IDN.IDN, future: Natural language interface (voice), programmable Web (operator + resource identifier = human command)
Resolution patterns requirements (determination, delegation, cascade, aggregation)
We need to understand the difference between Names & Modifiers:
page pepe le pue, Hilton in Palo Alto
Page pepe le pue