manufacturing systems integration division a development process for content standards kc morris,...

Manufacturing Systems Integration Division

A Development Process for Content Standards

KC Morris, Boonserm (Serm) Kulvatunyou, Josh Lubell, and Puja Goyal

US/DoC/NIST/MEL/MSID


Outline of the Talk

• Who we are

• Process for developing content standards: the Model Development Life Cycle (MDLC)

• Overview of our XML-related tools

• Examples of tools for XML Schema validation


Who We AreUS/DoC/NIST/MEL/MSID

• United States Government• Department of Commerce• National Institute of Standards and Technology• Manufacturing Engineering Laboratory• Manufacturing Systems Integration Division

(MSID)

= A government resource that provides technical solutions to advance system integration capabilities.


ManufacturingB2B

Integration

ManufacturingMetrology

Interoperability(Inspection)

ProcessPlant

ConstructionInformationIntegration

IntegratedCircuit

Manufacturing

ComponentValidation

Semantic Web R&D

“Generic” Testing Infrastructure and Tool Development(e.g., XML, ebXML, schema quality, test case generation)

Legacy MigrationThrough

Semantic Mapping

Automotive InventoryVisibility

CAD/CAMIntegration

SimulationSystem

Integration

NIST Interoperability Testbed


Background

• NIST B2B Interoperability Testbed– XML-based interoperability project with the automotive and

aerospace industries• NIST AEX Testbed

– XML-based interoperability project with the building construction industry

• Product Data Exchange and Validation Testing activities– Data exchange-based integration project, not XML-based

• Common characteristics– Specifications are segmented– Data exchange specifications evolve as integration projects

proceed• Also true for standards development efforts


Content Standards are Bridges


We Need a Process for Building Interoperability Bridges


Model Development Life Cycle

A guideline for building industrial strength data exchange bridges, that provides

• Detailed analysis of the development process for content standards

• Architecture for implementing that process

• Outline of requirements for tools

• Roadmap to the standards landscape


Some Specific Problems in Model Development

• Unbounded specification growth• Semantically duplicate terms, components, and

documents are created• Poor documentation reduces reuse• Classic interoperability problems are revisited• Large-scale harmonization (using a

common/canonical model) is hard to achieve

Model Development Life Cycle

Decomposition of the Model Development Life Cycle Existing Schemas & Classification Scheme

A2

Model Validation

A3

Model Piloting

A4

ModelRegistration

A1

Model Discovery

A5

Model Integration

Specification

Tools

RuleBased

Engines

Specification

Design Rules

Specification Reference

Data

Implementation Data

BusinessRules

ImplementationContext

Guidelines

SchematronXSLTEngine

AnnotationTools

Test Suites

ImplementationDocumentation

ExternalOntologiess

ClassificationAssistant

SemanticSimilarityMeasure

SemanticAlignmentAlgorithm

ExternalOntologies

Registry &Repository

QualifiedSchemas

DataExchange

Requirements

BusinessForms

ChangeRequests

Link Annotations

Change Requests

TableOf

Terms

Existing Schemas

Registry Entry

ClassificationScheme

NewSpecifications

Semantic AwareLookup Assistant

Requirement Gaps

Discovered Schema

Spreadsheet

AnnotationTools

Schema Semantics

ExistingData

Model Discovery

A1.1

Model SelectionData ExchangeRequirements

Semantic AwareLookup Assistant

A1.2

Model Extension

SchemaDocumentation

SelectedSchemas

forExtension

UncoveredRequirements

XML SchemaEditing Tool

New Schemas

A1.3

Model Creation

XML SchemaEditing Tool

New Schemas

Selected Schemas for Reuse

DesignRules

XML SchemaSpecification


DesignRules

SchemaDocumentation

ExternalOntologies

KnownSchemas


Model Validation

A2.1

SchemaQualification

A2.2

Data CoverageAnalysis

A2.3

SchemaCompatibility

Analysis

NamingGuidlines

DesignRules

RuleBasedEngine

NamingAssistant

Table of Terms

XML InstanceEditing Tool

XMLValidation

Tools

XML InstanceReference Data

XML Schema

ExistingData

BusinessForms

DataExchange

Requirements

Qualified Schemas


XMLValidation

Tools

Spreadsheet

Change Requests

Revised XML Instance Reference Data

Revised Qualified Schemas

Requirement Gaps

Qualified Schema

Model Piloting

A3.1

ModelComprehension

A3.2

ModelAugmentation

A3.3

ModelTransformation

XML Schemas

DocumentationEngine

DiagrammingTool

Model HTML

UML or other Diagrams

BusinessRules

TransactionRequirements

SchematronTools

Test SuiteDevelopment

Tools

Test Suites

XML Schemas

Implementation Data

ImplementationContext

Guidelines

XSLTEngine

ConversionRules

Tableof

Terms

Revised Implementation Data

Implementation Schema

Implementation Data

XML Schema

Model Registration

A4

ModelRegistration


Registry &Repository

ClassificationAssistant

XML InstanceReference

Data

New XML Components

QualifiedSchemas

LinkAnnotations

RegistryEntry

A2

A2

A2

A3

A5

A5

Test SuitesTable of Terms

Model Integration

A5.1

Identify OverlapsNew schema

SemanticSimilarityMeasure

A5.2

ResolveDuplicates

SchemaStatus

Duplicates

A5.3

Cross LinkOverlaps

Change Requests

AnnotationTools

ExternalOntologies

ExistingSchemas

Link Annotations

SchemaStatus

ExistingSchemas

Overlaps

AnnotationTools

SemanticAlignmentAlgorithm

New XML Components

Change Requests

Link Annotations


Overview of NIST Prototype Tools


XML Schema Validation Tool

• Objective: Ensure that schemas are compatible with a selected set of parsers

• Core Functionality: Validate one or more schemas or schema extensions with multiple selected parsers and schema files stored in a repository

• Status: Prototype


Quality of Design Tool

• Objective: Ensure that XML schemas conform to a selected set of design practices, e.g., use of common and valid terms, NDR conformance, use of the XML Schema structures that enhance reusability, maintainability, clarity, and interoperability

• Core Functionality: A flexible environment for specifying and executing best practice rules against the schemas

• Status: Beta – Available upon request. Contact Serm, [email protected]


XML Schema Naming Assister

• Objective: Ensure that type, element, and attribute names used in schemas are consistent within the schema and conform to ISO 11179 Naming Convention

• Core Functionality: Decompose names into Object Class, Property, and Representation Term tokens, validate them using a table of terms, and suggest alternate names

• Status: Prototype. Available at http://www.nist.gov/msid/Naming_Assister.html


XML Instance Validation Tool

• Objective: Ensure that schemas are compatible with a selected set of parsers, a set of sample data, a previous set of sample data (when the schemas have gone through changes)

• Core Functionality: Automatically validate one or more instance files against associated schemas with multiple selected parsers (in batch mode)

• Status: Prototype is available at http://www.nist.gov/msid/b2btestbed/semantic_checking.html


Schematron Editor Tool

• Objective: Assist a user in creating Schematron Rules

• Core Functionality: Create Schematron with little or no knowledge of XPATH/XSLT syntax through expression wizards that allow drag-n-drop elements from an imported XML schema business document

• Status: Prototype – available on Sourceforge site http://www.sf.net/projects/cs-wizard


Semantic Aware Lookup Assistant

• Objective: Assist the user when searching for a reusable business document or components that support data exchange requirements

• Core Functionality: Match data exchange requirements from the user with existing schemas and provide quantitatively measured results

• Status: Research has started


Classification Assistant

• Objective: Provide a quantitative measure suggesting a suitable classification to register a component within a classification scheme

• Core Functionality: Given a data exchange specification (and documentation), proposed a ranked set of appropriate classification nodes

• Status: Research has not started


Semantic Alignment Tool

• Objective: Provide quantitative analysis and suggestions for model harmonization

• Core Functionality: Analyze a newly registered data exchange specification against existing ones for semantically duplicative and overlapping structures and suggest alternatives

• Status: Research has not started


Examples

• Support model validation

• XML Schema Validation tool

• Schema Quality of Design tool

A2.1

SchemaQualification

A2.2

Data CoverageAnalysis

A2.3

SchemaCompatibility

Analysis

NamingGuidlines

DesignRules

RuleBasedEngine

NamingAssistant

Table of Terms

XML InstanceEditing Tool

XMLValidation

Tools

XML InstanceReference Data

XML Schema

ExistingData

BusinessForms

DataExchange

Requirements

Qualified Schemas


XMLValidation

Tools

Spreadsheet

Change Requests

Revised XML Instance Reference Data

Revised Qualified Schemas

Requirement Gaps

Qualified Schema

Model Validation


What is Schema Qualification?

Tests that a schema• Works with relevant tools• Consistently represents similar concepts• Uses constructs that enhance reusability,

maintainability, clarity, and interoperability• Uses preexisting schemas correctly• Use terms/names correctly and consistently


Prototype Validation Service

• Uploads an XML schema to test against the W3C standard for XML Schemas

• Validates using multiple XML tools• Provides access to a repository of schemas

which may be extended (e.g., Universal Business Language schemas)

Example 1

DEMO


Schema Quality of Design Testing Tool

Example 2

• Contains computer interpretable rules based on naming and design guidelines from a number of sources

• Upload rules written in Schematron and JESS into rule-base

• Execute rules against schema and report results


Application to Developing XML Schemas

QOD applied to grants.gov schemas resulted in several warnings including

• Gobal elements declared in non-desirable places• Anonymous/local types defined in non-desirable places• The “Global” schema doesn’t declare a default namespace• Document/Transaction level schemas define multiple

global elements• Non-determinism found• Redeclaration of elements and types (e.g. programType) in

different namespaces


Summary

• MDLC is a recipe for building robust data exchange specifications

• It drives development of tools and capabilities– Examples include Validation Service and

Quality of Design tools

• Maximizes reuse of tools to serve a diverse collection of customers


Contacts

• KC Morris – [email protected] • Serm Kulvatunyou – [email protected]• Josh Lubell – [email protected]• Puja Goyal – [email protected]

References

• Morris, KC , Kulvatunyou, Boonserm, Frechette, Simon , Lubell, Joshua , Goyal, P. , XML Schema Validation Process for CORE.GOV, NISTIR 7187, (2004)

Summary of NIST ToolsetTask Addressed Tool Status & Origin

Diagnose XML Schema design quality by applying best practice rules as well as design guidelines published by an authoritative source.

XML Schema Quality Assessment Tool and Rules Repository (QOD)

Prototype, NIST

Verify XML instance data with respect to the AEX XML schemas. XML Validation Page with WWW interface

Prototype, NIST

Verify the names in an XML Schema using a table of allowable terms and ISO11179 standard conventions.

XML Schema Naming Assister Prototype, NIST

Define XML instance validation rules in Schematron language. Schematron Editor and Constraint Specification Wizard (CSW)

Beta, NIST

Transform an XML Schema and/or XML instance data according to a prescribed design pattern.

XML Simplifier Tool Prototype, NIST

Capture, codify, and execute business rules that are not captured in the XML Schema.

Content Checking Tool (CVTS)http://syseng.nist.gov/b2bTestbed/projects/semanticChecking

Prototype, NIST

Verify an XML Schema interface implementation with respect to the input and output mapping of the content data onto the implementation data store.

Content Mapping Conformance Testing Tool (MapTest)

Prototype, NIST

Monitor and verify choreography of business transactions encoded using the Business Process Specification Schema (BPSS).

BPSS Process Monitor and Checking Tool (BPSS Monitor)

Prototype, NIST

Translate an XML Schema into the Web Ontology Language (OWL) and XML instances into OWL instances.

XML Schema-to-OWL Converter(Xml2Owl)

Prototype, NIST

Determine model-based compatibility among OWL ontologies and consistency of an OWL instance with respect to an OWL ontology.

OWL-based Integrator (OwlInt) Prototype, NIST

Estimate semantically close concepts across two independently developed taxonomies.

Semantic Proximity Estimator (Proxim)

Research, NIST-Academia


Schema Quality of Design Testing Tool

manufacturing systems integration division a development process for content standards kc morris,...

Documents

development process

xml schemas

xml schema validationwho

xml schema structures

commoncanonical model

schema files

schema extensions

schemas status