1. Presence Data Model Jonathan Rosenberg Cisco Systems

2. Changes Schema alignment with RPID- 07 Schema rules –MUST create valid –No expectation of validation on receipt –SHOULD be prepared to receive invalid ones IANA registrations removed from and –Status still discussed Lack of information follows RFC3840 rules Terminology change; instance -> ocurrence Additional occurrence ID construction discussion –UUID URN –Properties Devices with no services Example updated and validated Namespaces and extensibility –Can reuse a namespace if its parent is a leaf

3. Issue 1: UUID for Phones How does a device without a MAC address construct a UUID? –Do we care, actually? UUID has several versions –Version 1: time based Uses MAC –Version 3/5: name based Uses namespace ID –Version 4: Randomly generated Based on random number Proposal: recommend version 4 for now

4. Issue 2: Aliasing Document doesn’t really talk about aliases and their impact –Sip:joe@example.com –Sip:j.smith@example.com Alias = IMS public ID Proposal –Add a paragraph discussing –Suggest its just a characteristic –Do not define any actual attribute for it

5. Issue 3: Schema design issues fromUntil vs. sinceUntil –RPID defined type as “fromUntil” –But value of the attributes are “since” and “until” –Proposal: align schema name with actual name deviceID –Currently a global type in common schema –But defined as an element twice Data model RPID –Proposal: global element instead

6. Issue 4: PIDF-LO Integration Need spec somewhere that describes how pidf-lo gets used Data model discusses location generally Proposed to keep formal definition of PIDF-LO encapsulation out of data model

7. Next steps Minor revision Proceed to WGLC