Difference between revisions of "Action items from 05/03/07 call"
Jump to navigation
Jump to search
(New page: *Review term lists and Jennifer’s shot at placing terms into OBI categories (download the May 3 excel file to manipulate the term lists and add your comments). *Re-generate OBI schemat...) |
m |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | Go back to [[OCI:Main Page]] | ||
| + | |||
| + | |||
| + | |||
*Review term lists and Jennifer’s shot at placing terms into OBI categories (download the May 3 excel file to manipulate the term lists and add your comments). | *Review term lists and Jennifer’s shot at placing terms into OBI categories (download the May 3 excel file to manipulate the term lists and add your comments). | ||
*Re-generate OBI schematic based on current OBI version and come up with a permanent way to accurately synchronize the schematic with the current OBI draft. | *Re-generate OBI schematic based on current OBI version and come up with a permanent way to accurately synchronize the schematic with the current OBI draft. | ||
| − | *Richard will send out email about upcoming workshop, including issues that need to be addressed (such as how we want others to contribute to CTO developoment in a controlled fashion), what we should present, and what we want to accomplish (especially on Day 2. | + | *Richard will send out email about upcoming workshop, including issues that need to be addressed (such as how we want others to contribute to CTO developoment in a controlled fashion), what we should present, and what we want to accomplish (especially on Day 2). |
Latest revision as of 11:21, 6 July 2007
Go back to OCI:Main Page
- Review term lists and Jennifer’s shot at placing terms into OBI categories (download the May 3 excel file to manipulate the term lists and add your comments).
- Re-generate OBI schematic based on current OBI version and come up with a permanent way to accurately synchronize the schematic with the current OBI draft.
- Richard will send out email about upcoming workshop, including issues that need to be addressed (such as how we want others to contribute to CTO developoment in a controlled fashion), what we should present, and what we want to accomplish (especially on Day 2).