James M Snell wrote:
The value [of x:profile] is equivalent to the profile parameter on the media type. The
set of profile values contained in the document takes precedence over
the set of profile values contained in the media type.
Well, this needs clarification: If a feed at
Is there somewhere a comprehensive survey of the current level of
support in readers, with details for each feature, specially the most
Atom-specific?
I tested content=xhtml support for several readers and none does it
properly. I would like to have information for other readers.
(Remember also
Stephane Bortzmeyer wrote:
Is there somewhere a comprehensive survey of the current level of
support in readers, with details for each feature, specially the most
Atom-specific?
There are a couple of basic tests on the Atom wiki [1] including an
updated test. They're not very comprehensive,
Stephane Bortzmeyer wrote:
Is there somewhere a comprehensive survey of the current level of
support in readers, with details for each feature, specially the most
Atom-specific?
I tested content=xhtml support for several readers and none does it
properly. I would like to have information for
Regarding the following four link relations there seem to be some
inconsistencies with (or maybe only within) the APP 0.7 draft (but
hopefully the editors of 0.8 have caught those already ;-):
Attribute Value: previous
Attribute Value: next
Attribute Value: first
Attribute Value: last
In
Excellent points and yes, you're absolutely correct. If/when the
profile parameter is used in the HTTP content-type, it needs to take
precedence over the metadata contained inline.
Andreas Sewe wrote:
James M Snell wrote:
The value [of x:profile] is equivalent to the profile parameter on
To clarify my +1 to Ship it: At AOL, we are using Atom internally as
a data exchange format (and just converted to 1.0 syntax). We are using
an early version of the introspection document as well, but only for
limited internal use as it's nonstandard and likely to change. When the
dust
-Original Message-
From: Andreas Sewe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 11:37 AM
To: Atom Publishing Protocol
Cc: Atom Syntax
Subject: Re: [Fwd: Approval of Atom LinkRelations Attribute
Value Registrations]
Regarding the following four link
APP should use the values as registered. That is, previous, next,
first, last and current. No need to modify the registrations.
Scott Hollenbeck wrote:
-Original Message-
From: Andreas Sewe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 11:37 AM
To: Atom Publishing
On 24 Jan 2006, at 10:55 pm, James M Snell wrote:
Thoughts?
It's either not going to be used or will be abused when it is. I
can't see it ending well.
Graham
On Jan 25, 2006, at 11:56 AM, James M Snell wrote:
APP should use the values as registered. That is, previous, next,
first, last and current. No need to modify the registrations.
+1
On 26/1/06 4:23 PM, James M Snell [EMAIL PROTECTED] wrote:
thr:in-reply-to id=tag:example.org,2006:/some/entry
is that id for the thing being replied to, or the id of this thr:in-reply-to
element? if the former, is suspect idref would be more appropriate. but what
do I know?
e.
12 matches
Mail list logo
