Tim Frank wrote:
I would agree that a workflow standard would probably be incredibly complex... however, if one exists it would definately be a useful guide if nothing more :)

I have checked quickly the workflow used inside Lenya and that looks pretty slick and enough for most cases. If I had to pick one, I would check for Agila, Lenya, (both in the incubator), OSWorkflow and jBPM (in no specific order)


For me the issue was that there are not very many "smart" WebDAV clients out there right now that support the ability to checkout, lock, checkin. Aside from DAVExplorer, the OS based protocols are the "dumb" kind without DeltaV support. That makes using Web Folders a pain if you want to honour locks and such.

Good points which did not really came to my mind at first. For instance I'm not sure yet, what does Microsoft Office doing when editing a document, it looks like it is locking the resource, but I have yet to figure out what it means in terms of multi user access. I will have to check that.


I think having it integrated with the OS would be a great idea, but for now a web interface would be one way to have advanced features. Also, workflow would not likely be supported by OS clients, so you would need another interface for that portion.

Yes. You're right. I was also thinking about that, as I guess document permission may need to change to reflect effectively the workflow status. I'm not really sure yet what would be the best thing for that, does a workflow status trigger permissions as well or is it just something different ? if you're also accessing the document via WebDAV and it cannot be just something totally defined somewhere else, it must be deeply integrated within the WebDAV methods. (a workflow filter/content interceptor is probably needed for that)


It may also trigger other issues, for example, people often request that a document being validated is not considered 'live' anymore and should be put to 'archive' status, and they may have specific rules for handling archived documents (ie moving documents to a separate store, and being an important metadata when indexing/searching for documents)

Thanks for the link, I hadn't looked around for a DASL reference yet. I was going to do some playing around with the DASL sample in cocoon to see how easy/difficult it was to use. I think it would at least be a step up in simplicity from having to code Java/JSP with the API's.

Well, I'd be glad to have your feedback on that.

Stephane


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to