Okay, cool... This is the first I've seen this, but that obviously nothing of any great concern.

I guess my next question is the same as what what you, Elliotte, and Karl have already made the primary focus of this thread,

* Beyond providing a way of referencing what license(s) applies to any given entry, how does a machine determine "I am rendering ads on this page, so I can't display the content of this feed, but I can render this feed because the rules for this license allow me to display its content on a page supported by ads?

* Does there exist a specification of any sort, that extends from XML Schema, Schematron, RelaxNG, or similar, that would allow me to determine at run time what rules apply to a given license, and based on the rendering schema for any given page, determine which, if any, linked content can be accessed and rendered as part of this page instance?

Is this where you plan to take this John, or have I missed the boat completely?

On 6/7/06, John Panzer <[EMAIL PROTECTED] > wrote:
Yes, I intended to refer to James' feed license extension:

http://ietfreport.isoc.org/idref/draft-snell-atompub-feed-license/

(James, I think you meant "feed license draft" rather than "feed thread draft", right?  :) )


James M Snell wrote:
I don't want to speak for John, but in the feed thread draft, it's both.
The href is intended to be dereferenceable to retrieve some document
describing the license.

- James

M. David Peterson wrote:
Hey John,

In this example, does rel="license" represent a tagged reference or the
URI to the location of the license?

[snip]
  






--
<M:D/>

M. David Peterson
http://www.xsltblog.com/

Reply via email to