1 / 68

NCOIC Semantic Wiki

NCOIC Semantic Wiki. Aaron Budgor Bruno Carron Stephan Chevalier Ken Cureton Mills Davis Vish Dixit Steve Russell Conor Shankey Jacques-Arial Sirat John A. Yanosy Jr. Topics. Background & schedule — John Yanosy & Steve Russell Presenter bios — Mills Davis & Conor Shankey

calder
Download Presentation

NCOIC Semantic Wiki

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NCOIC Semantic Wiki Aaron Budgor Bruno Carron Stephan Chevalier Ken Cureton Mills Davis Vish Dixit Steve Russell Conor Shankey Jacques-Arial Sirat John A. Yanosy Jr

  2. Topics • Background & schedule — John Yanosy & Steve Russell • Presenter bios — Mills Davis & Conor Shankey • Semantic wiki • Semantic wiki concept of operation • NCOIC Work Group sample scenarios • Demos

  3. Mills Davis202-667-6400 • mdavis@project10x.com • Mills Davis is Project10X’s founder and managing director for industry research and strategic programs. He consults with technology manufacturers, global 2000 corporations, and government agencies on next-wave semantic technologies and solutions. • Mills serves as co-chair of the Federal CIO council’s Semantic Interoperability Community of Practice (SICoP) where he leads research into the business value of semantic technologies and the Semantic Wikis for Information Management (SWIM) working group. Also, Mills is a founding member of the AIIM interoperable enterprise content management (iECM) working group, and a founding member of the National Center for Ontology Research (NCOR). • A noted researcher and industry analyst, Mills has authored more than 100 reports, whitepapers, articles, and industry studies.

  4. Conor Shankey604-730-0086 • cshankey@visualknowledge.com • Founder and CEO of Visual Knowledge — a 15 year old software company specializing in semantic wikis, enterprise class semantic applications, and highly scaleable semantic agent technology. • Architected largest corporate wan/lan of it’s kind outside US in 1990 as part of an enterprise transactional frame system to supplement/replace mission critical mainframe systems of large power utility. • CTO/co-founder of several spin out companies from Visual Knowledge. Also, co-founder Clera Pharmaceuticals, a small anti-psychotic drug discovery company • Member of the NCOR technical committee, Chair of 2006 OWL workshop (International Semantic Web Conference), and industry studies.

  5. NCOIC Semantic Wiki Pilot Proposal

  6. The original WIKI* idea • “A web site where anybody can create/edit a web page” • Structure • is not pre-determined • invented & evolved by community • neither top down or bottom up • Quick collaborative writing • Non-linear hypertext * Wiki is the short form for “wiki wiki web,” from the Hawaiian expression “wiki wiki” meaning fast or quick.

  7. WIKI concepts • Authoring via web browser — Also, uploading of arbitrary (multimedia) content • Simplified wiki syntax — Very simple markup for authors • Collaborative editing — Any page can be immediately contributed to, extended, revised, corrected assuming you have the right privileges • Rollback mechanism — All changes are versioned, audited and transparent to the community • Strong linking — “Concepts” in text can immediately become active resources (pages/links) • Search — Typically, a full text search capability

  8. Wiki way: Distinct concepts or topics are built on the fly Discourse forms around or in the context of a topic Eliminates serialized document work flow Team or community members can immediately see commentary in the context of a topic Versus: Each person edits a copy of the document A poor soul merges the results Expensive file shares E-mailing bulky documents “Versions” of opaque documents everywhere “Organizing” documents in hierarchal file system Benefits of the wiki idea

  9. What? Convert data into something we can comprehend… By developing or applying concepts… Quickly relating them to instances in the world… Applying and revising our world models, and… Sharing our thoughts with others How? Identification—concept encoding Generalization—organizing concepts by kind Aggregation—organizing complexes into simpler concepts Common Properties— relationships (connecting properties), & attributes (flat properties) Naming Conventions— terms / phrases; language Semantics? It’s what we do every second.

  10. Semantic Technologies:Represent meanings & knowledge about things so both computers and people can work with it

  11. Model knowledge about infrastructure, information, behavior, & domain expertise separately from programs, data, & documents

  12. SemanticsWe have experience encoding our thoughts and meanings…

  13. NCOIC Semantic Wiki Pilot Goal:Manage concepts, relationships & models across NCOIC products using a semantic wiki!

  14. Semantic WikisMake knowledge interoperable…

  15. Semantic TechnologiesMake knowledge executable…

  16. NCOIC Semantic Wiki — Sample Screens

  17. Semantic Wiki Concept of Operation

  18. The ProblemDocument-Centric Work Group Processes • Inadequate process for reaching reasonable technical consensus • Costly & ineffective collaboration across work groups • Difficulty understanding & managing complex interrelationships across set of NCOIC products • Inefficient, error-prone, and time consuming process for aligning & harmonizing work products across work groups • Costly & ineffective process for managing changes and versions across NCOIC product set • Inability to support user needs to find all relevant NCOIC information and guidance in context • Lack comprehensive solution for compliance, export control, and jurisdictional viewing

  19. NCOIC Semantic Wiki Pilot Security, Control, Administration Users Information Sources NCOIC policy & reference knowledge Governance in wiki Jurisdictional viewing Member profiles/roles Security, sign-on, etc. INPUT OUTPUT Government Government Browse Search Assess Harvest Ingest Extract Categorize Sign-on Authorize Browse Search Query Navigate Report NCOIC Member NCOIC Member Documents Web DBs Models Schemas SEMANTIC KNOWLEDGE BASE Web Documents Patterns Models Industry Industry FT & WG Use Commercial Commercial Search Navigate Train Import Read Author Edit Select Extract Annotate Model Report Harmonize Consense Public/Internet Public/Internet Setup Secure Invite Authorize Change Version Approve CR SII NCAT NIF … Other The SolutionKnowledge-Centric Work Group Process

  20. NCOIC Semantic Wiki PilotOperational capabilities

  21. NCOIC Semantic Wiki PilotUser Roles NCOIC Security & Export Control Experts Apply law, regulation, policy to knowledge access & sharing across boundaries SEMANTIC KNOWLEDGEBASE NCOIC WG Domain Experts Work with documents & conceptsin the semantic wiki NCOIC Modeling Experts Develop schemas, models & ontologies

  22. NCOIC Semantic Wiki Alignment Environment • Defines semantic relationships across WGs • Enables collaborative development of visible harmonization across NCOIC work products • Creates & manages NCOIC knowledge base and NCOIC ontology CR FT Semantic Wiki SII WG Semantic Wiki NCAT WG Semantic Wiki NIF WG Semantic Wiki … • WFR • Data Collection Workbook • Stakeholder List • CR Ontology • Navy VKR Ontology • SCOPE Doc • Reference Guide • SCOPE Ontology • Standards (OWL, WSDL) • Content Doc • Object Model • Relational Model • Related Standards • Problem Statement Doc • Related standards NCOIC Semantic Wiki PilotEnvironment

  23. NCOIC Semantic Wiki PilotSemantic Wiki and Integrated NCOIC Semantic Knowledge Base Open Standards NCOIC Semantic Wiki NCOIC Lexicon Open Standards Ontology NCOIC Integrated Ontology NCOIC Integrated Knowledge Base Building Blocks • Customer • Requirements • DAR,CADM, DAP • DoDAF to DRL • JCIDS • PIM • NCOW RM • Capital Planning • PPBE • Acquisition • BCIDS • Net Ready KPPs • KIPs • DISRonlineProfiles Building Blocks Ontology NCAT NCAT Ontology NIF Patterns NIF Pattern Ontology • Semantic Interoperability • Patterns • -Information Exchange, Semantics • Services, Mediation • Msg Content Transformation • Collaboration, Workflow • Discovery, Context Awareness • Autonomicity, Management Mobility Mobility Ontology IA Customer Requirements Ontology IA Ontology SIOP Ontology Interoperability Causes Document NCOIC SCOPE Document NCO Tenets Ontology Interop Ontology SCOPE Ontology NCO Tenet Ontology

  24. S&RL Workbook FORCENet Workbook Building Blocks NIF ver 2 CR Ontology MBWG MNO MECI Workbook SCOPE Document CR Workbook IA Workbook MBWG MNE SII Workbook SCOPE Ref Guide MBWG Workbook CR WFR SII Source Docs SCOPE Ontology • CR Source Information • Documents • - Web sites • - Models • Frameworks • Architectures • R&D • Experiments • Live Exercises CR WSBB NCAT Standards NCAT Engine NCAT Content NCAT Ontology NCOIC Semantic Wiki PilotNCOIC Work Product Alignment Relationships Map (Subset) • Lines indicate technical alignment is required and complex and costly to perform • Semantic Wiki will enable detailed alignment specifications to be developed and captured

  25. NCOIC Work Group Sample Scenarios

  26. NCOIC Work Group Sample Scenarios • CR Ontology & CR Workbook Alignment • CR Topic Navigation Across Domains • CR/MECI Concept Traceability • SII SCOPE Document & Reference Guide Harmonization and Build SCOPE Ontology • NCOIC Information Alignment Trace/Query • NCAT Object & Relational Models/ SII SCOPE Alignment • NIF Consensus Building

  27. NCOIC Work Groups • Customer Requirements Functional Team (CR) • Semantic Interoperability (SII) • Net-Centric Alignment Testing (NCAT) • Net-Centric Interoperability Framework (NIF)

  28. WFR CR Workbooks PFCs/Patterns CR Data Model CR Ontology Building Blocks NCAT Engine Object Model NCAT Engine Relational Model Semantic Wiki Demo Elements SCOPE Ontology SCOPE Ref Guide SCOPE Document

  29. NCOIC Semantic Wiki Alignment Environment • Defines semantic relationships across WGs • Enables collaborative development of visible harmonization across NCOIC work products • Creates & manages NCOIC knowledge base and NCOIC ontology CR FT Semantic Wiki SII WG Semantic Wiki NCAT WG Semantic Wiki NIF WG Semantic Wiki … • WFR • Data Collection Workbook • Stakeholder List • CR Ontology • Navy VKR Ontology • SCOPE Doc • Reference Guide • SCOPE Ontology • Standards (OWL, WSDL) • Content Doc • Object Model • Relational Model • Related Standards • Problem Statement Doc • Related standards Collaborative Semantic Wiki Environment

  30. Semantic Wiki Scenario—1CR Ontology & CR Workbook Alignment • Import the CR Ontology into semantic wiki and extend to match the CR Workbook • Import CR Workbook model and data • Create CR knowledgebase (KB) semantic wiki concepts • Import information source (Systems of Systems-SOS) for matching with CR knowledgebase semantic wiki concepts (and data instances) • Results in X-cross product • (CR Ontology x CR Workbook Model x CR Workbook Data x Selected Doc) • CR Ontology = CR Workbook Model

  31. Semantic Wiki Scenario—2CR Topic Navigation Across Domains • Extend new conceptual relationships between Sponsor documents for SOS Topic • Demonstrate view of all CR instances related to a topic CR semantic wiki selected concepts and - navigate across two different domains to find same topic referenced in different sources (Air Force SAB, OSD draft Sponsor, Systems of Systems Engineering Guide Topic)

  32. Semantic Wiki Scenario—3CR/MECI Concept Traceability • MECI Inf X CR Workbook (Extract MECI research information and apply to CR workbook) • COMCARE Web Site, OASIS Standards, DHS Architecture, (EDXL, CAP), SOA Web Services DMIS, EPAD, Senate Katrina Report • Demonstrates level of traceability among [Information Sources X (MECI Report) Gap Analysis x Requirements x Alternatives(Architectures, Frameworks) x Standards x Recommendations] • Demonstrate extensions for cross domain and alternative solutions - Other Mobile Communications initiatives that might apply [Other initiatives(BACN, STRATELLITE) - CR Workbook x MECI semantic wiki]

  33. Semantic Wiki Scenario—4SII SCOPE Document & Reference Guide Harmonization And Build SCOPE Ontology • Create a SCOPE semantic model (selected dimensions and values) using the semantic wiki • SCOPE Document • SCOPE Reference Guide • Harmonize (SCOPE Doc x Ref Guide) • Create SCOPE ontology

  34. Semantic Wiki Scenario—5NCOIC Information Alignment Trace/Query • Create a Well Formed Requirements (WFR) semantic model (Customer Operational Requirements) using the semantic wiki • Create sample operational functional area templates – choose communications and data sharing • Map MECI x SCOPE x WFR and harmonize • Query semantically against aligned NCO concepts & relationships

  35. S&RL Workbook FORCENet Workbook Building Blocks NIF ver 2 CR Ontology MBWG MNO MECI Workbook SCOPE Document CR Workbook IA Workbook MBWG MNE SII Workbook SCOPE Ref Guide MBWG Workbook CR WFR SII Source Docs SCOPE Ontology • CR Source Information • Documents • - Web sites • - Models • Frameworks • Architectures • R&D • Experiments • Live Exercises CR WSBB NCAT Standards NCAT Engine NCAT Content NCAT Ontology NCOIC Alignment Relationships Map (Subset) • Lines indicate technical alignment is required and complex and costly to perform • Semantic Wiki will enable detailed alignment specifications to be developed and captured

  36. Semantic Wiki Scenario—6NCAT Object & Relational Models/ SII SCOPE Alignment • NCAT object model mapping with SII SCOPE dimensions and values • NCAT relational model and illustrate alignment with NCAT object model

  37. Semantic Wiki Scenario—7NIF Consensus Building • NIF consensus building around technical concepts • Concepts for functional areas • Concepts for PFCs, patterns

  38. Background & Schedule

  39. NCOIC Semantic Wiki Pilot Plenary Presentations & DemonstrationsNovember 27–December 1, San Diego, CA • Monday Nov 27th Tech team sometime in 3-6 PM session -High Level -- 20min presentation • Tuesday Nov 28th NCAT Content/SII 8-10 AM -- 20 minutepresentation • Wednesday Nov 29th 8:10 -9:00 AM Joint CR / SII Semantic Wiki – 50 min demo & prezo • Wednesday Nov 29th 11-12AM NCAT possible demo • Wednesday Nov 29th afternoon Semantic Interoperability Panel -- highlights (10 minute) • Thursday Nov 30 CR WFR Track 10-12 AM, -- 30 min presentation on semantic wiki • Thursday 1-4 PM Semantic Interoperability -- 60 minute demonstration with scenarios • Thursday Close of day outbrief --10 min highlights (out of 30 min) • Friday Morning Tech Team Wrap-up (Support statement, Benefit [e.g.Review Management], Recommendations, Request for Decision) • Next Steps – (Approve pilot program -- formation of Semantic Wiki Team, Contract, IT Plan, Training Plan)

  40. Semantic Wiki Concept of Operation(back-up)

  41. Pilot Action Recommendations • Authorize the NCOIC Semantic Wiki Pilot • Charter NCOIC Semantic Team to: • Maintain the NCOIC semantic model • Technically support for Semantic Wiki Pilot • Manage creation of an Integrated Semantic Knowledge Base • Approve the Pilot Plan • Review Statement of Work • Allocate Pilot Budget • Execute the Semantic Wiki Pilot with participation from SII, CR, NCAT, Building Blocks, NIF • Write the Pilot Evaluation Report for the Tech Team

  42. NCOIC Semantic Wiki PilotScope • Manage collaborative alignments across WGs • Support technical teams consensus building • Evaluate semantic wiki as cross-WG collaborative environment for: • Cross organizational information product alignment activities • Creation and management of information concepts in each COI • Extraction and analysis of source information and linking to WG technical concepts (standards, customer docs, etc.) • Knowledge version management • Establish Semantic ontologies and knowledge bases • Evaluate Semantic Wiki to develop semantic ontologies related to semantic wiki concepts • Evaluate ability to create model to align NCO information and initiatives • Evaluate ability to develop NCO knowledge base using semantic models • Evaluate ability to easily navigate and find relevant information • Evaluate ability to mediate multiple ontologies • Evaluate ability to automate semantic information discovery and import from any • Automate technical team activity reporting and status

  43. NCOIC Semantic Wiki PilotBenefits

  44. NCOIC Semantic Wiki PilotResults for NCOIC • Improve collaborative development, access to, and lifecycle management of NCOIC work products — including documents, knowledgebases, and underlying semantic models. • Establish an easily used social computing fabric for collaboration and consensus building across all concepts and work products that NCOIC is developing in its multiple working groups. • Pilot test a semantic wiki based concept of operations that provides work group collaboration; semantic email discussion; semantic search, query & navigation; content authoring, editing, and review; semantic modeling; harmonization of work products and models; automated change management & versioning; and semantic security, jurisdictional viewing & export control. • Enable creation, management and sharing of ontologies aligned with work products that all NCOIC members can share and use in multiple situations, especially to relate NCO problems, operational and technical requirements, force capabilities, architectural frameworks, architectural patterns, standards, and technology enablers. • Establish a semantic knowledge base that integrates NCOIC information and ontologies (semantic models) so that all concepts become visible and easily discoverable from a COI and user context perspective, consistent with jurisdictional viewing and export controls. • Create knowledge-based, executable NCO tools and collaborative applications that provide value to our stakeholders.

  45. NCOIC Semantic Wiki Pilot (at a glance)

  46. Semantic Wiki Concept of Operation • Set up a Work Group • Research & import information sources & models • Explore concepts in team room • Collaboratively author, edit work products • Build semantic models • Review, build consensus, approvals • Harmonize concepts across documents & work groups • Manage changes and versions • Apply security, jurisdictional viewing, export controls • Provide semantic search, query, and navigation • Automate knowledge extraction and reporting

  47. Concept of Operation—1Set up a Work Group • Form a work group in the semantic wiki — Can link to information in Kavi, if desired [ e.g., WG charter, members, work breakdown structure, schedule of meetings/events, schedule of deliverables]. • Create separate WG semantic wiki environments; also cross-WG semantic wiki environments. • Send email invitations to join, email acceptances, establish member roles.

  48. Concept of Operation—2Research and import information sources & models • Upload WG resources— documents, models, work products, other sources. • Extract concepts/relationships found in sources • Manage semantic concepts: • Concept identity • Definition • Higher-level classes • Lower-level (more detailed) classes • Associations (see also) • Relationships

  49. Concept of Operation—3Explore concepts in Team Room • Engineers from one or more WGs form a “team room” in the semantic wiki to explore concepts, issues, and recommend resolution. • Discuss topics, author and post material in wiki, edit content of topic, identify concepts of interest. • Conduct threaded discussions in the semantic wiki as well as through email. Email threads include concept references; replies go directly to members as well as post to wiki organized by concept discussion. • Semantic wiki captures team room discussion and organizes it by concept.

More Related