Issue with comparisons for triggerring

Thread: Issue with comparisons for triggerring

Search this list only Search all lists
Issue with comparisons for triggerring
	2006-03-10 15:07:56
Looks good to me - although I still think we do not need the struck-through text - it only seems to confuse. "The <changed> element is used to identify the XML element or attribute, from the package specific XML document, whose value MUST change, compared to the "previous XML document&quot;, in order to activate the trigger and cause the content to be delivered.  Previous XML document in this context refers to the last XML document that was selected for delivery delivered to that specific subscription before any filter was applied to it." Regards, Sean Jari Urpalainen <jari.urpalainennokia.com&gt; 10/03/2006 08:55                 To:        ext Sean Leahy <Sean.Leahymarconi.com>         cc:        &quot;Hisham Khartabil <hisham.khartabil&quot;, simpleietf.org         Subject:        Re: [Simple] Issue with comparisons for triggerring Hisham and Sean! For me the current text is eligible enough although there are some implicit rules to interpret (and I think I'll understand the intention, but correct me if my example is wrong ...). If this really needs to be clarified (which may not be likely given the 48hours state), an example would be worth a xxx of words: Given the state can have values A, B or C and a transition from A to C is the trigger rule: state | action --------------- A     | notify (initial subscription) B     | - C     | notify B     | - C     | - A     | - C     | notify --------------- Similar tables could be given with numbers with <by>. But as I said I'm contented with the current text although in general I'll prefer good examples over text (lazy implementer ). br, Jari