I am working on a distributed peer-to-peer version control system for Hibernate. Think of it as a Hibernate analogue to git or mercurial. (It will not be as fast as git, but I hope to make it plenty fast enough for its intended use cases.) It will be released under an open source license.
The intended use cases for it are for supporting lightweight content management. Things like blog entries, calendars, etc., that can be edited on multiple sites and then peer-to-peer reconciled and merged. I would ideally like to have some reasonably standard publishing protocol for accessing one of these repositories. The GData extensions to the Atom publishing protocol are pretty much the best fit for my needs, since my targeted content model is very much what GData already addresses. However, the GData protocol specification is silent on one issue: whether the GData protocol is an open specification. If I endeavor to build a GData server, one which supports the GData protocol for publishing data TO the server, is Google likely to have any issues with this? That is, is the GData protocol considered to be proprietary for server implementations, or is it an explicitly open protocol that anyone is free to implement either a client API *or* a server API for? (One other related question: is Google contemplating submitting its GData extensions to the IETF for inclusion in a future standard version of the Atom Publishing Protocol?) Please clarify. Thank you very much :-) Cheers! Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
