RE: [xri] phone number in XRD?

The same thinking that results in segregating something (like phone number) into two categories (like public and private) will eventually result in three, four, ... seventeen categories (public, private, family only, ... ultra private). I think the same reasoning applies to segregating XRDS into multiple categories.

Perhaps a better approach would be to devise a per SEP access control model -- some way to configure rules that control access to each SEP. Paul's example seems to deal with visibility controls. I heard a little about XRDSP which I think deals with write access. A real access control model should deal with both.

Markus,

FWIW, I’m thinking a lot lately about public vs. private attributes. For example, a person might have a public email address, or a private email address, or both. So in my mind I rephrase your question by adding the word “public” in front of “phone number”. In the architecture I’m envisioning, there’s yet another “private” discovery service SEP (which might also use a private XRDS, or some other mechanism analogous to the Liberty Discovery service) listed in the users “public” XRDS.

-Paul

From: markus.sabadello@gmail.com [mailto:markus.sabadello@gmail.com] On Behalf Of Markus Sabadello
Sent: Thursday, December 13, 2007 11:25 AM
To: OASIS XRI TC
Subject: [xri] phone number in XRD?

What would a SEP look like that has a phone number as an endpoint? And an e-mail address? Do we have service types for this?

Does anyone know an i-name that has such SEPs?

Markus

xri message