Bob Wyman wrote:
Roy T. Fielding wrote:
a proposal on making the feed element recursive
(Speaking for myself, I'm not clued-up enough to understand the
problem / use-case Roy's pace solves)
Equivalent proposals have often been made in the past (sometimes by
me!). These proposals fall in t
Tennessee Leeuwenburg wrote:
~ MelbournePhilosopher
Current draft specification:
http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-05.txt
atom:author element is defined on page 20
atom:author uses the Person Construct. So have a look at Section
3.2 "Person Constructs" page 9.
Just going through draft-8 at the moment, setting up some PHP classes.
4.2.4 The "atom:copyright" Element
---
"If an atom:entry element does not contain an atom:copyright element,
then the atom:copyright element of the containing atom:feed element's
atom:head
In section 3.3 titled "Date Constructs"
3.3 Date Constructs
A Date construct is an element whose content MUST conform to the
"date-time" production in [RFC3339]. In addition, an uppercase "T"
character MUST be used to separate date and time, and an uppercase
"Z" character MUST be pres
Tim Bray wrote:
PaceTextShouldBeProvided
+1 from Ruby, explicit -1's from Sayre and de hÓra. However, taking
this and PaceOptionalSummary together, it seems clear that the WG
generally believes the following:
- Title-only feeds are OK for data where that's really all you have.
- Failing to prov
Graham wrote:
On 18 May 2005, at 9:36 pm, Robert Sayre wrote:
atom:entry elements are advised to contain ... a non-empty
atom:summary element when the entry
contains no atom:content element
I'd like us to advise including an atom:summary when atom:content is
binary (or for that matter, any non
Mark Pilgrim wrote:
On 5/19/05, Tim Bray <[EMAIL PROTECTED]> wrote:
[atom:summary and accessibility]
Right now our draft says:
atom:entry elements MUST contain an atom:summary element in any of the
following cases:
...
- the atom:entry contains an atom:content that has a "src" attribute
(and is thu
In defining both an atom:feed and atom:entry, atomAuthor is specified as
allowing multiple authors, in both the text description and RELAX-NG
formats.
The atom:source defines atomAuthor as 0 or 1, not allowing multiple
atomAuthors. (Section 4.2.11)
Is that what was intended? Just seemed a
