[Oslc-recon] spec comments

John Arwe johnarwe at us.ibm.com
Thu Dec 6 11:47:12 EST 2012

Given the sheer volume, I'll recommend that we triage them on next week's 
call.  Anything that we have unanimous consensus on without any in-call 
discussion time, we can just minute and start updating between meetings 
(typos etc).  The rest we (I, probably) can open specific email threads 
on, since it's always easier to manage things when it's 1 subject per 
thread.  Where there are examples of "same pattern, multiple places" I 
usually took the approach of only noting it once and assuming all 
occurrences would ultimately be searched for and aligned with the working 
group's consensus for what it should look like (changed or not).  It would 
be very sensible if we prioritized the normative sections first, too.  I 
did not give deep scrutiny to the individual resources and properties yet, 
there's enough of the "global" issues to fix I wanted to get the process 
I'm also open to additional meetings to keep it moving, so schedule 'em if 
you want 'em.

I just snapshotted the wiki this morning, pasted into Word, added line and 
page numbers, and used markup to flag things.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-recon_open-services.net/attachments/20121206/d15dd2ce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20121206 Recon Spec.pdf
Type: application/octet-stream
Size: 633379 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-recon_open-services.net/attachments/20121206/d15dd2ce/attachment-0001.obj>

More information about the Oslc-Recon mailing list