ROME

[Stephen Duncan <st...@gmail.com>]

This was brought up on the ROME mailing lists:
https://rome.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1985

However, I'd like to hear thoughts on it from the Abdera community
point of view.  What pieces of ROME are in scope for the Abdera
project?  Is conversion either to or from other syndication formats
something that might be a module in Abdera?  How about support for
feed extensions such as GData, SSE, iTunes, etc?

Any other generic ideas on a vision for collaboration with ROME?  The
differing goals & scopes and all the options for cooperation seem to
make it difficult to get down to concrete ideas on what kind of code
should go where.  Certainly I'd hate to see too much duplication
though...

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: ROME

[James M Snell <ja...@gmail.com>]

The original goal for Abdera was, first-and-foremost to provide a
fully-functional Atom implementation.  The architecture is designed such
that additional things can be layered in.  For instance, it would be
possible to either use Abdera as the Atom parser for Rome, or even use
the Abdera architecture as a basis for Rome 2.0 (e.g. an RSS parser
could be built on StAX/Axiom using the same model used by the Atom
parser). However, I think it would be a mistake for us to try to do too
much, too fast, with regards to collaboration with Rome (which does have
a much broader scope).  I'd recommend that for our first milestone, we
focus primarily on providing solid RFC4287 and Atom Publishing Protocol
Draft-9 implementations.

Regarding extensions, I would suspect that support for common extensions
would be a key goal moving forward.  The nice thing about Abdera's API
is that most of these extensions can be used out of the box (e.g. they
don't require special module parsers or interfaces, etc).  Static
implementations of the extensions are possible using the
ExtensionFactory mechanism.  In my internal development image, I have an
"extras" module that I use to keep my experiments with static extension
implementations (most of which, I've discovered, aren't really necessary
given Abdera's native support for XPath :-)

Regarding conversion, I think an Atom<==>RSS conversion would be a good
thing.  I've been working on an Atom<==>JSON conversion that I'll be
checking into a "James' Crazy Experiments" Branch at some point in the
not too distant future.

Abdera's modular architecture makes it very easy to do these kinds of
"extra" packages.

- James

Stephen Duncan wrote:
> This was brought up on the ROME mailing lists:
> https://rome.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1985
> 
> However, I'd like to hear thoughts on it from the Abdera community
> point of view.  What pieces of ROME are in scope for the Abdera
> project?  Is conversion either to or from other syndication formats
> something that might be a module in Abdera?  How about support for
> feed extensions such as GData, SSE, iTunes, etc?
> 
> Any other generic ideas on a vision for collaboration with ROME?  The
> differing goals & scopes and all the options for cooperation seem to
> make it difficult to get down to concrete ideas on what kind of code
> should go where.  Certainly I'd hate to see too much duplication
> though...
> 

Re: ROME

[James M Snell <ja...@gmail.com>]

Our parser is fast enough that a ROME<=>Stream<=>Abdera would likely be
faster than walking through the object model.  If the by-object approach
did prove to be valuable, the best place for it would likely be an
"extras" package that could be optionally built on an as-needed basis.

- James

Stephen Duncan wrote:
> Sounds about right to me.  How about coversion?  Any value to the
> ability to switch between a ROME generic feed object & an Abdera feed
> object?  Or would you just go from ROME -> atom xml string -> Abdera &
> vice versa?  If there was value to doing it by object, where might
> such code live?
> 
> -Stephen
> 

Re: ROME

[Stephen Duncan <st...@gmail.com>]

Sounds about right to me.  How about coversion?  Any value to the
ability to switch between a ROME generic feed object & an Abdera feed
object?  Or would you just go from ROME -> atom xml string -> Abdera &
vice versa?  If there was value to doing it by object, where might
such code live?

-Stephen

On 6/9/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On 6/8/06, Stephen Duncan <st...@gmail.com> wrote:
> > This was brought up on the ROME mailing lists:
> > https://rome.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1985
> >
> > However, I'd like to hear thoughts on it from the Abdera community
> > point of view.  What pieces of ROME are in scope for the Abdera
> > project?  Is conversion either to or from other syndication formats
> > something that might be a module in Abdera?  How about support for
> > feed extensions such as GData, SSE, iTunes, etc?
> >
> > Any other generic ideas on a vision for collaboration with ROME?  The
> > differing goals & scopes and all the options for cooperation seem to
> > make it difficult to get down to concrete ideas on what kind of code
> > should go where.  Certainly I'd hate to see too much duplication
> > though...
>
> Personally, I'd like to keep Abdera focussed on Atom and extensions
> that work with Atom.  So GData, SSE, iTunes are all fine, but I have
> no interest in expanding into other formats (any of the RSS family,
> for example) or protocols (the metaweblog APIs, for example).
>
> As far as collaboration with Rome, I think it'd be fantastic if Rome
> decided to use the Abdera parser for their Atom support, but I'm less
> interested in merging the two projects since it seems like Rome has a
> much larger scope than Abdera does.
>
> All just inmy opinion of course,
>
> -garrett
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: ROME

[Garrett Rooney <ro...@electricjellyfish.net>]

On 6/8/06, Stephen Duncan <st...@gmail.com> wrote:
> This was brought up on the ROME mailing lists:
> https://rome.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1985
>
> However, I'd like to hear thoughts on it from the Abdera community
> point of view.  What pieces of ROME are in scope for the Abdera
> project?  Is conversion either to or from other syndication formats
> something that might be a module in Abdera?  How about support for
> feed extensions such as GData, SSE, iTunes, etc?
>
> Any other generic ideas on a vision for collaboration with ROME?  The
> differing goals & scopes and all the options for cooperation seem to
> make it difficult to get down to concrete ideas on what kind of code
> should go where.  Certainly I'd hate to see too much duplication
> though...

Personally, I'd like to keep Abdera focussed on Atom and extensions
that work with Atom.  So GData, SSE, iTunes are all fine, but I have
no interest in expanding into other formats (any of the RSS family,
for example) or protocols (the metaweblog APIs, for example).

As far as collaboration with Rome, I think it'd be fantastic if Rome
decided to use the Abdera parser for their Atom support, but I'm less
interested in merging the two projects since it seems like Rome has a
much larger scope than Abdera does.

All just inmy opinion of course,

-garrett