[OpenID] [LIKELY_SPAM]Re: [LIKELY_SPAM]Re: OpenID SREG best practice question

[Peter Williams]

The first of my lines below probably sounds crass. Of course RDF is used in massive  dynamic aggregation today, in blogging and syndication.


From: general-bounces at openid.net [mailto:general-bounces at openid.net] On Behalf Of Peter Williams
Sent: Thursday, November 13, 2008 9:22 AM
To: Nate Klingenstein
Cc: OpenID General
Subject: [LIKELY_SPAM]Re: [OpenID] [LIKELY_SPAM]Re: OpenID SREG best practice question

Now that RDF is getting mainstream and works in the core of SQL-server 2008, I can see us making our authorities perform dynamic collation of subordinate attribute authorities, quite soon, at high data rates.

All we really need for openid is some XRDS extensions that describe the attribute contracts.

What I wanted to point out, but didn't, was the ability today of the average aggregator to  impose data-driven ontologies on the aggregates in realtime, vs smush RDF streams for a given RDF schema. The schema-driven rdf engines have advanced to the point where they are now part of the core SQL DBMS scheduling and query-optimization world, vs a library working in RAM.

What matters most is the extension to XRDS, of course

In the typeless sreg/openid world presumably all it needs to be is a list of names, much like an LDIF file format's object class declaration.

Once that's adopted, then perhaps XRDS can focus on making a contract for the AX typed attribute. One could leverage the SAML schema for attributes, but I doubt it would fly in this world. For a too much religion around, in meta-modeling notations/markups.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081113/1ab43557/attachment-0001.htm>