RealNames Template

1
Requirements forKeyword Systems Nicolas
Popp Chief Technology Officer RealNames
Corporation October 2001
2
1. Unique Names

• Names as unique identifiers includes numbers
  and codes
• Printable names (the business card problem)
• Direct navigation as important application

3
2. Above DNS
Keywords (??)
Internationalized Domain Names (www.??.co.kr)
Domain Name System (www.samsung.co.kr)
IP Addressing System (231.133.53.23)

• New names require a new naming layer (layered
  approach)
• A Keyword hides a URI (resource physical address)

4
3. In all languages

• String equivalence issues
• localized rules
• standardized versus service differentiator
• client or server side

5
4. Context based
AlloCiné
AlloCiné
Cartões Bradesco

• 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 1-650-218-3615
Service Type
URI
country
lang
PHONE
tel
Tel[phone]
us
en-us
http
http//www.popp.nu/
us
en-us
mail
mailtonico_at_realnams.com
us
en-us
http.wap
http//wap.popp.nu
us
en-us
EMAIL
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