RE: hey dude

[Marc C. <ma...@ca...>]

How will PA and these others query pdns? Or more precise, how would you
prefer? I can build a ton of different ways in, and most likely will,
but I don't want to infringe into PA territory and what it is try to do.
-joel

>>>>>>>>>>>>> OK - free for all answer......


>>>>>>>>>>>>>> 1st of all - I'm cc:ing one James Tauber on this email -
he's expressed interest in helping as well.

>>>>>>>>>>>>>>  James is an rdf and XML nerd - and as I pondered
answering this question (about how to querry the PeoplesDNS) I suddenly
realized that the answer to that question - is the same answer that can
be used for another situation where we are faced with the battle of the
RSSs - the simple, XML based RSS 2.0 - versus the complex, rdf based RSS
1.0.

>>>>>>>>>>>>>  I'll jump to the chase and fill-in background later.....

>>>>>>>>>>>>>>>>  The problem new kinds of micro-content faces is in
getting sufficient uptake by all teh News aggregators, blogging tools
and other utils out there.  We are fortunate - within the digitalID
space - of having a format as can use and get additional specs into, in
the guise of FOAF.

>>>>>>>>>>>  It's not that simple for OpenReviews, Recipes or Events.

>>>>>>>>>>>>>>In the rest of the world - 75% of all subscriptions are in
RSS 2.0 format.  So most people expect simple XML and thus we're faced
with using namespaces to extend the format - to flow through new kinds
of micro-content.  And that fact is not such a horrible fact and since
we'll need some sort of namespace to extend teh rdf camp side of things
as well (whether it's RSS 1.0 or Atom) - then namespaces it is!

>>>>>>>>>>>>>>It doesn't take a genius (or a visionary marketing guy
like myself) to figure out that ONE schema should be established for
each of these new kinds of micro-content, and then they flow through
whichever subscription format: RSS 2.0 or RSS 1.0/Atom - and politics be
dammed.

>>>>>>>>>>>>>>>>>>So I can't help but think that the requirement of the
PeoplesDNS be - that it can take updates, pings, notification, r-t
streams, whatever teh hell someone comes up with - to notify an open,
central server about things about people.

>>>>>>>>>>>>>>>>>>>>>>Sure it would be nice ot have just one way to do
it - but (to me) that's like saying there's only kind of person, only
one way that people program, only one way to do something.

>>>>>>>>>>>>>>>>>>>>>>>>>>>> So:
		- SOAP
		- XML-RPC
		- email
		- Jabbber
		- fucking carrier pigeon if need be
		- .com

>>>>>>>>> Does that make sense at all?