DataPortability XML File?

[Navarr Barnier]

I know that this is an over-used concept, and similar in type to
another XML specification (of which I've forgotten, there are so
many!) But in the essence of being able to port data, wouldn't it be
nice to sign up for an online service, enter in the location of your
"DPXML" file, and it automatically catches the data in it (OpenID,
FOAF, OAuth, etc.).

This is something quick I threw together. Please, tell me what you
think. I'm eager to hear thoughts.

(Also needed would be some post protocol to the user's server so that
it can automatically be updated. I'm not sure if this goes along
with, or defeats the purpose of DataPortability, however. But it
would not work out so well if you did something on some service, and
it didn't update for the rest, right? You'd want to be able to keep
your data the same for everything (per DP profile)?

<?xml version="1.0" encoding="utf-8"?>
<portableProfile
xmlns = "http://www.dataportability.org/xmlns/1.0"
xmlns:openid = "http://openid.net/xmlns/1.0"
>
<auths>
<auth type="OPENID">
<location>http://www.gtaero.net/MyID.config.php</location>
<openid:Delegate>http://www.gtaero.net/</openid:Delegate>
</auth>
</auths>
<profiles>
<profile type="XRDS">
<location>http://www.gtaero.net/yadis.xrds</location>
</profile>
<profile type="FOAF">
<location>http://www.gtaero.net/foaf.rdf</location>
</profile>
<profile type="VCARD">
<location>http://www.gtaero.net/card.vcf</location>
</profile>
</profiles>
</portableProfile>

As you can see, its seperated into Authentifications (OpenID, OAuth)
and Profiles (XRDS/Yadis, FOAF, vCard) etc.

This is just some quick thinking on my part, please, post your
thoughts and comments, etc.

-Navarr T. Barnier

[David Recordon]

Hi Navarr,
Any reason this information couldn't just be stored within the XRDS
file as you seem to be using XML anyway? I'd think in most cases this
information will be discovered in the HTML source though as it already
is today.

--David

[Navarr Barnier]

XRDS is not specific enough to contain this information. This sort of file
separates out authentification handles from profiles; whereas XRDS is a list
of websites with a number signifying their importance (if I remember
correctly?). Essentially, the same thing could be accomplished in XRDS, but
in an entirely different way, I do believe.

[David Recordon]

<?xml version="1.0" encoding="UTF-8"?>
<xrds:XRDS xmlns:xrds="xri://$xrds" xmlns="xri://$xrd*($v*2.0)"><XRD>
<Service>
<Type>http://openid.net/signon/1.0</Type>
<URI>http://www.livejournal.com/openid/server.bml</URI>
</Service>
<Service>
<Type>http://xmlns.com/foaf/spec/</Type>
<URI>http://daveman692.livejournal.com/data/foaf</URI>
</Service>
</XRD></xrds:XRDS>