OntologWorkshop Nov 2003/NotesFromAttendees

ONTOLOG Face-to-face Workshop Nov. 5~7, 2003 - Notes from Attendees    (ADV)

Notes from PeterYim    (ADW)

ppy/ontolog-nov03-f2f_notes_20031106a.txt    (ADX)

• Thu 2003-11-06 2:00pm - Sue Probert    (ADY)

• TBG-17: group responsible for ebXML Core Component Harmonization    (ADZ)

• two facets in the CCTS    (AE0)
  • Naming    (AE1)
  • Structure    (AE2)

• CCTS is an implementation of ISO 11179 when the work started    (AE3)

• controlled vocabulary    (AE4)
  • the ultimate is ONE controlled volcabulary    (AE5)

• Oxford dictionary definitions, if it is not ambiguous    (AE6)

• cultural differences    (AE7)
  • multi-lingual group    (AE8)

• we now have a context-free UBL, because context-methodologies are slated for UBL 2.0    (AE9)

•    (AEA)
  • CC library should be context aware,    (AEB)
  • the structures should be context driven    (AEC)

•    (AED)
  • UN codelist 1001 - definition of business terms    (AEE)

• important ;    (AEF)
  • controlled vocabulary - "business terms"    (AEG)

• have John Yunker do a CCTS session [action!]    (AEH)

• Thu 2003-11-06 3:00pm Marion Royal    (AEI)

•    (AEJ)
  • FEA formed shortly after Mark Foreman    (AEK)
  • "quicksilver team" - government-wide initiatives    (AEL)

•    (AEM)
  • FEA Reference Models    (AEN)
    • agreement on terminology    (AEO)
      • Business Reference Model (BRM)    (AEP)
      • Service Reference Model (SRM)    (AEQ)
      • Technical Reference Model (TRM)    (AER)
    • identifying and reducing redundancies    (AES)
    • improving service    (AET)
    • saving money    (AEU)

•    (AEV)
  •    (AEW)
    •    (AEX)
      • Data & Information Refernence Model    (AEY)
        • data elements:    (AEZ)
          • Data Object    (AF0)
          • Data Property    (AF1)
          • Data Representation    (AF2)

•    (AF3)
  •    (AF4)
    • disonance in top-down and bottom-up approach    (AF5)
      • OMB sending it out for IVNV (independent verifcation & validation)    (AF6)
      • Marion purports that it suffices from building up from existing elements    (AF7)
    • Marion requests our review feedback    (AF8)
      • also, soliciting comments on: "Candidate Subject Area and Super-Types"    (AF9)
        • Marion doesn't think that is the way    (AFA)

•    (AFB)
  • Marion's work - XML    (AFC)
    • Gov-wide XML registry, distributed    (AFD)
      • Component Life Cycle    (AFE)
        • Identify Gap - emerging technology subcommittee    (AFF)

•    (AFG)
  • governance - AIC SC CIO OMB    (AFH)

•    (AFI)
  • questions to identify business patterns (source: IBM)    (AFJ)
    • Marion requests our review feedback    (AFK)

•    (AFL)
  •    (AFM)
    • details see http://www.feapmo.gov    (AFN)

• What would you want a bunch of ontologist do for you?    (AFO)
  • define the entire government in an ontology    (AFP)
  • but then, what can it do for us?    (AFQ)
    • FEA taxonomy - now with a pilot team    (AFR)

• Thu 2003-11-06 4:00pm - Eduardo Gutentag & Arofan Gregory    (AFS)

•    (AFT)
  • The UBL Context Mechanism    (AFU)
    • ebXML - "8-space" is a multi-dimensional axis    (AFV)

•    (AFW)
  • Arofan: "every classification that was not extensible, broke."    (AFX)

•    (AFY)
  • precepts:    (AFZ)
    • XSD    (AG0)
    • object oriented approach    (AG1)

• Arofan: a point of need:    (AG2)
  • we do not have classification schemes    (AG3)
  • what we need is someone to point us in the right direction    (AG4)

•    (AG5)
  • Bo: how long does it need to last?    (AG6)
    • Arofan: give me 10 yeats and "controlled evolution"    (AG7)

•    (AG8)
  • UDDI requires UN/SPSC, but some people just can't map their products into it.    (AG9)

•    (AGA)
  • Kurt to Arofan: give us some use cases    (AGB)
    • Arofan: Mike Adcock did some work that was pretty good ... let's see if we can dig something out for you guys    (AGC)
    • check also the RosettaNet PIPs (they are use case driven)    (AGD)
    • there's a group in electronics ... pretty good ... EDIC? (check with Jon)    (AGE)

•    (AGF)
  • "is my red equivalent to your scarlet?" -- depends on the situations    (AGG)

•    (AGH)
  • xsd only allows you one axis of ___    (AGI)

•    (AGJ)
  • schematron    (AGK)

•    (AGL)
  • might give us a list of use cases (done with Matt) -- they were bad, but that's the only one we have    (AGM)

•    (AGN)
  •    (AGO)
    • checkwith ____ who took over from Arofan to handle xCBL bug reports    (AGP)

•    (AGQ)
  • BoNewman: the classification schemes are the most brittle aspects ...    (AGR)

•    (AGS)
  • trans-navigational ontologies -- making the connections simultaneously    (AGT)

•    (AGU)
  • use case: Data Mining (--ppy)    (AGV)

Fri 2003-11-07    (AGW)

 (onsite): KurtConrad, BoNewman, BobSmith, BillMcCarthy, PeterYim.    (AGX)

 (online): PatCassidy    (AGY)

• BoNewman: "Alignment in the Virtual Project Space"    (AGZ)

•    (AH0)
  • primary interest with ontolog was in the process (not so much the ontological engineering)    (AH1)

•    (AH2)
  • since this is all voluntary, it boils down to "alignment" (and not "governance"    (AH3)

•    (AH4)
  • Unlike Adam, I believe in "personal ontologies"    (AH5)
    • most of which are implicit or tacit    (AH6)

•    (AH7)
  • Ontologies as Network of Knowledge elements (some people call them "memes")    (AH8)

•    (AH9)
  • there will not be a one-on-one full alignment between personal ontologies between different individuals -- some may have more overlap than others.    (AHA)

•    (AHB)
  • the "egg" model -- core, secondary professional-space), alignment-space,    (AHC)

•    (AHD)
  • the dominant position(s) will influence the goals of the group    (AHE)

•    (AHF)
  • the center of mass of our group (community) ontology -- or the "value network" of the group, may be drifting    (AHG)

•    (AHH)
  • Agent-Behavior-Artifact    (AHI)

•    (AHJ)
  • recommendation: whatever can be done to stabilize the "drift", align and then enforce it through governance    (AHK)

• KurtConrad - "Ontolog Planning"    (AHL)

•    (AHM)
  • Process - by Joe Beck - Strategic Focus    (AHN)

•    (AHO)
  • Core Values    (AHP)
    • Ontolog Values    (AHQ)
    • UBL Ontology Values    (AHR)

•    (AHS)
  • Outcome Statement    (AHT)
    • most desired UBL Ontology Project outcome    (AHU)
    • most desired Ontolog-Forum outcome    (AHV)

•    (AHW)
  • input from Per/IBM Norway    (AHX)
    • Design and Reuse    (AHY)
      • (overlap search, as a design-time tool)    (AHZ)
      • integrate new documents (doc type) into the library (we now have 700 documents and 19,000 elements (fields) -- need the tools to help us do it.)    (AI0)
      • challenge - getting different departments to harmonize on the data elements - is an ontology the solution?    (AI1)
    • have a document in Norwegian, might be able to translate the main point to English for us    (AI2)

• AdamPease -- Formailizing the UBL Invoice BIE's    (AI3)

•    (AI4)
  • Adam's editor: Visual Slickedit (highly recommended)    (AI5)
  • SUMO ... still some missing case roles    (AI6)

•    (AI7)
  • students and employees in SUMO are roles (and not classes)    (AI8)
    • the group her should be aware of this restriction (--PatCassidy)    (AI9)
    • Adam: Cyc, SUMO and DOLCE all relegate these to roles (--Pat later pointed out that OpenCyc actually also had some of those as classes)    (AIA)

• Reading recommendation    (AIB)
  • Ref: Metaphysics - Michael Liux (book)    (AIC)
  • Nicola Guarino N & Chris Welty (paper)    (AID)
  • AdamPease: Standard Upper Ontology Knowledge Interchange Format (SUO-KIF)    (AIE)

• Formalization assignments: [action!]    (AIF)
  • TaxPointDate - PeterYim    (AIG)
  • PaymentMeans - BillMcCarthy    (AIH)
  • Kurt, Bo, Bob & Pat to pick one term each    (AII)

• TimMcGrath - "Document Engineering and UBL"    (AIJ)