Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

Semantic Cloud Computing with Open Linked Data (RDF) Technical or by XR4Ulx5

VIEWS: 7 PAGES: 29

									                                              Services Working Group         Semantic Cloud Computing
                                                        or                     with Open Linked Data
                                             Cloud Computing Working            (RDF) Technical or
                                                       Group                     Capability Pattern




 Semantic Cloud Computing with Open Linked Data
  using Resource Description Framework (RDF) in
    lieu of XML Technical or Capability Pattern
                  (Alias Cloud Computing and SOA Technical Pattern)

Abstract: The latest NCOIC Pattern Guidance (see Appendix for requirements and comments) has been
used to produce a technical pattern for Cloud Computing and SOA in general and more specifically for
Semantic Cloud Computing with Open Linked Data. A specific example of this is the Open Group
Technical Standard for a Service-Oriented Ontology (1) in RDF (OWL) format (2). This pattern draws on
the considerable expertise of the participants in the Federal Cloud Computing, Data, and SOA
Communities of Practice (3, 4, & 5). Work on this pattern also includes a Web 2.0 platform (6) pilot to
show the relationships between the following: NCOIC Lexicon, SCOPE, and All Hazards Alerts and
Warnings (formerly IERS) Pattern (NEER IPT), as a possible way to show the relationships between all
the NCOIC patterns and other key NCOIC product documents (7).


                                               October 29, 2009

   Brand Niemann, United States Environmental Protection Agency et al

                                                Version History
  Version Number                              Description                           Author
 Version V0.1-2009-   This is the original documentation for this pattern.   Brand Niemann
 10-15 (Draft)
 Version V0.1.1-      Formatted per NCOIC                                    Jason Lee/Allen Jones
 2009-11-01




                                         Not Approved for Public Release
                        Limited distribution to Author, Services Group Chair & associates



Clearance                          Version
Working Group Consensus                         Draft v1.1                                  Page 1 / 29
                                                            Services Working Group                        Semantic Cloud Computing
                                                                      or                                    with Open Linked Data
                                                           Cloud Computing Working                           (RDF) Technical or
                                                                     Group                                    Capability Pattern


                                                               Table of Contents
1.   Description .............................................................................................................................................3
  1.1     Problem Statement & Context .......................................................................................................5
     1.1.1.       Problem Statement .............................................................................................................5
     1.1.2.       Context ...............................................................................................................................6
  1.2     Expected Benefits...........................................................................................................................7
  1.3     Participants ...................................................................................................................................10
     1.3.1         Actors ..............................................................................................................................10
     1.3.2         Interfaces .........................................................................................................................10
  1.4     Pre-Conditions .............................................................................................................................11
  1.5     Structure .......................................................................................................................................12
  1.6     Behavior .......................................................................................................................................13
  1.7     Post-Conditions ............................................................................................................................13
2. Implementation Guidance ....................................................................................................................14
  2.1     Standards ......................................................................................................................................14
  2.2     Expert Advice...............................................................................................................................15
     2.2.1        Lessons Learned ...............................................................................................................15
     2.2.2        Constraints & Opportunities ............................................................................................15
  2.3     Known Uses .................................................................................................................................17
  2.4 Potential Capability ............................................................................................................................17
  2.5     Related Patterns ............................................................................................................................18
  2.6     References ....................................................................................................................................22
3. Verification ..........................................................................................................................................24
4. Appendices (Optional) .........................................................................................................................25
  a. Supporting Information ....................................................................................................................25
  b. Additional Implementation Guidance ..............................................................................................25
  c. Adherence to Relevant NCOIC Documents ....................................................................................27
  d. Validation Artifacts and/or Evidence ...............................................................................................27
  e. Vision for the future .........................................................................................................................27




Clearance                                      Version
Working Group Consensus                                       Draft v1.1                                                    Page 2 / 29
                                         Services Working Group          Semantic Cloud Computing
                                                   or                      with Open Linked Data
                                        Cloud Computing Working             (RDF) Technical or
                                                  Group                      Capability Pattern




1. Description
   The following sub-sections define the NCP, its context, and the manner in which it is
used. It provides the detail necessary for a user to apply the NCP.
    NCOIC is a global organization, with membership open to those who wish to apply the vast potential
of network centric technology to the operational challenges faced by our nations and their citizens (8).
The NCOIC Mission is to facilitate the global realization of Network Centric Operations, enable
interoperability across the spectrum of joint, interagency, intergovernmental, and multinational industrial
and commercial operations (8). The NCOIC develops patterns to provide practical guidance for creating
systems with the desired net-centric capabilities in order to mitigate specific net-centric interoperability
problems.
According to Wikipedia, cloud computing is the provision of dynamically scalable and often virtualized
resources as a service over the Internet on a utility basis. Users need not have knowledge of, expertise in,
or control over the technology infrastructure in the "cloud" that supports them. Cloud computing services
often provide common business applications online that are accessed from a web browser, while the
software and data are stored on the servers (see figure below) (11).




According to the United States’ NIST (National Institute for Standards & Technology) (12), cloud
computing is a model for enabling convenient, on-demand network access to a shared pool of
configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be
rapidly provisioned and released with minimal management effort or service provider interaction. This
cloud model promotes availability and is composed of five essential characteristics, three service models,
and four deployment models. It is noted that cloud software takes full advantage of the cloud paradigm by
being service oriented with a focus on statelessness, low coupling, modularity, and semantic
interoperability.



Clearance                       Version
Working Group Consensus                    Draft v1.1                                Page 3 / 29
                                        Services Working Group        Semantic Cloud Computing
                                                  or                    with Open Linked Data
                                       Cloud Computing Working           (RDF) Technical or
                                                 Group                    Capability Pattern



The Federal CIO, Vivek Kundra, launched a Federal Cloud Computing initiative July 15th based on three
service delivery models that together create the ‘cloud’ (see figure below) (13). The Whitehouse Blog of
the formal launch September 15th stated the following (14): “We launched Apps.gov to help continue the
President’s initiative to lower the cost of government operations while driving innovation within
government (in speech at the NASA Ames Research Center).
Apps.gov is an online storefront for federal agencies to quickly browse and purchase cloud-based IT
services, for productivity, collaboration, and efficiency. However, federal agencies and departments
encounter many difficulties in deploying new IT services and products. Procurement processes can be
confusing and time-consuming. Security procedures are complex, costly, lengthy and duplicative across
agencies. Our policies lag behind new trends, causing unnecessary restrictions on the use of new
technology. Past practices too often resulted in inefficient use of purchased IT capabilities across the
federal government. We are dedicated to addressing these barriers and to improving the way government
leverages new technology. We are just beginning this undertaking, and it will take time (e.g. 10 years)
before we can realize the full potential of cloud computing. Like with Data.gov, Apps.gov is starting
small – with the goal of rapidly scaling it up in size. Along the way, we will need to address various
issues related to security, privacy, information management and procurement to expand our cloud
computing services.”




Clearance                      Version
Working Group Consensus                  Draft v1.1                               Page 4 / 29
                                         Services Working Group         Semantic Cloud Computing
                                                   or                     with Open Linked Data
                                        Cloud Computing Working            (RDF) Technical or
                                                  Group                     Capability Pattern


1.1 Problem Statement & Context
Address the history of the problem and the overall approach.
    In software engineering, a design pattern is a general reusable solution to a commonly occurring
problem in software design. A design pattern is not a finished design that can be transformed directly into
code. It is a description or template for how to solve a problem that can be used in many different
situations (9). In SOA, patterns describe solutions to a common problem individually documented in a
consistent format and usually as part of a larger collection (10).


1.1.1.         Problem Statement
Describe the problem the NCP solves within the appropriate context (described next), in
other words, why is this pattern needed? Include the primary NCP goal and the reason
for using it. Note that several domains can be addressed by a single NCP.




Clearance                       Version
Working Group Consensus                   Draft v1.1                                Page 5 / 29
                                        Services Working Group        Semantic Cloud Computing
                                                  or                    with Open Linked Data
                                       Cloud Computing Working           (RDF) Technical or
                                                 Group                    Capability Pattern


President's FY2010 Budget includes cloud computing (15 - see May 7, 2009: Improving Innovation,
Efficiency, and Effectiveness in Federal IT).

According to Wikipedia, SOA (Service Oriented Architecture) (see figure below) (16). service-orientation
requires loose coupling of services with operating systems, and other technologies that underlie
applications. SOA separates functions into distinct units, or services, which developers make accessible
over a network in order to allow users to combine and reuse them in the production of applications. These
services communicate with each other by passing data from one service to another, or by coordinating an
activity between two or more services. ZapThink (17) considers cloud computing to essentially be a
subset of SOA – or in other words, cloud computing needs a SOA.


1.1.2.        Context
Describe the context or scenario in which the NCP is applicable, and conditions under
which the NCP is to be used. Context includes the environmental entities with which the
NCP may interact. Also state the environmental conditions required for this NCP to be
applied.
     – For an Operational NCP, describe the mission domain and the operational
        entities.
     – For a Capability NCP, describe a scenario or use case that may explain both
        operational and technical entities
     – For a Technical NCP explain the technical goal and include the technical entities
Any net-centric principles from the NIF NSD-RM and applicable Specialized
Frameworks supported by this NCP should be identified in this section.
   Keep this section short, with details in the precondition section. or in an Appendix.




Clearance                      Version
Working Group Consensus                  Draft v1.1                               Page 6 / 29
                                          Services Working Group          Semantic Cloud Computing
                                                    or                      with Open Linked Data
                                         Cloud Computing Working             (RDF) Technical or
                                                   Group                      Capability Pattern


1.2 Expected Benefits
      Describe the advantages accruing from the use of this NCP. This paragraph
should provide the users of the NCP a reason for following this pattern as opposed to
other guidance or nothing at all.
Again, according to Wikipedia (11), cloud computing users can avoid capital expenditure on hardware,
software, and services when they pay a provider only for what they use. Consumption is usually billed on
a utility (e.g. resources consumed, like electricity) or subscription (e.g. time based, like a newspaper)
basis with little or no upfront cost. A few cloud providers are now beginning to offer the service for a flat
monthly fee as opposed to on a utility billing basis. The diagram below shows the economics of cloud
computing versus traditional IT, including capital expenditure (CapEx) and operational expenditure
(OpEx).




According to the new Apps.gov Web site (18) (see screen capture below), the features and benefits of
cloud computing are as follows (19):

Significant Cost Reduction: Cloud computing is available at a fraction of the cost of traditional IT
services, eliminating upfront capital expenditures and dramatically reducing administrative burden on IT
resources.

Increased Flexibility: Cloud computing provides on-demand computing across technologies, business
solutions and large ecosystems of providers, reducing time to implement new solutions from months to
days.




Clearance                        Version
Working Group Consensus                    Draft v1.1                                 Page 7 / 29
                                         Services Working Group         Semantic Cloud Computing
                                                   or                     with Open Linked Data
                                        Cloud Computing Working            (RDF) Technical or
                                                  Group                     Capability Pattern


Access anywhere: You are no longer tethered to a single computer or network. You can change computers
or move to portable devices, and your existing applications and documents follow you through the cloud.

Elastic scalability and pay-as-you-go: Add and subtract capacity as your needs change. Pay for only what
you use.

Easy to implement: You do not need to purchase hardware, software licenses or implementation services.

Service quality: Cloud service providers offer reliable services, large storage and computing capacity, and
24/7 service and up-time.

Delegate non-critical applications: Cloud computing provides a way to outsource non-critical applications
to service providers, allowing agency IT resources to focus on business-critical applications.

Always the latest software: You are no longer faced with choosing between obsolete software and high
upgrade costs. When the applications are web-based, updates are automatic and are available the next
time you log into the cloud.

Sharing documents and group collaboration: Cloud computing lets you access all your applications and
documents from anywhere in the world, freeing you from the confines of the desktop and facilitating
group collaboration on documents and projects.




Clearance                       Version
Working Group Consensus                   Draft v1.1                                Page 8 / 29
                                 Services Working Group   Semantic Cloud Computing
                                           or               with Open Linked Data
                                Cloud Computing Working      (RDF) Technical or
                                          Group               Capability Pattern




Clearance                 Version
Working Group Consensus             Draft v1.1                      Page 9 / 29
                                        Services Working Group        Semantic Cloud Computing
                                                  or                    with Open Linked Data
                                       Cloud Computing Working           (RDF) Technical or
                                                 Group                    Capability Pattern




 1.3 Participants
Identify the actors (performers or participants, and systems etc) that interface with a
supplier’s product or service (Building Block).

Participants in this pattern include members of the NCOIC Services Work Group and NCOIC Cloud
Computing Team as well as participants in the Federal Cloud Computing, Data, and SOA Communities of
Practice (see References 3, 4, & 5). Participation in this pattern is open to all who are willing to make
constructive contributions going forward.

An initial presentation of this pattern was given at the NCOIC meetings during September 21-23, 2009
(20 and 21).

1.3.1         Actors
       Describe precisely the actors that require this operation/capability/technology to
achieve their goal. Include indirect actors that may provide input, or receive output, as
a result of NCP use, with an appropriate method to show the actors that are associated
with the NCP:
       Views & Viewpoints (pictures) are worth a thousand words if the viewer
understands the visual methodology:
   o For an Operational NCP, describe how people and systems (both internal and
      external) interact to accomplish their activities (military operations or business
      objectives) in the given mission context
   o For a Capability NCP, describe how people and external systems invoke (or use or
      supply data to, or receive data from) the capability to achieve the required
      functions
For a Technical NCP, Describe how people and external systems interact with the
system or service that incorporates the NCP.

1.3.2         Interfaces
Identify and describe specific characteristics of interfaces between various actors. Also
identify interfaces between actors and the system(s) or services associated with the NCP.
This section addresses static interfaces rather than dynamic interfaces, defined in
Section 1.5 Behavior.


Clearance                      Version
Working Group Consensus                  Draft v1.1                             Page 10 / 29
                                      Services Working Group   Semantic Cloud Computing
                                                or               with Open Linked Data
                                     Cloud Computing Working      (RDF) Technical or
                                               Group               Capability Pattern




 1.4 Pre-Conditions
Describe constraints and assumptions for each NCP as follows:
    Operational NCP: Include a description of operational
        state(s) that exist before the NCP is applied
    Capability NCP: Include descriptions of conditions that must be in place before
       the capability can be used
    Technical NCP:
      o Infrastructure conditions that must be available for the technology to function
          properly.
      o KPP of the system prior to application of the NCP
Address the scope of the NCP, i.e., what are the boundaries of this NCP. In other words,
how much of the problem does this NCP address? List known/specified scope
limitations for the NCP context, at least at the top level of SCOPE dimensions.
To be added in next version.




Clearance                      Version
Working Group Consensus                  Draft v1.1                    Page 11 / 29
                                     Services Working Group       Semantic Cloud Computing
                                               or                   with Open Linked Data
                                    Cloud Computing Working          (RDF) Technical or
                                              Group                   Capability Pattern



 1.5 Structure
       The structure describes logical static elements supporting the understanding and
the implementation of the NCP.
    Identify NCP’s bounds.
    Specify main objects (components, functions and services) used in this NCP and
      their roles and relationships in the design.
    Distinguish between provided and consumed functions and services.
This attribute provides a description of the static structure present within the NCP.
Use an appropriate method to show the structure of the operation/capability/technology
as applicable to its use, such as: a block diagram of components
A new eGov Cloud Computing Enterprise Architecture Based on ArchitecturePlus Seminar, August 13,
2009 (22), was suggested at the recent NCOIC Cloud Computing Workshop, September 21, as follows
(23):

                                   Semantic
Objective         Product          Technology/          Example
                                   Semantic Web
Transparency,
                  New Web Sites    Semantic Search    Semantic
Openness, &
                  (24)             (25)               Government (26)
Collaboration
                                                    eGov Ontology &
Better Data       Data Models (27) Ontologies (28)
                                                    DRM 3.0 (29)
Better Process    Business Process Open Linked Data Open Linked Data
Integration       Models (30)      (31)             (32)
                                  Semantic Search
Better            Cloud Computing                     Cambridge
                                  and Open Linked
Infrastructure    (33)                                Semantics (35)
                                  Data (34)




Clearance                    Version
Working Group Consensus                Draft v1.1                           Page 12 / 29
                                      Services Working Group   Semantic Cloud Computing
                                                or               with Open Linked Data
                                     Cloud Computing Working      (RDF) Technical or
                                               Group               Capability Pattern



 1.6 Behavior
   Describe the dynamic interaction of the structure elements, interfaces, and actors
     described in the prior sections; in other words, what major interactions are
     required to achieve the intent of the NCP?
   Describe the major steps to accomplish the operation or capability NCP or the
     sequence of activities and interactions of components in the technical NCP
Suggest using an appropriate method to show interactions in the
operation/capability/technology, such as: flow diagrams of procedural steps.
To be added in next version


 1.7 Post-Conditions
Describe results, consequences, outputs and any potential side-effects in the
operation/capability/technology using this NCP
   Operational NCP: Include descriptions of operational conditions resulting from
     the operational scenario
   Capability NCP: Include a description of the conditions that result from the use of
     the capability
   Technical NCP: include
     • States and modes resulting from use of the technology
KPP of the system after the application of the NCP

To be added in next version.




Clearance                      Version
Working Group Consensus                  Draft v1.1                    Page 13 / 29
                                         Services Working Group         Semantic Cloud Computing
                                                   or                     with Open Linked Data
                                        Cloud Computing Working            (RDF) Technical or
                                                  Group                     Capability Pattern




2. Implementation Guidance
This section describes standards contained in the NCP, how to apply them, and expert
guidance in implementing an NCP.


 2.1 Standards
Describe required standard(s), including version(s) and optional variations applied in
the operations/capability/ technology implementation. Specified protocols should be
associated with selected standard(s)
   Use Open or Commercial Standards such as IETF, ITU, IEEE, ISO, OMG, AIAA
   Do not use Proprietary Standards
   Use DoDAF / MoDAF / NAF / AusDAF diagrams if appropriate
   Minimize use of special or country unique defense standards e.g., US DoD or
      NATO classified or restricted distribution standards


A key excerpt from the unpublished draft Data.gov Concept of Operations (36) is:

As semantically enabled data concepts are matured and pilots are successfully executed, the Data.gov
team will provide specific guidance to help agencies implement semantic markup within their datasets.
Specifically, the Data.gov team will not only leverage semantically enabled techniques within the
Data.gov site, but will help agencies implement semantically enabled data within their datasets so that the
datasets can be better leveraged not only by Data.gov but also by other end users of the data.

Semantically enabled techniques include the use of the World Wide Web Consortium’s RDF and OWL
Standards (37). Some key concepts of RDF and OWL are:

Works for structured, semi-structured, and un-structured information.
Metadata and data travel together.
Machine - processible.
Supports relational – like joins over the network.
Inferencing /reasoning (still in development for scalability).




Clearance                       Version
Working Group Consensus                   Draft v1.1                               Page 14 / 29
                                   Services Working Group     Semantic Cloud Computing
                                             or                 with Open Linked Data
                                  Cloud Computing Working        (RDF) Technical or
                                            Group                 Capability Pattern



 2.2 Expert Advice


2.2.1        Lessons Learned
Describe expert advice, lessons learned, and best practices that Subject Matter Experts
(SMEs) recommend for successful implementation of the standard(s) applicable to this
NCP, especially:
   Known cost / schedule / performance risks
   Interoperability failure Root causes using specified standards in prior and current
   systems (at time of release)



2.2.2        Constraints & Opportunities
      This section captures any constraints on the solution recommended by the SMEs
that may affect interoperability. Without constraints, a single set of standards would be
used and implemented in the same manner. Reality dictates there are factors that
constrains the use of simple solutions or limits the ability of certain solutions to achieve
interoperability.
      The recommendations by the NCP author (i.e., the SMEs) might include invoking
certain optional behavior or features of the standards; implementing more than one
standard; providing gateways, bridges, or translators; or possibly even noting that
certain types of users/systems might be limited in their ability to interoperate if a
reasonable solution was not available. Other possible examples of "constraints" might
include: performance, security and safety requirements/considerations.
Opportunities:
Opportunities capture ways to achieve significant improvements in interoperability over
previous/other approaches, or to identify ways to mitigate some of the restrictions
imposed by the constraints. For example, wrapping an existing legacy system to provide
services in a SOA enterprise without having to redesign the legacy system.




Clearance                  Version
Working Group Consensus              Draft v1.1                        Page 15 / 29
                                        Services Working Group        Semantic Cloud Computing
                                                  or                    with Open Linked Data
                                       Cloud Computing Working           (RDF) Technical or
                                                 Group                    Capability Pattern




An Enterprise Architecture Evolution / Innovation Roadmap Based on ArchitecturePlus Seminar, October
15, 2009 (38), has been suggested that uses semantic cloud computing with open linked data is as follows
(39):

Topic              Current            Next                Future

Enterprise        Segment            Collaborative        SOA & Semantic
Architecture (40) Architectures (41) Target               Interoperability
                                     Architectures (42)   Patterns (43)
Data.gov (44)     Metadata Catalog New CONOPS             Open Linked Data
                  (45)               (46)                 (47)

Enterprise         TROUX, etc. (49) Social Networking Integration of
Architecture Tools                  (50)              Current and Next
(48)                                                  Using (47) (51)
Implementation Web Services (53) SOA (54)             Integration of
(52)                                                  Current and Next
                                                      Using (47) & (51)
                                                      (55)




Clearance                      Version
Working Group Consensus                  Draft v1.1                             Page 16 / 29
                                       Services Working Group       Semantic Cloud Computing
                                                 or                   with Open Linked Data
                                      Cloud Computing Working          (RDF) Technical or
                                                Group                   Capability Pattern



 2.3 Known Uses
List missions and/or systems which use or have used the approach recommended in this NCP
According to Kevin Jackson (56), the known uses cases of government cloud computing are as follows:
United States
       Federal Chief Information Officers Council
       Data.gov & IT Dashboard
       Defense Information Systems Agency (DISA)
       Rapid Access Computing Environment (RACE)
       US Department of Energy (DOE)
       Magellan
       General Services Administration (GSA)
       Apps.gov
       Department of the Interior
       National Business Center (NBC) Cloud Computing
       NASA Nebula
       National Institute of Standards and Technology (NIST)
United Kingdom
       G-Cloud
European Union
       Resources and Services Virtualization without Barriers Project (RESERVOIR)
Canada
       Canada Cloud Computing
       Cloud Computing and the Canadian Environment
Japan
       The Digital Japan Creation Project (ICT Hatoyama Plan)
       The Kasumigaseki Cloud

 2.4 Potential Capability
Identify any portions of the NCP which can have increased capability without
interfering with interoperability:
    Operational NCP: may include mission flexibility
    Capability NCP: may include capability variation
    Technical NCP: may include additional capability (such as use of an optional
      extension of a standard) which if excluded or included would not impact
      interoperability of systems incorporating Building Blocks from different vendors
Also refer to section NIF Section A.1.7.5.4
To be added in next version.


Clearance                      Version
Working Group Consensus                  Draft v1.1                           Page 17 / 29
                                         Services Working Group    Semantic Cloud Computing
                                                   or                with Open Linked Data
                                        Cloud Computing Working       (RDF) Technical or
                                                  Group                Capability Pattern



 2.5 Related Patterns
Identify any related NCPs or associated NCPs.

According to a recent NCOIC Executive Council Briefing (see Ken Cureton, Executive Overview of
NCOIC Net-Centric Patterns, NCOIC Executive Council Session, September 21-25, 2009 Fairfax, VA,
Approved for Public Release Distribution Unlimited, NCOIC-Patt Workshop-FebPlen-20090225. 19
slides), the status of pattern work is as follows:

Completed Formal Review:

Asset Allocation Planning Pattern (S&RL IPT)
Simple and Extensible Email Services Technical Pattern (Specialized Frameworks FT)
Secure Formatted Information Exchange Gateway Technical Pattern (IA WG)

In Formal Review now:

Land FFT Gateway (NFFI Standard Guidance) Technical Pattern (C3 IPT and SF FT)
NC Services Framework V2.1 (Services WG)
Core Network Access (CNA) Technical Pattern (IA WG)
Legacy Services (Integration) Capability Pattern (Services WG)

Expected to enter Formal Review next:

Integrated Middleware Environment (IME) Capability for Live/Virtual/Constructive Simulations (M&S
AHWG)
Distributed Interactive Simulation (DIS) Technical Pattern
High-Level Architecture (HLA) Technical Pattern
Design Time Service Integration Technical Pattern (SF FT)
Disconnected Intermittent Limited (DIL) Communications Technical Pattern (Services WG)
Space Air Ground maritime (SAGM) Operational Pattern (MN WG)
Standard Management Framework (OS WG)
All Hazards Alerts and Warnings (formerly IERS) Pattern (NEER IPT)
Risk Management Framework Pattern (IA WG)
Resource Tracking Information Exchange Pattern (C3 IPT)

In Work by IPTs:

Flight Object Dissemination Capability Pattern (Aviation IPT)



Clearance                      Version
Working Group Consensus                  Draft v1.1                          Page 18 / 29
                                       Services Working Group       Semantic Cloud Computing
                                                 or                   with Open Linked Data
                                      Cloud Computing Working          (RDF) Technical or
                                                Group                   Capability Pattern


Weather Data Dissemination Capability Pattern (Aviation IPT)Resource Tracking Information Exchange
Pattern
(C3 Interoperability IPT > NATO FFT AHWG)
Information Dissemination Shared Database
(C3 Interoperability IPT > MAJIIC)
Common Operative Picture COP
(C3 Interoperability IPT > NATO)
FFT Services and Architecture
(C3 Interoperability IPT > NATO FFT AHWG)
Initial All Hazards, All Warnings (NEER IPT > AHAW)
Integrated Emergency Response Services (NEER IPT > IERS)

It further states that “Patterns are not contained in the NIF, (but will) will be stored in an online
Repository in the near future. (end of Ken Cureton quote).A Cloud Computing Reference Model (CC-
RM) Overview (see figure below), has been provided recently by Eric Marks (57) and (58) which may be
summarized as follows:
Comprised of four sub-models
Pragmatic approach to Cloud modeling, architecture and deployment
Enables mapping and alignment of SOA Reference Architectures to Cloud RM/RA
Provides a foundation for Cloud adoption and Cloud value for your enterprise
Will enable rapid Cloud value to be harnessed for our Enterprise




Clearance                     Version
Working Group Consensus                 Draft v1.1                            Page 19 / 29
                                          Services Working Group         Semantic Cloud Computing
                                                    or                     with Open Linked Data
                                         Cloud Computing Working            (RDF) Technical or
                                                   Group                     Capability Pattern




Work on this pattern has included a Web 2.0 platform pilot to show the relationships between the
following:

All Hazards Alerts and Warnings (formerly IERS) Pattern (NEER IPT)
NCOIC Lexicon
NCOIC SCOPE

as a possible way to show the relationships between all the NCOIC patterns and other key product
documents (see http://networkcentricity.wik.is) (see figure below).

The 2009 Federal IT Summit Cloud Computing session laid out more details for the management,
architecture, and infrastructure of the new administration’s initiative (59) and the slides will be made
available soon (60). We are tracking this for updating this pattern.




Clearance                       Version
Working Group Consensus                    Draft v1.1                               Page 20 / 29
                                 Services Working Group   Semantic Cloud Computing
                                           or               with Open Linked Data
                                Cloud Computing Working      (RDF) Technical or
                                          Group               Capability Pattern




Clearance                 Version
Working Group Consensus             Draft v1.1                    Page 21 / 29
                                     Services Working Group      Semantic Cloud Computing
                                               or                  with Open Linked Data
                                    Cloud Computing Working         (RDF) Technical or
                                              Group                  Capability Pattern



 2.6 References
(1) http://www.opengroup.org/projects/soa-ontology/doc.tpl?gdid=16940
(2) http://www.opengroup.org/projects/soa-ontology/uploads/40/16940/draft200.owl
(3) http://federalcloudcomputing.wik.is
(4) http://federaldata.wik.is
(5) http://federalsoa.wik.is
(6) http://www.mindtouch.com/MindTouch_Deki/Features/Architecture
(7) http://networkcentricity.wik.is
(8) https://www.ncoic.org/about/overview/Overview_10July09.pdf
(9) http://en.wikipedia.org/wiki/Design_pattern_(computer_science)
(10) http://www.soaglossary.com/design_pattern.asp
(11) http://en.wikipedia.org/wiki/Cloud_computing
(12) http://csrc.nist.gov/groups/SNS/cloud-computing/index.html
(13) http://www.ndu.edu/irmc/ilss/CCppts/visuals02-kundra.ppt
(14) http://www.whitehouse.gov/blog/Streaming-at-100-In-the-Cloud/
(15) http://www.whitehouse.gov/omb/budget/fy2010/assets/crosscutting.pdf
(16) http://en.wikipedia.org/wiki/Service-oriented_architecture
(17) http://www.zapthink.com/report.html?id=ZTP-0353
(18) http://apps.gov
(19)
https://apps.gov/cloud/advantage/information/page.do?BV_UseBVCookie=Yes&keyName=CLOUD_FA
Q
(20)
http://federalcloudcomputing.wik.is/@api/deki/files/97/=BrandNiemannCloudComputingWorkshop09212
009.ppt
(21) http://federalcloudcomputing.wik.is/@api/deki/files/98/=BrandNiemannsServicesWG09222009.ppt
(22) http://semanticommunity.wik.is/Federal_Chief_Architects_Forum/2009_August_13
(23) http://federaldata.wik.is/@api/deki/files/103/=BrandNiemann09112009.ppt
(24) http://www.usaspending.gov, http://www.recovery.gov, http://www.data.gov, etc.
(25) http://expert1.expertsystem.us.com/semgov/
(26) http://semanticgovernment.org (in process - see (25))
(27) http://en.wikipedia.org/wiki/Data_model
(28) http://en.wikipedia.org/wiki/Ontology_(information_science)
(29) http://www.oegov.org/ and
http://federaldata.wik.is/Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form
(30) http://en.wikipedia.org/wiki/Business_process_modeling
(31) http://en.wikipedia.org/wiki/Linked_Data
(32) http://linkeddata.org
(33) http://en.wikipedia.org/wiki/Cloud_computing



Clearance                    Version
Working Group Consensus                Draft v1.1                          Page 22 / 29
                                       Services Working Group       Semantic Cloud Computing
                                                 or                   with Open Linked Data
                                      Cloud Computing Working          (RDF) Technical or
                                                Group                   Capability Pattern


(34) http://semanticommunity.net
(35) http://www.cambridgesemantics.com
(36) Data.gov Concept of Operations, Office of E-Government and IT Office of Management and Budget,
Powered by the Federal Chief Information Officers Council and the Federal Enterprise Architecture,
Version 0.93, September 3, 2009, 34 pages.
(37) http://www.w3.org/2009/Talks/0615-SanJose-tutorial-IH/Slides.ppt
(38) http://semanticommunity.wik.is/Federal_Chief_Architects_Forum/2009_October_15
(39) http://federaldata.wik.is/@api/deki/files/123/=BrandNiemann10162009.ppt
(40) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx
(41) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx
(42) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx
(43) September 23rd and October 5th: http://kevinljackson.blogspot.com/2009/09/ncoic-holding-full-day-
cloud-computing.html and http://federalsoa.wik.is/
(44) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx
(45) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx Note: Over 500 Data Sets and
Over 100,000 Geospatial Objects (Maps, Photos, etc.)
(46) http://gcn.com/articles/2009/09/10/kshemendra-paul-keynote.aspx
(47) http://www.w3.org/TR/2009/WD-gov-data-20090908/ Also
http://www.w3.org/2007/eGov/IG/wiki/Main_Page and
http://semweb.meetup.com/31/calendar/11017956/
(48) http://en.wikipedia.org/wiki/Enterprise_architecture
(49) http://www.troux.com/products/troux_eagov/
(50) http://en.wikipedia.org/wiki/Social_network_service
(51)
http://federalcloudcomputing.wik.is/@api/deki/files/94/=BrandNiemannCloudComputingforEAWG08272
009.ppt
(52)
(53) http://en.wikipedia.org/wiki/Web_service and http://web-services.gov
(54) http://en.wikipedia.org/wiki/Service-oriented_architecture
(55) Ira Grossman, Co-chair, Chief Architect Forum and Chief Architect, FEMA/DHS, at EA 2009
Conference, September 10th. See http://1105govinfoevents.com/EventOverview.aspx?Event=EA09
(56) Kevin Jackson, Cloud Computing Webex Media Briefing, October 27, 2009, 14 slides. Includes
Lockheed Martin Cloud Computing Research Investigation (slides 8-10).
(57)
http://federalsoa.wik.is/@api/deki/files/91/=10_15___AgilePath_SOA_eGov_October_5_2009_v3_Publi
c.pdf
(58) Cloud Computing Reference Model (CC-RM) Overview, October 8, 2009, Eric Marks, AgilePath, 45
pages. http://federalsoa.wik.is/@api/deki/files/109/=AgilePath_Cloud_Ref_Model_Webinar.pdf
(59) Same as (15)
(60) http://www.cio.gov



Clearance                     Version
Working Group Consensus                 Draft v1.1                            Page 23 / 29
                                    Services Working Group   Semantic Cloud Computing
                                              or               with Open Linked Data
                                   Cloud Computing Working      (RDF) Technical or
                                             Group               Capability Pattern




3. Verification
This section’s intent is to provide Building Blocks suppliers a minimum set of
requirements to ensure that their solutions conform with the guidance, standards,
specifications and protocols contained within the NCP. It also identifies which
methodologies and indicators of conformance the Building Blocks suppliers must
provide to show conformance with the pattern for NCOIC Building Blocks certification.
Verification must be accomplished via specified methods such as Analysis, Test,
Demonstration, Inspection, etc.
This section should indicate the allowable methods as well as a definition for each
method listed.
To be added in the future.




Clearance                    Version
Working Group Consensus                Draft v1.1                    Page 24 / 29
                                                Services Working Group             Semantic Cloud Computing
                                                          or                         with Open Linked Data
                                               Cloud Computing Working                (RDF) Technical or
                                                         Group                         Capability Pattern




4. Appendices (Optional)
  a. Supporting Information
Identify any supporting material, such as
  Details of prior versions
  Comments from prior reviews that were deferred for future implementation, e.g.,
         – Standards known to be in-work, or complete but not yet approved
         – New technologies that are currently not mature enough for use at this time
            (TRL 5 or below)1
         – Due to legal implications, product liability, political considerations (e.g.,
            inability to obtain export approval)
   Description of conflict resolution between technical factions to avoid reopening
      already-resolved issue(s), or discussion of conditions under which the issue(s)
      should be reexamined
   Names of Working Groups, Integrated Project Teams, external organizations, and
      individuals that worked jointly on this NCP (if applicable)
   New participants in the NCOIC are often unaware of prior discussions and often
      question consensus on issues— need to document the consensus process
      regarding NCP content.

See especially References 3, 4, & 5.


    b. Additional Implementation Guidance
    This section allows NCP authors to include additional guidance as part of this
    appendix to the NCP where that guidance is not addressed earlier in the document.
    Typical NCP implementation guidance includes:
     Architecture
     Design implementation
     Requirements definition and/or validation/verification
     Procedures


1
    Technical Readiness Levels as defined by the U.S. DoD Acquisition Guide Book, 2009


Clearance                             Version
Working Group Consensus                           Draft v1.1                               Page 25 / 29
                                                Services Working Group         Semantic Cloud Computing
                                                          or                     with Open Linked Data
                                               Cloud Computing Working            (RDF) Technical or
                                                         Group                     Capability Pattern


Another way to understand the three categories of NCPs is by using SCOPE2
dimensions as follows:
   Technical NCPs represent a binding decision between one or more Net Ready
     SCOPE dimensions & associated value ranges, and one or more Technical
     Feasibility dimensions & associated value ranges. They include/specify no
     SCOPE attributes in the Capability SCOPE Dimension set.
   Capability NCPs include one or more binding decisions between Capability
     SCOPE Dimension attribute value ranges and Net Ready SCOPE dimension
     attribute value ranges. They may also include binding decisions to Technical
     Feasibility dimension attributes and value ranges.
   Operational NCPs represent a binding decision among Capability SCOPE
     Dimension attributes only. No Net Ready SCOPE dimensions and associated
     value sets are specified, nor are any Technical Feasibility dimensions or values
     specified, with the possible exception of the inter-element time binding dimension
     pertaining to actors and actions in the operational NCP.
Ken Cureton, Practical Guidance for Net-Centric Pattern Developers, NCOIC Plenary Workshop,
September 21-25, 2009 Fairfax, VA, Approved for Public Release, Distribution Unlimited, NCOIC-Patt
Workshop-FebPlen-20090225, 48 slides.

Ken Cureton, Executive Overview of NCOIC Net-Centric Patterns, NCOIC Executive Council Session,
September 21-25, 2009 Fairfax, VA, Approved for Public Release
Distribution Unlimited, NCOIC-Patt Workshop-FebPlen-20090225. 19 slides

Ken Cureton, Network-Centric Operations Industry Consortium (NCOIC) Collaborations, I/U CRC
Industrial Advisory Board Meeting, October 8-9, 2009 Plano, TX, 25 slides.

Kevin Jackson, Cloud Computing Webex Media Briefing, October 27, 2009, 14 slides. Includes
Lockheed Martin Cloud Computing Research Investigation (slides 8-10).




2
    NCOIC Systems, Capabilities, Operations, Programs, and Enterprises model


Clearance                             Version
Working Group Consensus                           Draft v1.1                           Page 26 / 29
                                      Services Working Group       Semantic Cloud Computing
                                                or                   with Open Linked Data
                                     Cloud Computing Working          (RDF) Technical or
                                               Group                   Capability Pattern



 c. Adherence to Relevant NCOIC Documents
This section describes the pattern's mapping to the guidance in the NIF NSD-RM and
any applicable Specialized Frameworks documents. This section must include a
description of how the NCP supports each principle identified.
  NIF NSD-RM Adherence and Analysis - Examine the NIF overarching
      principles, determine their applicability to the NCP under development and if
      applicable, verify adherence to NIF Overarching Principles (NIF NSD-RM
      Section 2.3.1.2).
  Specialized Frameworks Adherence and Analysis - Verify adherence to principles
      and analysis contained in Specialized Frameworks as appropriate. ,


 d.   Validation Artifacts and/or Evidence
Provide evidence documenting what was done to validate the credibility and completeness of this NCP.
Evidence may include artifacts, test results, reports, briefings, analyses, or Subject Matter Expert
(SME) recommendations, from the review of this NCP.
     Operational NCPs: might include a description of how the NCP was derived from a validated
      Operational Requirements Document, a commonly accepted Concept of Operations,
      Operational Description (OD) or a commonly accepted Operational Scenario
     Capability NCPs: might include historical evidence of how this capability has been successfully
      used in operational missions
     Technical NCPs: might include description of, or test results from a prototype implementation
      of the technology in the NCP and field trials or experimentation

 e.   Vision for the future
     Recommended roadmap for follow-up activities
     Decision-points for revisiting the NCP
          – Update Standards and/or Guidance
          – Replace or Retire the NCP
This section allows NCP authors to include additional guidance as part of this appendix to the NCP
where that guidance is not addressed earlier in the document. Typical NCP implementation guidance
includes:
     Architecture
     Design implementation
     Requirements definition and/or validation/verification
     Procedures


Clearance                    Version
Working Group Consensus                Draft v1.1                            Page 27 / 29
                                                Services Working Group         Semantic Cloud Computing
                                                          or                     with Open Linked Data
                                               Cloud Computing Working            (RDF) Technical or
                                                         Group                     Capability Pattern


Another way to understand the three categories of NCPs is by using SCOPE3 dimensions as follows:
      Technical NCPs represent a binding decision between one or more Net Ready SCOPE
       dimensions & associated value ranges, and one or more Technical Feasibility dimensions &
       associated value ranges. They include/specify no SCOPE attributes in the Capability SCOPE
       Dimension set.
      Capability NCPs include one or more binding decisions between Capability SCOPE Dimension
       attribute value ranges and Net Ready SCOPE dimension attribute value ranges. They may also
       include binding decisions to Technical Feasibility dimension attributes and value ranges.
      Operational NCPs represent a binding decision among Capability SCOPE Dimension attributes
       only. No Net Ready SCOPE dimensions and associated value sets are specified, nor are any
       Technical Feasibility dimensions or values specified, with the possible exception of the inter-
       element time binding dimension pertaining to actors and actions in the operational NCP.
For actors recommend the following as appropriate.
      UML/SysML Use Case Diagram showing actors & use cases of the system, procedure, or
       operation
      U. S. Department of Defense Architecture Framework (DoDAF) / UK Ministry of Defense
       Architecture Framework (MoDAF) / NATO Architecture Framework (NAF) / AusDAF
       diagrams: Operational & Capability
For Structure recommend the following as appropriate.
      UML Class Diagram
      SysML Block Definition Diagram (& SysML Parametric Diagrams or Requirement Diagrams,
       if applicable)
      DoDAF / MoDAF / NAF / AusDAF diagrams: Systems & Services
      A simple Block Diagram of components
For Behavior recommend the following as appropriate.
      UML / SysML Activity Diagram, Sequence Diagram (or State Machine and Timing Diagram, if
       applicable)
      DoDAF / MoDAF / NAF / AusDAF diagrams: Services & Capabilities
      Flow diagram of procedural steps using BPMN and associated flow diagrams, IDEF-0 or
       similar modeling method for capability or operational pattern behaviors, especially those with
       close coupling to commercial enterprise processes
For a Requirements Verification table, the following format is recommended:
#   Title        Description         Type       Reference Verification Comments
                                                            Method
1
2
3
-

3
    NCOIC Systems, Capabilities, Operations, Programs, and Enterprises model


Clearance                             Version
Working Group Consensus                           Draft v1.1                           Page 28 / 29
                                    Services Working Group        Semantic Cloud Computing
                                              or                    with Open Linked Data
                                   Cloud Computing Working           (RDF) Technical or
                                             Group                    Capability Pattern


-
n

#               A numerical tracking number that can be used to trace requirements to
                implementation and testing for certification purposes
Title           A short title to identify the requirement
Description     A short description of the requirement being captured
Type            The type of requirement (“Mandatory,” “Recommended”, or “Allowed”)
Reference       A pointer to the applicable sections of the pattern that discuss the
                requirement AND any applicable sections of the underlying standards that
                apply. While this element must contain a linkage to the pattern guidance
                and applicable sections of the standards, it is by reference only and should
                NOT reiterate guidance verbatim from other sections of the pattern.
Verification    List the verification methods (Analysis, Test, Demonstration, or Inspection)
Method          that are allowable for this requirement).
Comments        List any additional information that would be useful for the Building
                Blocks supplier in implementing and verifying this requirement




Clearance                  Version
Working Group Consensus              Draft v1.1                             Page 29 / 29

								
To top