On Sun, May 08, 2005 at 06:57:09PM +0100, Graham wrote:

> >That's a feature.
> 
> The thing is, I have no idea where to put the atom:copyright content.  
> It might be a short "(C)2005 Robert Sayre" like you see at the bottom  
> of every web page, or it might be a shouty "FOR PRIVATE USE ONLY"  
> thing intended to be displayed prominently, or it might be wordy  
> licensing text, etc etc. As a publisher, I wouldn't know what to put  
> in there other than by seeing what kind of things other people are  
> putting, which kind of undermines having an Atom spec. Some  
> clarification in this area is needed.

My feeling is that we can't impose significant constraints on what the
clients do with the data. Something like "Atom consumers SHOULD
include a way to display the rights statements; publishers MUST NOT
assume that such a display will be given prominence." (The terminology
is probably wrong here.)

What this means to client implementors is that, beyond providing a way
for end users to get at the rights statements, they don't have to bend
their interface or program design towards the rights issue. Since
we're not trying to come up with any kind of mandatory rights
declaration, this strikes me as the right balance.

In my view, a shouty "FOR PRIVATE USE ONLY" would be better placed in
the content itself, at the beginning. While this doesn't make sense
logically, it seems the only viable tradeoff that has any real
utility.

James

-- 
/--------------------------------------------------------------------------\
  James Aylett                                                  xapian.org
  [EMAIL PROTECTED]                               uncertaintydivision.org

Reply via email to