RE: [Simple] Updated RPID

[hisham.khartabil at nokia.com]

> -----Original Message-----
> From: Isomaki Markus (Nokia-TP/Espoo) 
> Sent: 13.October.2004 16:59
> To: Khartabil Hisham (Nokia-TP-MSW/Helsinki); 
> 'jdrosen at dynamicsoft.com'
> Cc: 'simple at ietf.org'; 'dag.ekengren at hotsip.com'; 
> 'hgs at cs.columbia.edu'
> Subject: RE: [Simple] Updated RPID
> 
> 
> Hisham,
> 
> There will be no interoperability problem on _syntactic_ 
> level. As you say, a tuple saying I'm in a car is 
> syntactically as correct as a tuple saying I'm in a meeting. 
> 
> What is meant in this context with an interoperability 
> problem is something that actually manifests itself on the 
> user and user interface level. Let's take your example:
> 
> Hisham wrote:
> > PUA1 publishes that the person is in a meeting
> > PUA2 publishes that the person is in a car
> > compositor1 composes in a way picking the former, in a meeting
> > compositor2 composes in a way picking the latter, in a car
> 
> From user and PUA point of view this is undeterministic 
> behavior which is not very good. As a vendor of mobile phone 
> software I would like to give my users a UI whereby they can 
> explicitly set their status to be "in a car", even if some 
> other source tells they are "in a meeting". If there is no 
> way instructing the compositor whether PUA1 or PUA2 input 
> should be taken, the user really has no clue as to what his 
> OWN presence will be, unless he subscribes to it. And even 
> after that he does not know how to change it.

This is not an interoperability problem in my book. This is problem in the compositor implementation that gives your specific user an undesirable result. The behaviour is deterministic, but on a compositor by compositor bases. When you purchase a compositor, you will read the specs for it. If the PUA can communicate with the compositor, and the compositor can communicate with the watcher, then this is enough interoperability.

I think what you want is that the compositor behaves differently in different situations for different users, but you want it to be done in a standardised way. I agree with this, but lets do this work as a second step.

Regards,
Hisham

_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple