From OntologPSMW

Jump to: navigation, search
[ ]

Contents

[CCT-Rep] CCT-Representation Project Home Page     (1)

Project Title: CCT-Representation ("[CCT-Rep]") - An Ontological Basis for ebXML Core Component Types     (1A)


Current Work Products     (1B)

Most Critical Task(s) At Hand     (1C)

What's New     (1D)

Key Date(s) to Note     (1E)

  • Dec. 1~3 2004 - Semantic Methodology session at EIDX Conference - Menlo Park, CA, USA (rescheduled. was: Aug. 3, 2004 - Orlando, Florida)     (1E1)

Project Mission     (1G)

  • Goal: To influence the adoption of ontologies and ontological engineering methodologies in eBusiness standards.     (1G1)
  • To establish an Ontological Basis for ebXML Core Component Types ("CCT") using the methodologies the [ontolog-forum] has established for the UblOntology project; engage representation and participation from the ontological engineering and standards community (particularly from the standards community that developed and implemented the core component types); and, to produce a reference CCT ontology and a report on findings and recommendations for submission to UN/CEFACT CCTS (and possibly the Harmonization) working group(s).     (1G2)
  • Deliverable(s)     (1G3)
    • 1. a reference ontology of approved ebXML Core Component Types ("CCTONT")     (1G3A)
    • 2. a report on findings and recommendations regarding the current CCT specifications     (1G3B)

Project Workspace     (1H)

CCONT Work Segment: Communications - Protocol - Logistics     (1H3)

  • Business Case for an ontological approach: input to Business Case     (1H3C)
    • this is for collecting arguments supporting the Business Case for employing an Ontological Engineering approach to developing eBusiness standards, of which our [CCT-Rep] project - both the deliverables and the process - can serve as a reference.     (1H3C1)
  • Feedback, Comments, Suggestions for the CCT-Representaion project work: CctRepresentation/CctRep_Feedback     (1H3D)
    • this is for collecting feedback from the team, the ontolog community, the e-business standards development community, and the public at large to the CCT-Ontology development team (i.e. for incoming feedback, from ontolog's perspective) to collaboratively improve on the quality and relevance of this work.     (1H3D1)
  • Draft Feedback and Recommendations for other eBusiness Standards Working Groups: CctRepresentation/CctRep_Recommendation     (1H3E)
    • this is in preparation for the compilation of position paper(s) that the CCT-Representation project team and the Ontolog community can present to the various e-business standards development bodies (i.e. for outgoinging feedback, from ontolog's perspective) that will include (but not limited to) learnings and recommendations as a result of this work.     (1H3E1)

Project Plan     (1I)

  • Updated draft Work Plan: (--ppy/2004.06.15)     (1I1)
    • 1. Continue from AdamPease's mapping of CCT's to SUMO and get out a completed draft first version of the CCTONT. Continuously improve on that. (CCTONT being the 1st deliverable of this project)     (1I1A)
    • 2. Open up the above (item 1) Draft CCTONT for review and comments, and in particular, collect and compile "lessons learned" and appropriate feedback that we could provide to the standards development colleagues -- UBL, OAG, ebXML-CCTS WG, UN/CEFACT-TBG17, ...     (1I1B)
    • 3. Based on the work output of 1. Pat Cassidy moves CCTONT over to the Protege platform by employing work he's been doing in the ProtegeKIF project. Continuously improve on that.     (1I1C)
    • 4. With the KIF-based CCTONT as the normative ontology, start developing/translating/mapping it (in a "lossless" or "lossy" manner) to other languages and representations/languages/formats -- including, but not limited to (as resources and skillsets permit): OWL, XML/XSD, RDF/S, UML2/OCL, UMM/UML Class Diagram, SQL, ... and continuously improve on that.     (1I1D)
    • 5. Based on the work output in 3., put our project in front of the public (the Protege community would be a strong candidate we should target) and solicit support to help get the above (item 4) done. (The July 2004 ontolog workshop at the Protege Conference in Bethesda, MD will be a prime opportunity to get this going.)     (1I1E)
    • 6. Compile and write-up the report on findings and recommendations regarding the current CCT specifications (which is the 2nd deliverable of this project).     (1I1F)
    • 7. Publish and submit the report in 6. to the appropriate standards body. (The August 2004 panel at the EIDX Conference (now postponed to early Dec. 2004) will be a prime platform to debut this report, or at least a draft of it, to the standards community.)     (1I1G)
    • 8. Follow-up on the liason with the standards community with an aim towards influencing the adoption of ontologies and ontological engineering methodology as part of the standards development efforts. Continuously improve on that.     (1I1H)
  • Draft Plan (as of 2004.03.11) - see update above     (1I2)
    • Aim at doing this (first published draft) in 3 months, and open it to public review     (1I2A)
    • possible submission and presentation to UN/CEFACT CCTS (and possibly, Harmonization) Working Group(s) in/about 6 months     (1I2B)
    • Process and Timeline:     (1I2C)
      • clarify UN/CEFACT's intent, where we feel it is ambiguous - try approaching Mark Crawford, editor of CCTS, as the point person     (1I2C1)
      • comments to Adam's mapping -- one month     (1I2C2)
      • we'll try to take one month to draft the deliverable     (1I2C3)
      • and another month to clean it up for presentation     (1I2C4)
      • total time: 3 months     (1I2C5)
      • try to match that to the UN/CEFACT timeline (e.g. so we can formally present it at one of their face-to-face meetings)     (1I2C6)
        • they are now meeting in Bonn this week; the next meeting is probably 6 months away, probably also in Europe.     (1I2C6A)

The Team     (1J)

Reference & Links     (1K)

Meetings, Conference Calls & Work Sessions     (1L)


This page has been migrated from the OntologWiki - Click here for original page     (1L18)