2 NCOIC Semantic Wiki Aaron Budgor Bruno Carron Stephan Chevalier Ken Cureton Mills Davis Vish Dixit...

2

NCOIC Semantic WikiAaron Budgor

Bruno Carron

Stephan Chevalier

Ken Cureton

Mills Davis

Vish Dixit

Steve Russell

Conor Shankey

Jacques-Arial Sirat

John A. Yanosy Jr

3

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

4

Mills Davis202-667-6400 • [email protected]

+ 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.

5

Conor Shankey604-730-0086 • [email protected]

+ 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.

6

NCOIC Semantic Wiki Pilot Proposal

7

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.

8

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

9

Benefits of the wiki idea

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

10

Semantics? It’s what we do every second.

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

11

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

12

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

13

Semantics

We have experience encoding our thoughts and meanings…

Natural language Documents, speech

Visual language Tables, graphics, charts, maps

Formal language Models, schema, logic, mathematics, professional and scientific notations

Behavior language Software code, declarative specifications, functions, algorithms,

Sensory language User experience (UX), human-computer interface

14

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

15

Semantic Wikis

Make knowledge interoperable…

16

Semantic Technologies Make knowledge executable…

17

NCOIC Semantic Wiki — Sample Screens

18

Semantic Wiki Concept of Operation

19

The Problem Document-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

20

The Solution

Knowledge-Centric Work Group Process

Government

NCOIC Member

Public/Internet

Industry

Commercial

Government

NCOIC Member

Public/Internet

Industry

Commercial

CR SII NCAT NIF Other

SEMANTICKNOWLEDGE

BASE

Information Sources UsersSecurity, Control, Administration

…

NCOIC policy & reference knowledgeGovernance in wiki Jurisdictional viewing Member profiles/rolesSecurity, sign-on, etc.

BrowseSearchAssessHarvestIngestExtractCategorize

DocumentsWebDBsModelsSchemas

INPUT OUTPUT

Sign-onAuthorizeBrowseSearchQueryNavigateReport

WebDocumentsPatternsModels

SetupSecureInviteAuthorize

SearchNavigateTrainImportReadAuthorEdit

SelectExtractAnnotateModelReportHarmonizeConsense

ChangeVersionApprove

FT & WG Use

NCOIC Semantic Wiki Pilot

21

NCOIC Semantic Wiki PilotOperational capabilities

22

NCOIC WG Domain ExpertsWork with documents & conceptsin the semantic wiki

NCOIC Security & Export Control ExpertsApply law, regulation, policy to knowledgeaccess & sharing across boundaries

NCOIC Modeling ExpertsDevelop schemas, models

& ontologies

SEMANTICKNOWLEDGEBASE


User Roles

23

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 FTSemantic Wiki

• WFR• Data Collection Workbook• Stakeholder List• CR Ontology• Navy VKR Ontology

SII WGSemantic Wiki

• SCOPE Doc• Reference Guide• SCOPE Ontology• Standards (OWL, WSDL)

NCAT WGSemantic Wiki

• Content Doc• Object Model• Relational Model• Related Standards

NIF WGSemantic Wiki

•Problem Statement Doc•Related standards

…

NCOIC Semantic Wiki Pilot Environment

24

NCOIC Semantic Wiki Pilot Semantic Wiki and Integrated NCOIC Semantic Knowledge Base

NCOIC Semantic Wiki

NCOICIntegratedKnowledge

BaseNCAT

NIF Patterns

Semantic InteroperabilityPatterns-Information Exchange, Semantics-Services, Mediation-Msg Content Transformation-Collaboration, Workflow-Discovery, Context Awareness-Autonomicity, Management

Customer Requirements-DAR,CADM, DAP-DoDAF to DRL-JCIDS-PIM-NCOW RM-Capital Planning-PPBE-Acquisition-BCIDS-Net Ready KPPs-KIPs-DISRonlineProfiles

NCOICSCOPE

Document

NCOICLexicon

NCOTenets

Ontology

Mobility

InteroperabilityCauses

Document

InteropOntology

SCOPEOntology

NCO TenetOntology

OpenStandards

OpenStandardsOntology

CustomerRequirements

Ontology

NIF PatternOntology

IA

SIOPOntology

BuildingBlocks

BuildingBlocks

Ontology

IA Ontology

Mobility Ontology

NCAT Ontology

NCOICIntegratedOntology

25

1. Lines indicate technical alignment is required and complex and costly to perform2. Semantic Wiki will enable detailed alignment specifications to be developed and captured

SCOPERef Guide

CR WSBB

S&RL Workbook

MECI Workbook

IA Workbook

FORCENet Workbook

CR Ontology

CR Source Information-Documents-- Web sites-- Models-Frameworks-Architectures-R&D-Experiments-Live Exercises

SII Workbook

MBWG Workbook

NCAT

NCAT Engine

NCAT Content

Standards

NCAT Ontology

NIF ver 2

MBWG MNO

MBWG MNE

CR WorkbookSCOPE

Document

SII Source DocsSCOPEOntology

CR WFR

Building Blocks

NCOIC Semantic Wiki Pilot NCOIC Work Product Alignment Relationships Map (Subset)

26

NCOIC Work Group Sample Scenarios

27

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

28

NCOIC Work Groups

+ Customer Requirements Functional Team (CR)

+ Semantic Interoperability (SII)

+ Net-Centric Alignment Testing (NCAT)

+ Net-Centric Interoperability Framework (NIF)

29

WFR

Building Blocks

PFCs/Patterns

NCAT EngineObject Model

NCAT EngineRelational Model

CR Workbooks

CR Data Model

CR Ontology

SCOPE Ref Guide

SCOPE Document

SCOPE Ontology

Semantic Wiki Demo Elements

30

Collaborative Semantic Wiki Environment

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 FTSemantic Wiki

• WFR• Data Collection Workbook• Stakeholder List• CR Ontology• Navy VKR Ontology

SII WGSemantic Wiki

• SCOPE Doc• Reference Guide• SCOPE Ontology• Standards (OWL, WSDL)

NCAT WGSemantic Wiki

• Content Doc• Object Model• Relational Model• Related Standards

NIF WGSemantic Wiki

•Problem Statement Doc•Related standards

…

31

Semantic Wiki Scenario—1

CR 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

32


CR 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)

33

Semantic Wiki Scenario—3 CR/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]

34


SII 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

35

Semantic Wiki Scenario—5 NCOIC 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

36

1. Lines indicate technical alignment is required and complex and costly to perform2. Semantic Wiki will enable detailed alignment specifications to be developed and captured

NCOIC Alignment Relationships Map (Subset)

SCOPERef Guide

CR WSBB

S&RL Workbook

MECI Workbook

IA Workbook

FORCENet Workbook

CR Ontology

CR Source Information-Documents-- Web sites-- Models-Frameworks-Architectures-R&D-Experiments-Live Exercises

SII Workbook

MBWG Workbook

NCAT

NCAT Engine

NCAT Content

Standards

NCAT Ontology

NIF ver 2

MBWG MNO

MBWG MNE

CR WorkbookSCOPE

Document

SII Source DocsSCOPEOntology

CR WFR

Building Blocks

37

Semantic Wiki Scenario—6 NCAT 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

38

Semantic Wiki Scenario—7 NIF Consensus Building

+ NIF consensus building around technical concepts

+ Concepts for functional areas

+ Concepts for PFCs, patterns

39

Background & Schedule

40

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 minute presentation

+ 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)

41


(back-up)

42

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

43

NCOIC Semantic Wiki Pilot Scope+ 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

44

NCOIC Semantic Wiki Pilot BenefitsCapability Benefit1. Semantic wiki work group process

WGs gain faster, more transparent, concept-centric technical collaboration for development, harmonization, life cycle change management, consensus building, and approval of NCOIC work products including cross-product semantic models.

2. Semantic search, query & navigation

End-users and communities of interest (COIs) gain capability to access NCOIC knowledgebase semantically to find more relevant information with less effort.

3. Semantic content authoring, editing, and review

WGs gain capability to upload documents, extract concepts and relationships, explore concepts across sources, and post comments via web or email, with content managed semantically across all sources. Semantic process is flexible, faster, less error prone, than with document exchanges.

4. Semantic modeling WGs gain capability to import schemas & models, edit & refactor them, link concepts & relationships extracted from documents and other sources. WG can exploit semantic models to develop, harmonize, and manage change to concepts across WG products.

5. Semantic harmonization WGs gain capability to flexibly map, align, integrate, restructure concepts across work products, posting comments and documenting the results of harmonization, enabling end-users to access consistent NCOIC knowledge.

6. Semantic change management & versioning

WGs gain savings in time & effort through automated detection and impact assessment changes to and versions of the NCOIC product set.

7. Semantic security & jurisdictional viewing

US & international partners gain comprehensive compliance for access to NCOIC knowledge, governed by applicable law (e.g. ITAR), policy & user role.

45


Results 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.

46

NCOIC Semantic Wiki Pilot (at a glance)

47


+ 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

48

Concept of Operation—1

Set 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.

49

Concept of Operation—2 Research 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

50

Concept of Operation—3 Explore 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.

51

Concept of Operation—4 Collaboratively author, edit work products

+ E.g. -- Create an outline for a work product, extract concepts, & assign authoring responsibilities.

+ Author & edit concepts in draft.

+ Import text, graphics, & pictures.

+ Author new text, revisions to text

+ Update concepts, terms, etc.

+ Build document ontology (I.e., concepts & relationships) while authoring and reviewing.

52

Concept of Operation—5 Build semantic models

+ Identify and extract concepts & relationships of interest in a document as OWL instances.

+ Import RDF/OWL models from external source; also, import schemas of databases and XML documents, and expose them semantically.

+ Author, edit semantic models -- add classes, properties, relationships to named models. Most common semantic models are lists, taxonomies (hierarchies), thesauri, concept models, and ontologies.

+ Associate concept instances with classes in the semantic model.

+ Resulting knowledgebase can be semantically searched, queried, navigated & reported.

53


Review, revise, build consensus, & gain approval

+ Establish a collaborative review process that encourages socialization of concepts and consensus building.

+ Also, a WG can link the work product to a review process setting forth steps, agreements needed, and evidence required for approval.

+ Invite reviewers to read, discuss, comment upon, and revise a WG work product in the wiki.

+ Discuss and comment in the semantic wiki or by semantic email thread that links to concepts in the work product, links to comments from different reviewers, links comments to original text, and makes all contributions visible to all reviewers in real-time.

+ Governance process may culminate with voting, or other annealing process to arrive at consensus.

54

Concept of Operation—7 Harmonize concepts across documents & work groups

+ WGs agree on criteria and collaborative process for cross-product harmonization using the semantic wiki.

+ Edit/review cross-product terminology use, consistency, mapping of concepts, alignment of semantic models for gaps, overlaps, conflicts, differences in architectural perspective.

+ Take appropriate actions to resolve issues. Discuss via semantic email threads and posts to semantic wiki. Document resulting harmonization.

55

Concept of Operation—7 Harmonize concepts across documents & work groups (cont.)

+ As an outcome of harmonization activities:

+ Create and maintain a NCOIC harmonized integrated ontology

+ Create and maintain NCOIC domain ontology specific to WGs:

+ SCOPE Ontology

+ CR Workbook Ontology

+ NCAT Content Ontology

+ NIF Architectural Pattern Ontology

+ Standards Ontology

+ VKR Liaison

56

Concept of Operation—8 Manage changes and versions

+ Use the semantic wiki to help automate management of changes, upgrades, and version of NCOIC work group products.

+ Query how proposed changes in content/ concept/ & semantic model affect NCOIC work products. Query result identifies issues and their ownership & suggests resolutions to traceability, conflicts, misalignments, etc..

+ WGs examine issues. Discussions in semantic wiki or via semantic email threads.

+ Document proposed revisions, resolutions.

+ Collaboratively review, consensus building, and governance process leads to approval and version release.

57

Concept of Operation—9 Provide semantic search, query, and navigation

+ Provide semantic search, query, and navigation that makes all NCOIC information visible and discoverable from a community of interest (COI) and end-user context perspective.

+ Provide semantic search, query, and navigation capabilities that deliver more relevant information, more easily than using conventional text, key word, or web-based information retrieval.

58


Apply security, jurisdictional viewing, & export controls

+ Implement granular/flexible security, role access, governance, jurisdictional viewing, & export controls in the semantic wiki.

+ Set-up a “policy wiki”. Import authorizing regulations, policies, and guidance documents.

+ Identify & extract governance concepts and incorporate these into semantic security models that govern who can do what, and under what circumstances.

+ “Wire” these concepts into semantic wiki behaviors.

+ Simulate & test to ensure full traceability and accountability from policy document, to model,to system behavior.

59


Automate knowledge extraction & reporting

+ Incorporate natural language processing into the semantic wiki

+ Automate knowledge extraction

+ Automate question answering and reporting

60

Backup

61

Mutually Consistent

State

Collaborative

AlignmentActivity

Alignment Relationships

Technical Consensus

Knowledge Capture

Validate NCOIC

Concepts

Discover Sufficiently Granular

Info External COI Query into NCOIC

Not achieving

Failure to identify,Specify, manage

Costly where identified

Failure to integrate

No traceabilityAcross WGs

Not understanding & managing

Not providing

Not providing

Not achieving

NCOIC Work Products

External Initiatives,

Info Sources

NCOIC Problems

62

NCOIC Problem Organizational Wiki Process SWiki Collaboration

1. Not achieving reasonable technical consensus on NCOIC work products and concepts across the NCOIC community

Attract sufficient participation to gain credibility

Utilize a consensus building on-line environment rather than approval process

Provide a single on-line and easily navigable collaborative environment that captures all comments and contributions across all NCOIC content

2. Not understanding and managing the complex complementary relationships across the set of NCOIC work products and information sources used to create them

Create Alignment WG to identify major relationships, tech teams work details

Specify process to manage alignment relationships status

Provide extensible, integrated on-line Semantic Wiki concept model supporting specification of alignment across all NCOIC information content

3. Failure to Identify, specify, and enable specific collaborative activities to align the work products to a mutually consistent state

Mandate Alignment WG to identify and kickoff alignment activities

Specify process for alignment activity to be followed for each cross WG

SWiki specifies a concept model covering all major NCOIC information alignment relationships

4. Costly and inefficient collaborations across working groups

Alignment WG responsible for managing alignment process against alignment map

Specify alignment process to be part of initial COI activity, rather than a catch up activity

Enable WG members to specify alignment concepts as they work their COI work products from the beginning instead of waiting till finished with their own WG product

5. Failure to capture knowledge created by NCOIC associates that investigate, describe and specify the complex concepts comprising the NCOIC work products in a manner that is traceable and that validates the NCOIC developed concepts

NA Makes visible consensus state of each contribution

Semantic Wiki captures all contributed content, makes visible, discoverable within aligned NCOIC information map. Also enables capture of consensus state of each contribution.

6. Inability to support user’s needs to find all relevant NCOIC information and concepts at a sufficient granular level

NA NA Supports complex queries against the internals of NCOIC information work products, not just at a file level.

7. Inability to provide NCOIC information from the perspective of different COIs

NA NA Supports a variety of query views that have vocabulary and query capability oriented to different COIs.

NCOIC Semantic Wiki Solution

63

Proposed Use Cases

A. Required Documents to use in Semantic Wiki Demo - who will provide guidance to demo team

1. SCOPE Document and Reference Guide (J. Yanosy) (Available)

2. NCAT documents (A. Budgor) (Available)

3. CR Workbooks and CR Data Model/Ontology and Stakeholder List (S. Russell) (?)

4. CR Well Formed Requirement/Well Specified Building Block functional area templates (??)

5. NIF documents ver 2 (A. Jones, F. Lebas, ??) (Available)

B. Semantic Wiki Demo Scenarios

1. Capture SCOPE Dimensions and Values concepts from the SCOPE documents (J.Yanosy, H. Polzer)

2. Capture NCAT concepts from NCAT documents (A. Budgor, Dixit, A. Meilich, ??)

3. Capture Requirements Dimensions and Values concepts from the CR Team's Well Formed Requirement/Well Specified Building Block

4. Capture Global Aspects Dimensions and Values of PFCs from NIF v1 document

5. Capture DoD NR-KPP and Network Centric metrics work from OFT, JFCOM, DISA and W2COG documents (optional)

6. Harmonize and relate selected CR, SCOPE and NCAT (and optionally NR-KPP) Concepts through collaborative aspects of Semantic Wiki (J. Yanosy, A. Budgor, V. Dixit, A. Meilich, ??)

7. Capture concepts from the Customer Requirements (CR) Workbooks (S. Russell)

8. Harmonize and related selected Customer Requirements Workbook concepts with Harmonized SCOPE/NCAT Concepts (S. Russell, J. Yanosy)

9. Capture NIF ver 2 concepts from documents and email threads (A. Jones, F. Lebas)

10. Capture concepts from a few selected standards, WSDL, IPv6,

11. Relate standards concepts to SCOPE/NCAT/CR harmonized concepts (All)

12. Illustrate continuous lifecycle management or governance within Semantic Wiki (Modification of one or more concepts affecting multiple WGs)

C. General Demo Capabilities

1. Semantic concept capture from documents and email

2. WG multi-contributor development of semantic concepts in a WG using a WG specific Semantic Wiki

3. Collaborative development to harmonize concepts across WGs in related work products in an multi-WG Semantic Wiki

4. Demonstrate governance or lifecycle management of Semantic Wiki

64

Semantic Wiki Pilot Goals

+ Manage Collaborative Alignments Across WGs

+ Support CR, SII, NCAT NCOIC working groups consensus building

+ Create SWiki Concepts to build and archive WG consensus development

+ Early identification of alignment activities across WGs

+ Creation of ontologies and semantic knowledge base for each COI

+ Evaluate Semantic Wiki as Cross WG collaborative environment for:

+ Cross organizational information product alignment activities

+ Capturing knowledge of experts as thy build consensus on technical concepts

+ Creating and managing information concepts in each COI

+ Extraction and analysis of source information and linking to WG technical concepts (Standards, Customer Docs, etc.)

+ Knowledge version management

+ Semantic Ontologies and Knowledge Bases

+ Evaluate Semantic Wiki to develop semantic ontologies related to SWiki concepts

+ Evaluate ability to create models of models to better align and harmonize NCOIC information deliverables

+ Develop COI semantic knowledge base that evolves as the NCOIC evolves NCO concepts

+ Support complex semantic queries against the SWiki, Ontologie, and Knowledge Base

65

Semantic Wiki Pilot Proposal

+ Purpose

+ Rationale

+ Scope

+ Participants and roles

+ Approach

+ Schedule of deliverables

+ Benefits

+ Costs

67

Presenter Bios

68

Semantics build on things we already know

Sounds like Metadata?

Sounds like Taxonomy and Vocabularies?

What more do Semantics provide?

+Similar…

+Metadata serves the implementation paradigms of the system

+Is the semantics of the data structures in a system, e.g.:

– Relational – ERD

– Object oriented – UML

– XML documents – XSD XMI

+Close…

+Taxonomy provides a hierarchy of terms of concepts from a social point of view

+Permits only one accepted notion of a term:

– Brother? family, or religion, or union, or…

+Context

+Multiple points of view

+Inferred relationships

+Causality

+Granularity

2 NCOIC Semantic Wiki Aaron Budgor Bruno Carron Stephan Chevalier Ken Cureton Mills Davis Vish Dixit...

Documents

Transcript of 2 NCOIC Semantic Wiki Aaron Budgor Bruno Carron Stephan Chevalier Ken Cureton Mills Davis Vish Dixit...