- From: Jason <jeacott@hardlight.com.au>
- Date: Tue, 12 Dec 2006 16:42:12 +1030
- To: mark.birbeck@x-port.net
- CC: Roland Merrick <roland_merrick@uk.ibm.com>, www-forms <www-forms@w3.org>, www-forms-request@w3.org
I quite like this. In the past I have built complex workflows (not using xforms) that are based on the notion of overdue documents (nothing new here), and as part of that system we ended up adding classifications to documents so that a workflow/escalation/handling policy was based on a document's due date and its classification (and its author and anything else deemed relevant by the various workflows themselves). So that for a given due date the notification times/frequencies/recipients/messages/escalations etc are all different depending on the documents classification. Any thoughts that help represent this kind of idea in an xform are very welcome in my book. Jason. Mark Birbeck wrote: o on. > > The way I was thinking about 'state' was that if some organisation had > a concept of 'overdue' that they applied across many applications, > then it would be great to be able to capture that. So, perhaps we > could do something like this: > > <xf:state id="overdue" /> > > <xf:bind nodeset="books/toread/book" mip:overdue="..." /> > <xf:bind nodeset="books/read/book" mip:overdue="..." />
Received on Tuesday, 12 December 2006 06:12:37 UTC