El Jueves, 18 de Septiembre de 2008, Paul Kyzivat escribió:
> Iñaki,
>
> What you suggest is a valid way to manage presence.
> This all comes down to how presence data from different sources is
> aggregated. This was discussed quite a bit once, and then we concluded
> that it isn't something that we knew how to standardize. So presence
> aggregation is an area for product innovation. Some may want it the way
> you suggest. Others may really want a single view of presence.


Hi, replying to this old thread:


I read in RFC 3863 (PDIF: Presence Information Data Format) about the 
<location> tag:

   <?xml version="1.0" encoding="UTF-8"?>
   <presence xmlns="urn:ietf:params:xml:ns:pidf"
       xmlns:local="urn:example-com:pidf-status-type"
       entity="pres:[email protected]">
     <tuple id="ub93s3">
       <status>
         <basic>open</basic>
         <local:location>home</local:location>
       </status>
       <contact>im:[email protected]</contact>
     </tuple>
   </presence>


Could it be used to implement the behaviour I suggested? It would rely just on 
the client (on how it renders all the received tuples for the same AoR).

The behaviour in XMPP clients is the following:

- Alice subscribes to presence of Bob.

- Bob is registered at home (resource: "home") and at work (resource: "work").

- He is oline at work and offline at home.

- Alice receives a NOTIFY with two tuples:

     <tuple id="ub93s3">
       <status>
         <basic>open</basic>
         <local:location>work</local:location>
       </status>
     </tuple>
     <tuple id="eqwsdsd">
       <status>
         <basic>offline</basic>
         <local:location>home</local:location>
       </status>
     </tuple>

- Since one of the tuples is "online", the phone of Alice displays Bob as 
"online".

Could it be feasible? does it makes sence?




However, in the same RFC (section 4.2.5 Standardizing Status Extensions) I 
read:

   ------------
   The following example XML Schema defines an extension for <location>
   presence information, which can have the values of 'home', 'office',
   or 'car'.  If the <location> element were standardized, this document
   would be made available in an RFC along with information about the
   use of the extension.
   ------------

So, is this <location> tag already estandarized? (note: it's EASY, just allow 
any string).


Thanks.



-- 
Iñaki Baz Castillo <[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to