John Panzer wrote:
There were strong suggestions at the time, I think, that this was part
of HTML and should belong to the WHAT-WG.
So is there a WHAT-WG document to look at?
Yes. http://www.whatwg.org/specs/web-apps/current-work/#link-type5
--
Elliotte Rusty Harold [EMAIL PROTECTED]
I'd like to add multiple links to my feed for both the current version
of the story and the permalink. E.g.
entry
titleMatt Mullenweg has released Wordpress 2.1.1 and 2.0.9.
/title
content type=xhtml
div xmlns=http://www.w3.org/1999/xhtml;
id=February_22_2007_30633
Antone Roundy wrote:
Both of those would probably be best described as alternate links.
The second one in particular is what alternate was intended to be used
for. However, RFC 4287 contains the following:
o atom:entry elements MUST NOT contain more than one atom:link
element
A. Pagaltzis wrote:
What’s the purpose of the `current` link? Is there ever a case
where it would be bad to send the reader to the permanent
location of the item?
Yes, for some definitions of bad. First of all many sites want to
direct a user to the main page, and then have them click
Mark Nottingham wrote:
Atom has a namespace; that can be use to introduce new versions of the
format.
No, no, and no. We've been down this road before in other specs, and the
community wisdom is that you do not rev the namespace just to
introduce a new version. Doing so breaks a huge
Alastair Rankine wrote:
4. All comments and trackbacks. For each comment or trackback:
a. Source text
This one needs to be expanded somewhat. In particular is it:
A. The text of the entry as published in an Atom feed?
or
B. The source of that text as it appears in the original?
In
Alastair Rankine wrote:
Seems simple enough, but there's almost certainly some complexity that
I'm overlooking.
Yep. What if the images aren't subdirectories of the blog. e.g.
Say we had a blog at http://example.com/foo/bar/blog which in turn
referenced images at
Karl Dubost wrote:
IMHO, when the implementors do not understand the licenses, they have no
rights to do things with content (because it's highly dependant of local
laws)
Ignorance of the law is no excuse. Implementors have the rights they
have under the applicable set of laws,
James M Snell wrote:
That's not quite accurate. Two entries with the same atom:id may appear
within the same atom:feed only if they have different atom:updated
elements. The spec is silent on whether or not two entries existing in
*separate documents* may have identical atom:id and
John Panzer wrote:
I'm attempting to promote the use of explicit licenses in feeds, and
Creative Commons is one great source of predefined licenses suitable for
the kinds of things that people want to use feeds for today:
Creative Commons only covers a very small subset of what's needed
James M Snell wrote:
We are proposing the creation of an Atom Reference Implementation
project at Apache and have donated source to kick things off. Currently
the source fully implements RFC4287 and includes preliminary support for
parsing APP introspection documents and the Feed Thread
James M Snell wrote:
We are proposing the creation of an Atom Reference Implementation
project at Apache and have donated source to kick things off.
What minimum Java version are you targetting? 1.2? 1.4? 5?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
XML in a Nutshell 3rd Edition Just
John Panzer wrote:
All -- I'm starting a discussion about feed licencing which might be of
interest to members of this mailing list, and which will hopefully help
form the technical extensions that AOL uses to deal with feed
licencing. I'd welcome any input that this group may have.
I would recommend against using xsd:anyURI for IRIs. A URI is much more
restrictive than an IRI, and one of the easiest things for a schema
validator to check about an xsd:anyURI is that it only contains
URI-legal ASCII characters. I think a new type is necessary if you do
want to allow IRIs
Eric Scheid wrote:
Is this a valid atom entry?
entry
[...elided...]
summarya snippet of foo xml/summary
content type=application/foo+xml
foo:thing xmlns:foo=http://xmlns.com/foo/0.1/;
foo:nameKing George/foo:name
/foo:Person
15 matches
Mail list logo
