[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tools not supporting atom:content with @src ?
- To: atom-syntax@xxxxxxx
- Subject: Tools not supporting atom:content with @src ?
- From: Peter Krantz <peter.krantz@xxxxxxxxx>
- Date: Wed, 10 Jun 2009 00:42:09 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=XyQBw3k8DR2Q9grMQAC0GMYVwWE3PzSKxrkJPxVRp2Y=; b=A7qVpvy3KLFUFrx4Bp/nUYyHQVwV6GFKwU2N24P8AyD1RUTZNKdmfkgFRpoqxRRYKJ /7zWJnxNja6XxQ/8nNMiRw0VnQjVocNttm7I+Bh9DjNgEV0oNeIdc2B0xDD0QXAHIsCp 0F5xoVfmgg91sci0z4THWa9E50YMrZIYYS7hk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=vldGh2E7TxipMd/TSz16vuVn4X/PHZVgWIHgIe+Eoz6Uuhu7pOk7FWOWEzJ4tcnTE7 f2smzDCN715wAYaAD81McavRc/MmhyTO8UYkGM7gZOqYk0O0rYki9x5ZSzjD+EGw6L2c 4nWjmg8OuzHND6yOa0kDfRGgT832n8ZHNYXLo=
- List-archive: <http://www.imc.org/atom-syntax/mail-archive/>
- List-id: <atom-syntax.imc.org>
- List-unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
- Sender: owner-atom-syntax@xxxxxxxxxxxx
Hi!
We are using Atom to get notifications about PDF documents added to
collections at various government agencies. This works well since we
are consuming the feeds programatically. A typical entry looks like
this (please note the atom:content element):
<entry>
<id>tag:example.com,2009:1</id>
<updated>2009-05-13T18:30:02Z</updated>
<published>2009-05-13T18:30:02Z</published>
<title>A title</title>
<summary>A summary</summary>
<content src="/docs/example.pdf" type="application/pdf" />
</entry>
It would be nice if the same feeds could be used in popular
feedreaders too. I have tried feeds with entries like the one above in
IE8, Firefox 3.5b4, Google Reader and Safari 4 but none of them make
it possible to access the PDF specified in the atom:content element.
Is this a misunderstanding on my part or is it just a rare enough
example that hasn't been implemented in client software?
Regards,
Peter Krantz