draft-ietf-simple-winfo-filter-reqs-00.txt

draft-moran-simple-pres-filter-reqs-00.txt

draft-khartabil-simple-filter-format-

00.txtdraft-khartabil-simple-filer-func-

00.txtHisham Khartabil

hisham.khartabil@nokia.com

SIMPLE Interim Meeting

29th May 2003

draft-ietf-simple-winfo-filter-reqs-00.txt

• No discussion on mailing list

• We need volunteers to review

• WGLC?

draft-moran-simple-pres-filter-reqs-00.txt

• Newer version draft-ietf-simple-pres-filter-reqs-00.txt was released but never made it to the archive

• Requirement necessitating the ability to retrieve the structure of an XML document. Eg: In order to learn that a tuple has been added

• Ignoring filter requests (perhaps to be polite about unauthorized elements). Should we mandate that: a notifier MUST fully accept or reject a filter

• Volunteer to review

• WGLC?

draft-khartabil-simple-filter-format-00.txt

<?xml version="1.0" encoding="UTF-8"?>

<ev-filter-set xmlns="urn:ietf:params:xml:ns:simple-winfo-filter"

pkgdef="winfo">

<ev-filter id = "filter_X" uri="sip:presentity@domain.com">

<what>

//*[(../@package="presence" and ((@status="terminated" and @event="rejected"))]/ancestor-or-self::*

</what>

<trigger>

<changed changed-from="pending" changed-to="terminated">//*[@status] </changed>

<added></added>

<removed></removed>

</trigger>

</ev-filter>

</ev-filter-set>

draft-khartabil-simple-filter-format-00.txt

draft-khartabil-simple-filer-func-00.txt• Location of the filter function

• More efficient means to replace/ reset filters

• We need volunteers to review

• Are we heading in the right direction?