does it matter what values are in the extended prefix and namespace elements in the atom feed configuration?

does it matter what goes here?

at the end of the day, it's just arbitrary, & unique, literals. it's nice to have them human friendly.

eg, could another publisher swap their name in and be happy,

yes.

or should we default to topazproect.org namespace instead

these are PLoS feeds. the namespaces are being used to tune the feed for PLoS content, services. recommend staying with PLoS namespace.

hmm. if topaz is going to be distributing this as is to other sites, then it should be genericized.

if topaz is planning on distributing a publishing app that doesn't include an enhanced feed, with maybe a different branch for plos, then it makes sense to stay plos.

i certainly don't think that the extended feed is plos specific - any academic publisher would want these features.

my feeling is that nothing in the code should say "plos". amit, please tell me if that's not the goal here, and we're just building something for plos (and then please don't distribute the publishing app code to anyone else :) and i will stop filing tickets about taking out the plos in topaz.

or let me know if i should wait 6 months before caring about this issue (again, my feeling is that the sooner we get the plos out, the less we have to clean up later)

Replying to russ:

hmm. if topaz is going to be distributing this as is to other sites, then it should be genericized.

Topaz is different from the Publishing Application. Topaz has no PLoS specific code in it.

if topaz is planning on distributing a publishing app that doesn't include an enhanced feed, with maybe a different branch for plos, then it makes sense to stay plos.

How the Publishing Application is going to be distributed is not determined yet.

i certainly don't think that the extended feed is plos specific - any academic publisher would want these features.

Yes. Hence the design I had talked to you about passing an XSLT to the all gory feed to allow select transformation.

my feeling is that nothing in the code should say "plos". amit, please tell me if that's not the goal here, and we're just building something for plos (and then please don't distribute the publishing app code to anyone else :) and i will stop filing tickets about taking out the plos in topaz.

This is not my call. The board had determined that the Publishing Application will be open source and PLoS name will definitely be part of it. Passwords are different then this.

or let me know if i should wait 6 months before caring about this issue (again, my feeling is that the sooner we get the plos out, the less we have to clean up later)

I agree, but this is not an issue right now. Let's keep branding stuff out of our list now.

sounds good. i will stop bugging you all about it!

Milestone 0.8 deleted