Comments on: FOAF meets XRI http://blog.fen.net/2004/07/22/foaf-meets-xri/ peace, privacy and political reform with an eye on freedom, liberty, education, and community Tue, 06 Jan 2009 08:03:27 +0000 http://wordpress.org/?v=2.5.1 By: Fen Labalme http://blog.fen.net/2004/07/22/foaf-meets-xri/#comment-10 Fen Labalme Wed, 28 Jul 2004 23:13:50 +0000 http://wp.fen.net/?p=24#comment-10 The suggestion of another namespace with its own vocabulary sounds good, but I see two problems with it: 1) "get people using it", and 2) privacy issues and progressive disclosure are not addressed. As of now, the FOAF community is already using the foaf:mbox property as sort of a primary key, so there's less of a problem with getting people to use it. Privacy and progressive disclosure would be handled by one's i-broker. Certainly I can see that there may well be a need for an xri: or xdi: namespace in the future, and in fact we're building those now. It might just be that at some point down the road, rather than having XRI/XDI embedded inside of FOAF, it could be the other way around. But that future is a ways away. The suggestion of another namespace with its own vocabulary sounds good, but I see two problems with it: 1) “get people using it”, and 2) privacy issues and progressive disclosure are not addressed.

As of now, the FOAF community is already using the foaf:mbox property as sort of a primary key, so there’s less of a problem with getting people to use it. Privacy and progressive disclosure would be handled by one’s i-broker.

Certainly I can see that there may well be a need for an xri: or xdi: namespace in the future, and in fact we’re building those now. It might just be that at some point down the road, rather than having XRI/XDI embedded inside of FOAF, it could be the other way around. But that future is a ways away.

]]> By: Morten Frederiksen http://blog.fen.net/2004/07/22/foaf-meets-xri/#comment-9 Morten Frederiksen Wed, 28 Jul 2004 20:37:38 +0000 http://wp.fen.net/?p=24#comment-9 You can make this happen on your own: Create a property, say somenamespace:i-name, make it an owl:InverseFunctionalProperty, and get people using it. You now have a key that's usable by everyone - without modification to exisiting usage. You can make this happen on your own:

Create a property, say somenamespace:i-name, make it an owl:InverseFunctionalProperty, and get people using it. You now have a key that’s usable by everyone - without modification to exisiting usage.

]]>