I would like to have application/atomentry+xml for entry. As a result,
application/atom+xml must be a feed.
2. We add a type parameter to the application/atom+xml media type
to differentiate feed and entry documents,
e.g. application/atom+xml;type=feed,
Why is one of the normative references in draft draft-ietf-atompub-format-11
instead of RFC4287?
Franklin Tse
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James M Snell
Sent: Tuesday, November 28, 2006 00:53
To: atom-syntax; atom-protocol
Subject:
, 2006 22:24
To: Tse Shing Chi (Franklin/Whale)
Cc: 'atom-syntax'
Subject: Re: PaceResurrectAutodiscovery
Tse Shing Chi (Franklin/Whale) wrote:
I think that only link should be used. All feeds linked by a
should be ignored during the process of autodiscovery.
Why?
Autodiscovery should
Parse Error! [ http://www.whatwg.org/specs/web-apps/current-work/#parse ]
Quote
The error handling for parse errors is well-defined: user agents must either
act as described below when encountering such problems, or must abort
processing at the first error that they encounter for which they
(Franklin/Whale)
Cc: 'atom-syntax'
Subject: Re: PaceResurrectAutodiscovery
Tse Shing Chi (Franklin/Whale) wrote:
Lachlan Hunt wrote:
Ah, but this works!
html
head
titleFeed Autodiscovery/title
/head
body
p... really long body .../p
link rel=alternate type=application/atom+xml href
location.
Franklin Tse
-Original Message-
From: Lachlan Hunt [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 26, 2006 00:38
To: Tse Shing Chi (Franklin/Whale)
Cc: 'atom-syntax'
Subject: Re: PaceResurrectAutodiscovery
Tse Shing Chi (Franklin/Whale) wrote:
No. Authors take
] On Behalf Of Tse Shing Chi
(Franklin/Whale)
Sent: Sunday, November 26, 2006 00:50
To: 'Lachlan Hunt'
Cc: 'atom-syntax'
Subject: RE: PaceResurrectAutodiscovery
Sorry, browsers have to deal with the infinite number of legacy
documents that already make an infinite number of mistakes.
Significantly
(Franklin/Whale)
Cc: 'atom-syntax'
Subject: Re: PaceResurrectAutodiscovery
Tse Shing Chi (Franklin/Whale) wrote:
However, since the Web Applications draft already covers all of
these issues fairly well, I believe it is unnecessary for this
draft to be resurrected. Instead, a few of the good ideas
type=xhtml... is lacking support from processors.
Franklin Tse
-Original Message-
From: Henri Sivonen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 21, 2006 05:28
To: Tse Shing Chi ((Franklin/Whale))
Cc: atom-syntax@imc.org
Subject: Re: Forward Compatibility
On Nov 20, 2006, at 17:47
Web Apps 1.0 is already defining it
However, since the Web Applications draft already covers all of these
issues fairly well, I believe it is unnecessary for this draft to be
resurrected. Instead, a few of the good ideas from this draft should be
integrated into the WA1 spec.
Web
Section 4.2.1 of RFC 4287:
If an atom:entry element does not contain atom:author elements, then
the atom:author elements of the contained atom:source element are
considered to apply. In an Atom Feed Document, the atom:author
elements of the containing atom:feed element are
to atom-syntax@imc.org
Franklin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Pagaltzis
Sent: Wednesday, November 22, 2006 04:07
To: atom-syntax@imc.org
Subject: Re: The src attribute of atom:content
* Tse Shing Chi (Franklin/Whale) [EMAIL PROTECTED
that
Atom should not be easy to change or be updated very frequently. That's why
Atom should leave some extents of forward compatibility.
Franklin
-Original Message-
From: Henri Sivonen [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 19, 2006 17:43
To: Tse Shing Chi ((Franklin/Whale))
Cc
I recently tried to make a feed acting as a linking page. I am impressed by the
src attribute of atom:content. Then I made a feed entry as follow.
entry
titleExample Title/title
idhttp://www.example.org//id
content type=text/html src=http://www.example.org/; /
Snell
Sent: Monday, November 20, 2006 01:20
To: Tse Shing Chi (Franklin/Whale)
Cc: atom-syntax@imc.org
Subject: Re: The src attribute of atom:content
The spec can be changed, it's just not a great idea to do so until we
get a critical mass of issues that can't seem to be adequately worked
around
Currently, there is no “version” element or attribute to reflect the current
version of Atom using in an Atom feed. Does it mean that there will not be any
new version of Atom?
On the other hand, the specification mentioned “If the value of type is
xhtml, the content of atom:content MUST be
I am sorry that I have sent an e-mail in HTML format. This is the plain text
version, which has the same contents with the HTML version sent before.
Currently, there is no version element or attribute to reflect the current
version of Atom using in an Atom feed. Does it mean that there will
/content
By the way, are they the same?
Franklin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James M Snell
Sent: Sunday, November 19, 2006 03:20
To: Mark Nottingham
Cc: Tse Shing Chi ((Franklin/Whale)); atom-syntax@imc.org
Subject: Re: Forward Compatibility
: Sunday, November 19, 2006 11:30
To: Tse Shing Chi (Franklin/Whale)
Subject: Re: Forward Compatibility
Tse Shing Chi (Franklin/Whale) wrote:
This means that XHTML 2 contents can be used as follows?
content type=xhtml
div xmlns=http://www.w3.org/2002/06/xhtml2/;
!-- Contents XHTML 2.0
19 matches
Mail list logo
