Hi Julian, As the others have already mentioned, an xml namespace seems like a more appropriate way to insert this. The GData extendedProperty elements seem more intended for string key/value pairs. So using a namespace instead, you would wind up with something like:
<myext:status> <myext:created_at>Thu Nov 08 13:38:03 +0000 2007</myext:created_at> <myext:id>398129912</myext:id> <myext:text>My Status Update Text</myext:text> <myext:source>web</myext:source> <myext:truncated>false</myext:truncated> </myext:status> Daniel is quite right though that everyone will be free to ignore your extension, or standardize on a different, incompatible version. We really need a governance model defined for how the spec evolves. In the meantime though, it would be good to at least agree on a directory where extensions in use could be listed. That might encourage some re-use and consensus. I found this existing wiki page for the group: http://groups.google.com/group/opensocial-api/web/opensocial-standards Seems like a good place to start a list of xml extensions. --gh On Nov 9, 2007 8:03 AM, Daniel Feygin <[EMAIL PROTECTED]> wrote: > > Julian, > > There is no process defined right now to negotiate (with whom?!) and > publish well-known GData extensions.You are on your own grabbing > whatever namespace you feel is right and defining your own structure > within it. Since you are way ahead of most people at this point, it > may then become input to whatever extension governance mechanism will > be instituted (may be as simple as publishing to this mailing list), > but there is a high likelihood whatever you come up with will be > obsoleted and you would have to migrate to the newly defined > extension. For now, I suggest publishing to this list to see if there > are other container developers who might be interested in the > extension and who would be willing to support a common extension > format with you for particular data. > > You can also document your extensions on an ecademy developer > website/blog to help developers understand them and create apps to > process such ecademy extension data. Perhaps through adoption of your > extensions by third-party apps you would have better leverage in > standardizing your extensions. On the other hand, if nobody ends up > using the extension on ecademy, then obviously there is no point in > providing the data, at least until the use of such extension becomes > more pervasive among containers to make it worthwhile for app > developers. > > Daniel > > > > On Nov 9, 2007 3:19 PM, Julian Bond <[EMAIL PROTECTED]> wrote: > > > > Julian Bond <[EMAIL PROTECTED]> Thu, 8 Nov 2007 13:22:38 > > > > >I've just been doing some work on support for the People Data API as a > > >source. > > > > >http://www.ecademy.com/feeds/people/1 > > >http://www.ecademy.com/feeds/people/1/friends > > > > One of the bits that bothers me is the right way to extend the GData > > data. Here's one example. Many systems now have a status field (What am > > I doing now?) of 140 ->255 chars. Some also have a location field (Where > > am I now?). These are typically made up of multiple fields eg from > > Twitter. > > > > <status> > > <created_at>Thu Nov 08 13:38:03 +0000 2007</created_at> > > <id>398129912</id> > > <text>My Status Update Text</text> > > <source>web</source> > > <truncated>false</truncated> > > <user> > > ... > > </user> > > </status> > > > > It does seem to me that there's some commonality here across all the > > systems that have this type of status. At the very minimum, and using a > > more GData style. > > > > <status> > > <updated>2007-11-02T06:36:28+00:00</updated> > > <id>http://www.domain.com/status/entry/398129912</id> > > <text>My Status Update Text</text> > > </status> > > > > Now obviously this doesn't fit into gd:extendedProperty unless we do > > something like > > > > <gd:extendedProperty name="status"> > > <updated>2007-11-02T06:36:28+00:00</updated> > > <id>http://www.domain.com/status/entry/398129912</id> > > <text>My Status Update Text</text> > > </gd:extendedProperty> > > > > I want to do this in a way that Myspace, Twitter, Jaiku, Pownce, > > Ecademy, etc could all support in the same way and developers could > > understand the data immediately. > > > > Comments? > > > > > > > > > > -- > > Julian Bond E&MSN: julian_bond at voidstar.com M: +44 (0)77 5907 2173 > > Webmaster: http://www.ecademy.com/ T: +44 (0)192 0412 433 > > Personal WebLog: http://www.voidstar.com/ skype:julian.bond?chat > > *** Just Say No To DRM *** > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Container Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
