https://ontologforum.com/index.php?action=history&feed=atom&title=OntologPlanning_2004%2FPeterInput 2026-07-26T21:04:37Z Revision history for this page on the wiki MediaWiki 1.39.0 https://ontologforum.com/index.php?title=OntologPlanning_2004/PeterInput&diff=2192&oldid=prev 2013-04-26T05:11:02Z

<p>Last updated at: 2005-03-30 17:57:59 By user: ArnoldYim</p> <p><b>New page</b></p><div>= Input to the 2004-01-08 Planning Session by [[PeterYim]] =<br /> <br /> * Ontolog Forum Planning <br /> <br /> * <br /> ** Articulate Goals (1 to 3 years) <br /> <br /> Task: Draft at least two goals (projects, to do items) &amp; 2 measurable objectives (deliverables) for each goal<br /> Time: 7 minutes to work independently &amp; 3 minutes to review <br /> <br /> * <br /> ** <br /> *** Goals <br /> **** Be the foremost international open forum on Business Domain ontology -- attracting, retaining, [and invigorating] the best minds in this field as members of the community <br /> **** be running major projects in collaboration with other organizations in the business ontology domain <br /> <br /> * <br /> ** <br /> *** Deliverables <br /> **** have at least 5 to 10 active participants in all of the key facets of a community of practice <br /> **** number of projects going in 1 year - 3 ; 2 years - 10 ; 3 years - 30 <br /> <br /> (ran out of time) ... moving on <br /> <br /> * UBL Ontology Project Planning <br /> ** What timeframe? <br /> *** be able to release a first ubl-ontology (alpha-1) by May 2004 <br /> *** be at beta stage by end Dec. 2004 <br /> ** 2 goals <br /> *** get funded so we actually have resources to get this work done <br /> *** team up with others -- standards group (UBL, UN/CEFACT, NIST, ...) and users organizations, so that our deliverables can be validated and applied <br /> ** deliverables <br /> *** SBIR proposal by January 15 <br /> *** get awarded at least 1 SBIR grant by Jun 2004 <br /> *** start 3 pilot implementations after alpha is available <br /> *** have a demo for each of our 3 use cases <br /> <br /> * Constraints - top 4 <br /> ** not properly organized <br /> ** don't have an action plan <br /> ** not yet funded <br /> ** not properly trained to implement the methodology adopted <br /> <br /> * Strategy <br /> ** get organized <br /> *** form a proper team, with committed leadership <br /> ** put together an action plan <br /> *** do KIF training (core player should all know how, even if not proficient) <br /> *** then assemble pairs of ontologist+domain experts and then formalize in natural language first <br /> *** get funded (and hire students to code after the process above) <br /> *** post a project plan / gantt chart ... (the whole works) ... and keep that refreshed <br /> <br /> * <br /> ** also, we should have started with core components, not documents (like purchase order or invoice) <br /> <br /> * 3 issues under [Gap Analysis] - description, resolution strategy &amp; 2 measurable objectives each: (session: 2004.02.05) <br /> <br /> * <br /> ** (1) Lack of solid project plan -- as a project, maybe because this is a distributed ad hoc working group, we still lack the very basic organization and project life-cycle planning and management processes that ordinary projects of this sort would have started out with. <br /> *** Strategies -- <br /> **** what we are doing now ([[OntologPlanning]] 2004) is good, let's keep that up, and get more people involved <br /> **** appoint project managers and start to manage the [[UblOntology]] project like a &quot;real&quot; project, with regular and structured meetings (virtual or f2f), deliverables and deadlines. <br /> **** alloting one weekly session per month to do planning (as we are doing now) is great! <br /> **** before doing that, I think we need to get some sponsorship or funding, so that core people can make this part of their &quot;job&quot; and a priority to get things done on time. <br /> <br /> * <br /> ** (2) Not properly trained to implement the methodology which has been adopted -- participating members should all be brought up to speed on the basics of formalizing a concept (say, something in UBL) and representing that in SUO-KIF. <br /> *** Strategies -- <br /> **** do structured tutorials and have them documented for future reference and re-use <br /> <br /> * <br /> ** (3) Not adequately funded -- if we were to develop any sort of serious standards work, we need the resources to get things done properly. <br /> *** Strategies -- <br /> **** form a fund-raising sub- task force <br /> **** get commercial and government sponsors</div>

imported>ArnoldYim