Not being an XML expert, really, I might be wrong. However, I think the best way to sort these issues out is to check the XML schema out.
 
The actual XML schema for PIDF defined in RFC3863 itself (section 4.4). The <status> and <basic> elements are defined as follows:
 
     <xs:complexType name="status">
       <xs:sequence>
         <xs:element name="basic" type="tns:basic" minOccurs="0"/>
         <xs:any namespace="##other" processContents="lax" minOccurs="0"
            maxOccurs="unbounded"/>
       </xs:sequence>
     </xs:complexType>
     <xs:simpleType name="basic">
       <xs:restriction base="xs:string">
         <xs:enumeration value="open"/>
         <xs:enumeration value="closed"/>
       </xs:restriction>
     </xs:simpleType>
Don't think this allows such fancy usage as the one you describe.
 
Hope this helps,
 
David
 
 
 
-------- Original Message --------
Subject: [Sip-implementors] Presence: <basic> status and rich presence
From: Iñaki_Baz_Castillo <[EMAIL PROTECTED]>
Date: Thu, November 20, 2008 12:03 am
To: sip-implementors@lists.cs.columbia.edu

Hi, could you please confirm me that the <basic> tag in a PUBLISH/NOTIFY
for "Event: presence" can be just "open" or "close"?

RFC 3863 says:
---------------
4.1.4. The <basic> element
The <basic> element contains one of the following strings: "open" or
"closed".
---------------

AFAIK a more detailed presence status is done using rich presence, something
like X-Lite does:
---------------
<tuple id='tb474d31a'>
<status>
<basic>open</basic>
</status>
</tuple>
<dm:person id='p95426255'>
<rpid:activities>
<rpid:on-the-phone/>
</rpid:activities>
...
---------------

I also find other way in RFC 3863:
--------------
<tuple id="ub93s3">
<status>
<basic>open</basic>
<local:location>home</local:location>
</status>
<contact>im:[EMAIL PROTECTED]</contact>
</tuple>
--------------



Well, I've found a SIP implementation that uses the following presence XML:
-------------
<tuple id='t6a5ed77e'>
<status>
<basic>on-the-phone</basic>
</status>
</tuple>
-------------

I'm trying to report that this state "on-the-phone" is not valid, or maybe
that it's not implemented in "real world" in which the way is adding detailed
presence status with rpid.

Could you please confirm it to me and point to some RFC in which it appears?

Thanks a lot.



--
Iñaki Baz Castillo

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to