[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New Version Notification for draft-divilly-atompub-discovery-00

To: "Nikunj R. Mehta" <nikunj.mehta@xxxxxxxxxx>
Subject: Re: New Version Notification for draft-divilly-atompub-discovery-00
From: Hadrien Gardeur <hadrien.gardeur@xxxxxxxxxxxxx>
Date: Wed, 20 May 2009 19:46:58 +0200
Cc: atom-protocol Protocol <atom-protocol@xxxxxxx>
In-reply-to: <AFBD43E6-5E2C-4FAE-BE87-033258902309@xxxxxxxxxx>
List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
List-id: <atom-protocol.imc.org>
List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
References: <20090520171701.7481F3A6C57@xxxxxxxxxxxxxx> <AFBD43E6-5E2C-4FAE-BE87-033258902309@xxxxxxxxxx>
Sender: owner-atom-protocol@xxxxxxxxxxxx

Nikunj,

I agree: it makes sense to divide hierarchy and collection discovery in two separate I-D.

About discovery in HTML documents: you specify rel="service" for AtomPub Service Documents and rel="feed" for an Atom feed, don't you think that it might be useful to have a specific way to discover writable feeds too (backed by a collection) ?

Where should these links be specified ? rel="service" is usually strictly used in the header, but some other rel values from the IANA registry are also used in the body XHTML documents (rel values for pagination for example).

Hadrien

Follow-Ups:
- Re: New Version Notification for draft-divilly-atompub-discovery-00
  - From: Nikunj R. Mehta

References:
- Fwd: New Version Notification for draft-divilly-atompub-discovery-00
  - From: Nikunj R. Mehta

Prev by Date: Fwd: New Version Notification for draft-divilly-atompub-discovery-00
Next by Date: Re: New Version Notification for draft-divilly-atompub-discovery-00
Previous by thread: Fwd: New Version Notification for draft-divilly-atompub-discovery-00
Next by thread: Re: New Version Notification for draft-divilly-atompub-discovery-00
Index(es):
- Date
- Thread