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

Re: PaceAppControlID

To: atom-protocol <atom-protocol@xxxxxxx>
Subject: Re: PaceAppControlID
From: Eric Scheid <eric.scheid@xxxxxxxxxxxxxxx>
Date: Sun, 18 Mar 2007 09:18:54 +1100
In-reply-to: <45FC5E1E.3040607@xxxxxxxxx>
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>
Sender: owner-atom-protocol@xxxxxxxxxxxx
User-agent: Microsoft-Entourage/10.1.1.2418

On 18/3/07 8:31 AM, "James M Snell" <jasnell@xxxxxxxxx> wrote:

> Could not the same extension spec that defined the feature ref specified
> in the service doc also specify the app:control extension for declaring
> the clients intent?

you mean as an f:control element?

app:draft could also be defined the same way.

Doing so however raises the bar as to what client and server must understand
to implement these two features ... two features which I argue are pretty
fundamental for APP.

e.

References:
- Re: PaceAppControlID
  - From: James M Snell

Prev by Date: Re: Version AtomPub?
Next by Date: Re: I-D ACTION:draft-ietf-atompub-protocol-14.txt
Previous by thread: Re: PaceAppControlID
Next by thread: Re: PaceAppControlID
Index(es):
- Date
- Thread