James,
My apologies if these questions and comments have been dealt with
before:
* What is the expected or intended relationship between data carried
in the atom:rights element and data pointed to by the license relationship?
* Why did you choose the word "license" when Atom itself uses the
word "rights" for a very similar (if not identical) concept?
* If the intent of the license link is to provide a mechanism to
support "out of line" rights elements, then did you consider doing something
similar to the handling of out-of-line atom: content via a "src" attribute?
For example: Does the license link do anything that would not be
accomplished by adding support for rights elements in the following form:
<rights src="http://..."/>
* If a feed reader discovers both atom:rights and a license link in
a single entry or feed, is there any concept of precedence between the two?
For instance, if the text of the license is more or less restrictive than
what is in the atom:rights element, what should the reader assume about the
rights that are granted?
bob wyman
