Another interesting feature of feedLink is that it allows either a reference (href) to the nested feed or the feed directly inlined. However, since at this point I dont need that flexibility, I going for a combination of a custom rel and type="application/atom+xml; type=feed" on a standard atom:link to signify that this is a nested feed. I am not sure if this is kosher with respect to the standard, but that is the least of my concerns now and will address this later by changing my impl if necessary.
thanks for your help! -- yuri On Apr 3, 1:54 pm, "Jeff Fisher (Google)" <[EMAIL PROTECTED]> wrote: > Hi yuri, > > For <gd:feedLink>, I think the general rule of thumb used was that > <atom:link> is used for alternative related elements whereas > <gd:feedLink> was used for elements that are part of the current entry > (e.g. comments) but that are too verbose to be in-lined. > > For guidance the ultimate end-all is in the AtomPub > RFC:http://atompub.org/rfc4287.htmlGranted it's a bit verbose, but it > covers what is required for compliance. There is some trickiness in > things like hierarchies, which have proposals out there but I don't > think there is a consensus on how to properly represent hierarchal > data in Atom yet. > > I'll see if I can scare up some more resources for you. > > Cheers, > -Jeff > > On Apr 2, 12:48 pm, Lemao <[EMAIL PROTECTED]> wrote: > > > Jeff, > > > I am made some initial progress accessing my own data api using GData > > API but I am running into some difficulties when trying to create a > > few extensions myself. These are not issues with the APIs or the > > underlying design just that there is some learning curve both at the > > implementation level and understanding Atom. > > > Do you know of additional pointers that explains how to extend GData > > API entries and feeds (I know I may be asking too much, but I doesnt > > hurt to ask)? > > > My immediate need is to be able to create hierarchical feeds in the > > same way that <gd:feedLink/> is implementing. However it seems that > > feedLink is to be used as a child of <gs:comments/>. I would be happy > > for now to get something working by either implementing my own version > > of feedLink or by reusing it out of the box. > > > thanks, > > --yuri > > > On Mar 26, 5:40 pm, "Jeff Fisher (Google)" <[EMAIL PROTECTED]> > > wrote: > > > > Hiyuri, > > > > There is nothing stopping you from using the Java client library with > > > your own custom services. (Some of the auth stuff might requiring re- > > > working on your end, but a custom service should be able to solve most > > > of this.) You are free to extend and modify the library within the > > > (fairly generous) terms of the Apache 2 license. You are also welcome > > > to re-use the semantics of Google Data for your own APIs, if you see > > > fit. > > > > Let me know how it works out for you and feel free to share your > > > experiences with this group. > > > > Cheers, > > > -Jeff > > > > On Mar 26, 11:53 am, Lemao <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > I am curious to what extent it is possible to use the Java Google Data > > > > API to access own non-google services. > > > > > I took a quick peek at the Java client and design seems decoupled > > > > enough for me to plug my own service class and connect to my own Atom > > > > enabled services. Is that even possible? Do you see any issues with > > > > this (technical or otherwise)? > > > > > thanks, > > > > > --yuri --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Data API" 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/google-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
