anonymous wrote : Personally, I'd wonder if DTSTART, LOCATION, PERCENT and CLASS can
be left out for now.
I agree that these may not be immediate requirements, but wonder if there are some missing
requirements here...or some not so obvious mappings. For my purposes I used task variables
for DTSTART and LOCATION.
anonymous wrote : The task variables should be as easily readable as possible, so I'd
not go for X- properties. Putting them in the description would also not be my favourite,
so that leaves the ATTACH option or leave them out completely (at first).
I need to look a bit further at the possibilities of ATTACH, for readonly purposes I
formatted them into the description.
anonymous wrote : Additionally, I'd include a link somewhere that directly opens the
task form page. For me that would be a near-perfect first release.
Yes, already done.
anonymous wrote : A XUL based ui could be nice, but why not just use the /a webbased page
for updating?
That's certainly the short term approach, but what I'm thinking about here are the
possibilities of providing task specific extensions to PIM type tools for both off-line
and on-line useage. Or to put it another way how far does the iCalendar set of RFCs go to
provide a standard Human Task protocol? Having just come across WS-HumanTask buried
alongside BPEL4People I need to see how close the two compare...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139852#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...