Updated with annotations with what is supported in 1.0 and candidates for 2.0 (or beyond)
Operations that cause state transitions may fall outside of 2.0
Prioritization would be (from highest to lowest) for Tasktop:
data model information (like XML schema) (effort large)
support for attachments (effort small)
operation workflow transitions (effort large)
Looking at RSS/IMAP style of notification of changes, see changes as pushed as by server event
Need to address "task key" concept
Progress on extending participation:
Report back on the 22nd with results
SteveSpeicher reported results from synchronization tools providers: interested in OSLC and providing implementations. Will monitor scenarios and specs and be available for solicited feedback.
Some implementation reports have started CmImplementationReports and working on gathering other reports
Discussion on alignment and timing of 2.0 specs with potential product plans.
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use Ideas, requests, problems regarding this site? Send feedback