[Cosmo-dev] atom media creation/update

[Travis Vachon]

Hi Brian

This all sounds fine to me. I'm not finished with the subscription  
and preference work anyway, so this doesn't sound like significantly  
more work on my end than what I already have planned. If you're  
hoping to move forward with this immediately I'll hold off on doing  
this stuff until I hear more from you. This stuff does sound simpler,  
so it could even save me some work.

A couple comments:

>
> i propose that we use xhtml with simple custom microformats to
> represent subscriptions and preferences. this data is easily parsed by
> the browser for use in our ui,
This sounds correct.

> and it makes debugging easier, since i
> can jump into a browser, GET a subscription and see it rendered,
> rather than having to save it as a file to disk and open it with a
> text editor, which is usually what i have to do for entry documents.
>
I usually use Firebug for this kind of thing, so it's not a huge win  
for me. Then again, it could be nice to do spot checks on  
subscriptions by just typing them into the browser bar, a situation  
for which Firebug doesn't currently help.

> we already have eim-json and eimml for representing items, so there's
> no need to come up with anything new there.

Just so we're clear: you're proposing that we leave everything except  
subscriptions and preferences _completely untouched_, correct? If so  
this doesn't sound risky to me.

One other note:

We decided a while back that we need to have some facility for  
setting a preference in the CMP signup request to support the "signup  
and add this subscription to my account" workflow. Will this  
accommodate that?

-Travis

>
> comments? concerns?
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev