[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RSS extensibility




On Jan 7, 2005, at 5:48 AM, Danny Ayers wrote:


<feed "http://purl.org/atom/ns#
xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/";>
<entry>
   <prism:embargoDate>2005-02-15</prism:embargoDate>
...
</entry>
</feed>

[[
embargoDate
Earliest date (potentially including time) the resource may be used
according to the rights agreement, or clause in the rights agreement.
]]

So the human meaning of an 'embargoDate' element is reasonably clear.
The problem is that with RSS 2.0's approach to extensibility, there is
no relationship defined between this element and any part of the feed
data. Ok, it's an embargo date. But the embargo date of what?

The embargo date of the entry. This seems painfully obvious, and any other reading would be willfully contrary. Either software understands what embargoDate means or it doesn't, and if it does, well then, it'll embargo the entry, and if not, not.


I have not seen any evidence that these RDF incantations have any relation to the needs of implementors. -Tim