|
link@rel='self' -- different for /collection/entry and link@rel='edit'?: msg#00496network.syndication.atom.protocolsurfacing this out of the MD5 thread... > So you agree that <link rel='self'/> and <link rel='edit'/> can point to > different locations? I'm trying to implement AtomPub -09 section 11.2. I > don't want to expose app:control on link rel='self', only link rel='edit'. If > I decide to implement 11.2, are you saying I MUST tie its use to <updated>? With the caveat that once you retrieve the representation located at link@rel='edit' (which would include <app:control />), then *that* representation's link@rel='self' would reference the location where *that* representation could be retrieved (that's what the 'self' relationship means). Uh oh ... everyone, is this a problem? Are we assuming that an entry resource's 'self' URI would remain the same for all various representations (ie. as represented in the collection feed, and the 'edit' representation)? e. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Why MD5 Headers are Imperative: 00496, Eric J. Bowman |
|---|---|
| Next by Date: | Re: Why MD5 Headers are Imperative: 00496, Eric Scheid |
| Previous by Thread: | Some editoria of the '09 specificationi: 00496, Asbjørn Ulsberg |
| Next by Thread: | Re: link@rel='self' -- different for /collection/entry and link@rel='edit'?: 00496, Asbjørn Ulsberg |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |