Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

IETF105 Regext RDAP JCard Profile

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Cargando en…3
×

Eche un vistazo a continuación

1 de 4 Anuncio
Anuncio

Más Contenido Relacionado

Anuncio

Más de APNIC (20)

Más reciente (20)

Anuncio

IETF105 Regext RDAP JCard Profile

  1. 1. 1 draft-harrison-regext-rdap-jcard-profile ●●● Tom Harrison (tomh@apnic.net) George Michaelson (ggm@apnic.net) IETF 105 REGEXT Working Group
  2. 2. 2 Why profile jCard? ● jCard’s appropriateness in the RDAP context is being reevaluated: – jCard structure is difficult to work with – Underlying vCard model is complex, supports many things not needed in RDAP ● Alternative formats are being considered – E.g. draft-stepanek-jscontact ● Before proceeding with alternatives: could profiling be sufficient?
  3. 3. 3 Details ● Properties – Name, phone number, email, delivery address – Role, organisation – Language, geographic co-ordinates – Contact URI ● Other – Unstructured addresses are required – Multilingual elements may be used (altid/language parameters) – Country code parameters (RFC 8605) may be used
  4. 4. 4 Open topics ● Could this work as an alternative to deprecating jCard? ● Does anything else need to be included? ● Are more/better jCard libraries an alternative to a profile?

×