- From: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
- Date: Tue, 07 Jun 2011 13:36:47 +0200
- To: Giuseppe Pascale <giuseppep@opera.com>
- CC: Russell Berkoff <r.berkoff@sisa.samsung.com>, Matt Hammond <matt.hammond@rd.bbc.co.uk>, public-web-and-tv@w3.org
On 3/6/11 17:14 , Giuseppe Pascale wrote: > ** Application Responding to Requests (ISSUE-13) > Is this really needed as a separate use case? Isn't this part of the > "expose a service" and "discover a service" usecase? JCD: The intent of having this one separate is to highlight the message API. Should we have a requirement for an abstract API breaking up a message into its component arguments or not. If you want the issue to be addressed separately, I am fine with dropping this one. Best regards JC -- JC Dufourd Directeur d'Etudes/Professor Groupe Multimedia/Multimedia Group Traitement du Signal et Images/Signal and Image Processing Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144
Received on Tuesday, 7 June 2011 11:37:22 UTC