OntologWorkshop Nov 2003/AttendeeContribution

ONTOLOG Face-to-face Workshop Nov. 5~7, 2003 - Attendee Contributions    (AC2)

 (ref. recap by Kurt)    (AC3)

Goals / Expectations for the Workshop    (AC4)

• Build rapport between Ontolog members -> effectiveness online    (AC5)
• See if ontological perspective will help (me / UBL / others)    (AC6)
• See if Ontolog is jelling – identify role / contribution    (AC7)
• Identify value for ontology to provide (use cases)    (AC8)
• Detect inappropriate use of concepts / relationships –> guidelines    (AC9)
• Visibility into UBL work products -> extract semantics    (ACA)
• Secondary objectives    (ACB)
  • Build political relationship with other committees (courtship -> adoption)    (ACC)
  • Observe & learn from process    (ACD)

From the Facilitated Planning Session by KurtConrad    (ACE)

• Ontolog Forum Planning    (ACF)

•    (ACG)
  • Core Values    (ACH)
    • Knowledge creation    (ACI)
    • Open    (ACJ)
    • Exploration    (ACK)
    • Formal and informal    (ACL)
    • Business-focused    (ACM)
    • Enterprise-focused    (ACN)
    • Global impacts    (ACO)
    • Education    (ACP)
    • Understand applied ontologies (methods, tools, technology, theories, philosophy, people)    (ACQ)
    • Community    (ACR)

•    (ACS)
  • Draft Vision Statements    (ACT)
    • Demonstrate a process that enables users with different needs to agree on an overarching structure for knowledge representation.    (ACU)
    • Suddenly able to connect the dots between two-dozen academic and practical “knowledge silos”: BMPL, Open EDI, BPEL, Rosetta Net, International Association of Social Network Analysis, ebXML, UBL, etc.    (ACV)
    • The Ontolog Forum will become a focal point for the development and deployment of open source tools for analyzing and understanding ontologies (singular and multiple)(ontology and Ontology).    (ACW)
    • Be the foremost international open forum on Business Domain ontology -    (ACX)
      • attracting, retaining, [and invigorating] the best minds in this field as members of the community    (ACY)
    • A technical report that analyzes the content of the UBL document set and derives a business collaboration ontology at the business operations level    (ACZ)

• UBL Ontology Project Planning    (AD0)

•    (AD1)
  • Values    (AD2)
    • Apply our knowledge to organize other’s knowledge    (AD3)
    • Detached / Independent / Objective    (AD4)
    • Orchestrate creative result    (AD5)
    • Not fixated on process    (AD6)
    • Create / improve UBL and standards committee alignments    (AD7)
    • Ontology is a solution (range of “positions”)    (AD8)
      • Evangelical    (AD9)
      • Fantatic    (ADA)
      • Practical    (ADB)
      • Objective    (ADC)
    • Mechanism for global impacts    (ADD)
      • Energized and committed    (ADE)
      • Specific objective    (ADF)
      • Deadline    (ADG)
      • Concrete application    (ADH)
      • Education    (ADI)
      • User needs    (ADJ)
      • Add value    (ADK)

• Draft Vision Statements    (ADL)

•    (ADM)
  • To get several users with different project goals (within the general area of business transactions) to agree on a single, detailed representation that is suitable for their different applications.    (ADN)

•    (ADO)
  • Automatically “parses” a complex 22 page legal agreement into a one-page, time-phased (dec-tree, iscoo, declarative) form / display that is easily read by “average” citizen of UK, Tibet, or or even native speaker of Tlinkit (Alaskan) language.    (ADP)

•    (ADQ)
  • The UBL Ontology Project will provide the UBL committee with the means (tools, analysis methods, and metrics) to analyze the ontological consistency and robustness of the UBL.    (ADR)

•    (ADS)
  • Our work product becomes, or at least heavily influences, UBL x.0 (say 4.0), and that UBL x.0 actually turns out to be an ontology and gets adopted by the rest of the business world. (comment: direction OK, UBL may or may not be the vehicle. Therefore, a "UBL-like standard" maybe more appropriate.)    (ADT)

 --
 above content transferred to OntologPlanning_2004 for continuation of the exercise.    (ADU)