Your SlideShare is downloading. ×
0
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
PLCS Reference Data Testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

PLCS Reference Data Testing

911

Published on

Describing experience gained using Semantic Web tools in PLCS Reference Data development.

Describing experience gained using Semantic Web tools in PLCS Reference Data development.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
911
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. On PLCS Reference Data Testing David Price Managing Director, TopQuadrant Limited [email_address] Analysis Validating Maintaining Deploying Evolving Acquiring Modeling Architecting Integrating
  • 2. Semantic Tool RD Testing Capabilities
    • SPARQL queries for quality assessment
    • SPARQL Rules/SPIN also available for persistent constraints
    • Reference Data development
      • Import/Transform to RD
      • RD spreadsheet or RD XML
      • XSD2OWL (generic)
      • UML or EXPRESS to OWL
    • Export as N3 so reviewers can read plain text as well as XML
    • ISO PLCS schema, OASIS RD subset schema, OASIS RD available as needed
  • 3. Constraint-like SPARQL Queries
    • Example - Find OWL Classes without a dc:source annotation
    NOTE – Available in TopBraid Composer Free edition
  • 4. General SPARQL Queries
    • Find all Assigned_property-related RD classes
  • 5. SPIN (aka SPARQL Rules)?
    • SPIN is the de-facto industry standard to represent SPARQL rules and constraints on Semantic Web models.
    • Open source implementation available and is included in TopBraid Composer Free Edition
  • 6. SPARQL Rules/SPIN QA
    • Use SPIN Constraints to check RD quality
    • Define constraints requiring Dublin Core on all OWL Classes
    • Turn on ‘Validation’ in TBC
    • Violations shown when editing RD classes
    NOTE – Available in TopBraid Composer Free edition
  • 7. Dublin Core Constraints
  • 8. Constraint Violation!
    • Missing dc:source annotation in DerivedDocument
    1 or more errors exist Each error flagged Apply SPIN constraints
  • 9. Constraint Violation! – Big Screen 2) Errors found in instance 3) Each error flagged 1) Apply SPIN constraints
  • 10. Reference Data Testing Approach
    • Create ‘PLCS proxy ontology’ from AP239 EXPRESS schema
    • Create OWL Individuals based on PLCS proxy ontology
      • Equivalent to Part 28 XML data file contents
      • Derive rdf:type from PLCS Classification Assignment in data so that reasoners can find errors such as using disjoint classes on same instance
    • Use Semantic Web tools where useful
      • SPARQL
  • 11. Domain/Proxy Ontologies Proxy Ontology Domain Ontology Mapping P28 XML Schema Message Mappings EXPRESS XML reeper
  • 12. AP239 Proxy Ontology Screenshot
  • 13. Exchange File Testing Approach?
    • Convert P28/P21 to OWL individuals
    • Converter or post-conversion SPARQL Construct can add rdf:type statements to RD
    • Open individuals file in Semantic Web tool
    • Run SPARQL queries
    • Run SPARQL Construct to generate data based on ‘valid’ PLCS dataset and compare with expected result data
    • Execute ‘domain’ constraints written using SPIN
    • Generate reports
    • TopBraid Composer can compare two ontologies
      • Result is RDF to be processed into a report
      • Could compare results of data exchange tests
  • 14. Namespaces on Following Diagram
    • AP239 = PLCS Proxy Ontology used to create instances, the full PLCS schema as OWL
    • data = data as in a Part 28 XML or Part 21 text file
    • ShipDesignRD = Ship Design Reference Data
    • schema = subset of PLCS schema classes used as top of RD hierarchy
    • Orange circle = Class
    • Purple diamond = instance
    NOTE – Diagramming not available in TopBraid Composer Free edition
  • 15. Part Manufacturer RD Example rdf:type (green box) is OWL equiv of PLCS Classification_assignment (red box) of PLCS External_class.id = URI of the OWL class. ShipDesignRD schema = RD PLCS schema AP239 = Proxy ontology
  • 16.  
  • 17. PLCS-Related Ontology Layers PLCS RD and Proxy Ontology SPARQL Rules for PLCS and/or DEX Business, domain, testing SPARQL Rules
  • 18. Additional thoughts
    • The proxy ontology testing approach clearly results in a ‘schema’ that can be used for data exchange
      • In addition to P21, P28 can use RDF encodings
      • Need to do more work on EXPRESS schema constraints as SPARQL/SPIN
    • Starting process of standardizing SPIN as ‘SPARQL Rules’
      • If interested in supporting that, please let me know
    • PLCS ontology is a step towards PLCS data sharing on the Web vision
  • 19. Feedback
    • DEXLib, like STEPmod is designed for spec writers,not implementors
      • Perhaps stop trying to do both and use something else for implementation?
    • Writing P28-based implementations is actually pretty easy
    • Big Question – Why DEXs given technology available today?
    • Or perhaps Why always a DEX for PLCS?
    • In cases where OASIS PLCS spec ‘gets something wrong’, just say NO!
      • For example, a simple script can add /IGNORE if ever required
  • 20. TopQuadrant Corporate Overview
    • Formed in 2001
      • Privately held
      • First Semantic Web Consulting Firm in U.S.
    • Products: TopBraid Suite
      • Semantic Web Application Platform
      • 600+ Customers
    • Solution Services
      • Workshops: Solution Envisioning, Ontology Modeling
      • Jumpstarts to Large Implementations
    • Semantic Web Training
      • 700+ People Trained
    • International Locations
      • Alexandria, VA
      • London, UK TopQuadrant Limited
      • Mountain View, CA
      • TopQuadrant Korea – Seoul, S. Korea
    • Strategic Partnerships
      • Oracle, Franz, CTG

×