RE: [Simple] Adding a telephone number to a basic PIDF document

Thanks Paul.  Would it be fair to say that devices are generally only used when multiple services need to be represented together?  

Back to your question regarding the missing contact element, it looks like I have something else I need to clear up.  The schema in RFC 3863 makes contact an optional element for tuple.  I figured that if the contact is omitted, then it should be simply derived from either the subscription request URI, or the entity attribute.  If that is not the case, and the contact element really is optional, then what does it mean to have a tuple with no contact? 

Tim

________________________________

From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Thu 10/6/2005 4:26 PM
To: Tim Rang
Cc: Simple WG
Subject: Re: [Simple] Adding a telephone number to a basic PIDF document

Tim,

I wouldn't do it the way you propose.

I would simply add an extra <tuple> with a <contact> containing the
telephone number as a tel: uri. You can also identify it as a different
device if you wish. I believe you may do that as a deviceID in the tuple
*without* also including <device>.

But I am confused about your intent. It looks like you intend to have
one tuple even without the phone number. (Since you are from MS I am
pretty sure you must plan to have a PC in here.) But then I am confused
because your tuple is open but has no contact - so it isn't *very* open.

If my assumption is right, I would expect something like:

<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"
xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"

xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" entity="sip:foo@bar.com">
   <tuple id="0">
     <status>
       <basic>closed</basic>
       <ep:activities>
         <ep:activity>away</ep:activity>
       </ep:activities>
     </status>
     <dm:deviceID>your-pc</dm:deviceID>
   </tuple>
   <tuple id="1">
     <status>
       <basic>open</basic>
       <ep:activities>
         <ep:activity>away</ep:activity>
       </ep:activities>
     </status>
     <contact>tel:+4255551234</contact>
     <dm:deviceID>tel:+4255551234</dm:deviceID>
   </tuple>
</presence>

You could of course put in <device> as well if you want, but I don't see
any need here.

        Paul

Tim Rang wrote:
> My apologies if I have addressed this to the wrong alias, but I am
> having a PIDF problem which I need help with.  My goal is to add a user
> specified phone number to an existing PIDF document format.  I do not
> wish to make a SIP endpoint available for A/V calls, just to tell people
> how to dial my PSTN number.  My starting point is a basic PIDF document
> like the following-
>
> 
>
> <presence xmlns="urn:ietf:params:xml:ns:pidf"
> xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"
> xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"
>
> xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:foo@bar.com">
>
>   <tuple id="0">
>
>     <status>
>
>       <basic>open</basic>
>
>       <ep:activities>
>
>         <ep:activity>away</ep:activity>
>
>       </ep:activities>
>
>     </status>
>
>   </tuple>
>
>   <ci:display-name>Foo Bar</ci:display-name>
>
> </presence>
>
> 
>
> Excluding the option of vcard, I assume that I need to add this phone as
> a device.  So I add a device tuple.  Since I have nothing more reliable
> to use than the telephone number, it is used in both the id attribute
> and the deviceID element.  Draft-ietf-simple-presence-data-model-05
> doesn't state explicitly as far as I can tell, but reading between the
> lines I don't think I can have a device without an associated deviceID
> element pointing to it from a service.  I also assume that the 'note'
> element for device is interpreted differently from a note for person or
> under the 'presence' root so that the note is merely a descriptor of the
> device.  I only assume this because I don't see a better candidate for
> describing the device.  Assuming that, my original document is modified
> as follows-
>
> 
>
> <presence xmlns="urn:ietf:params:xml:ns:pidf"
> xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"
> xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"
>
> xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" *xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"* entity="sip:foo@bar.com">
>
>   <tuple id="0">
>
>     <status>
>
>       <basic>open</basic>
>
>       <ep:activities>
>
>         <ep:activity>away</ep:activity>
>
>       </ep:activities>
>
>     </status>
>
> *  <dm:deviceID>tel:+4255551234</dm:deviceID>*
>
>  </tuple>**
>
>   <ci:display-name>Foo Bar</ci:display-name>
>
>  *<dm:device id="4255551234">*
>
> *   <dm:deviceID>urn:tel:+4255551234</dm:deviceID>*
>
> *   <dm:note>Home Phone</dm:note>*
>
> * </dm:device>*
>
> </presence>
>
> 
>
> Is this how other folks are implementing this?
>
> 
>
> Thanks for your feedback,
>
> Tim Rang
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www1.ietf.org/mailman/listinfo/simple

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