Global Justice XML Data Model Naming and Design Rules 17 August 2005.

Slides:



Advertisements
Similar presentations
Database Systems: Design, Implementation, and Management Tenth Edition
Advertisements

1. Introduction OASIS Reference Model for Service Oriented Architecture 2. ECF 4.0 Architecture 2.1 Core vs. Profiles 2.2 Major Design Elements 2.3.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
1 Overview of Other Global Networks Exchange Network User Group Meeting April 2006.
IRS XML Standards & Tax Return Data Strategy For External Discussion June 30, 2010.
Technical Writing Function. The purpose of having guidelines is to make the document more readable. Standard guidelines govern – Format – page layout,
1 1 Roadmap to an IEPD What do developers need to do?
NIEM-UML Profile Justin Stekervetz, NIEM PMO
ISO Standards: Status, Tools, Implementations, and Training Standards/David Danko.
GJXDM Information Exchange Package Methodology Naming & Design Rules (MNDR) John Ruegg County of Los Angeles Information Systems Advisory Body GJXDM User.
1/31/2006OLSI Standards Interoperability Meeting 1 OLSI Standards Interoperability Meeting LegalXML Member Section Briefing Donald L. Bergeron – LexisNexis.
Lecture Seven Chapter Six
GJXDM User’s Conference September 7, 2006 Component Reuse: Identifying and Building Components for Use in Exchange Analysis.
A Tool Kit for Implementing XML Schema Naming and Design Rules OASIS Symposium: The Meaning of Interoperability May 9, 2006 Josh Lubell,
U.S. Department of the Interior U.S. Geological Survey NWIS, STORET, and XML National Water Quality Monitoring Council August 20, 2003.
National Information Exchange Model Briefing for FGDC HSWG David Li, Ph.D. Geospatial Management Office, DHS Feb 16, 2006.
1 GJXDM/NIEM Presentation. Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 2 Background:
PLANNING RSTWG Review of Planning Concept of Operations & Requirements Tasks.
An Experiment on Spatial Data Exchange May 22, 2002 SAIJO, Yuuki (Geographical Survey Institute Japan) ISO/TC211 Workshop on Standards.
Federal XML Naming and Design Rules and Guidelines Paul Macias.
Federal XML Naming and Design Rules and Guidelines Paul Macias.
3 rd Annual European DDI Users Group Meeting, 5-6 December 2011 The Ongoing Work for a Technical Vocabulary of DDI and SDMX Terms Marco Pellegrino Eurostat.
Federal XML Naming and Design Rules and Guidance: Potential Next Steps Ken SallKen Sall, SAIC XML Community of Practice Presented at NIST March 15, 2006.
Developing a common set of federal NDR’s Mark Crawford Draft April 28, 2005.
U.S. Department of the Interior U.S. Geological Survey NWIS, STORET, and XML Advisory Committee on Water Information September 10, 2003 Kenneth J. Lanfear,
Federal XML Naming and Design Rules and Guidelines (NDRG) / XML Schema Guidelines (XSG) – An Overview Ken SallKen Sall, SAIC / KC Morris, NISTKC Morris.
SEARCH Membership Group Systems & Technology PAC Global Justice XML Data Model (GJXDM) Update January 29, 2005.
Who is TIJIS? What is NIEM? What is the Texas Path to NIEM? What does it mean to me?
Federal XML Naming and Design Rules and Guidelines Mark Crawford.
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 13 June 2013 Meeting #3 hData Record Format Taskforce 1 © 2012 The MITRE Corporation.
NIEM-UML PROFILE Justin Stekervetz, NIEM PMO Cory Casanave, Model Driven Solutions Mark Kindl, Georgia Tech Research Institute March 2012 OMG Meeting.
IRS XML Messaging Schemas 22-September Why are we talking about “Messaging Schemas”? IRS has a need to exchange data –Batch processing –Transaction.
National Information Exchange Model Update for the Global Advisory Committee Spring 2008 Meeting April 10, 2008 NIEM Technical Architecture Committee (NTAC)
JIEM and Business Process Change. Exchange Analysis  Work with stakeholder Subject Matter Experts (SMEs) to identify information sharing requirements.
United States Department of Justice Implementing Privacy Policy in Justice Information Sharing: A Technical Framework John Ruegg,
1 Presentation to Legislative Council Panel on Financial Affairs Progress of Implementation of Basel II in Hong Kong Hong Kong Monetary Authority 4 May.
P1516.4: VV&A Overlay to the FEDEP 20 September 2007 Briefing for the VV&A Summit Simone Youngblood Simone Youngblood M&S CO VV&A Proponency Leader
Strategy Markup Language (StratML) XML CoP
NIEM Information Exchange Package Documentation (IEPD) Mini Kanwal NIEM Technical Advisor Department of Homeland Security September, 7 th 2006.
SAML in Authorization Policies draft-guenther-geopriv-saml-policy-00.
Message Development Framework (MDF) Is a Methodology for building HL7 models Is a description for defining HL7 standard messages Full instruction.
11/7/ :20 PM National Information Exchange Model Global Justice XML Data Model Users Conference June 10, 2005 James Feagans, DOJ and Michael Daconta,
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
11/10/ :04 AM National Information Exchange Model James Feagans & Michael Daconta NIEM Project Manager GLOBAL ADVISORY COMMITTEE BRIEFING October.
Sheet 1XML Technology in E-Commerce 2001Lecture 2 XML Technology in E-Commerce Lecture 2 Logical and Physical Structure, Validity, DTD, XML Schema.
1 1 Coordinating the Development and Adoption of Emergency Data Standards With The Ongoing Development of NIEM Status and Questions.
Partnerships in Information Sharing California Department of Justice Bureau of Criminal Identification and Information.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
Information Exchange Package Documentation (IEPD) Clearinghouse Christopher Traver, Technical Advisor BJA/OJP/USDOJ May 17 th, 2006
Internet & World Wide Web How to Program, 5/e. © by Pearson Education, Inc. All Rights Reserved.2.
JIEM and Business Process Change. 2 Objectives Need for Exchange Analysis – Available Tools What is JIEM? Business Process Modeling Using JIEM Where JIEM.
Leveraging UBL for Developing Justice XML (GJXDM) Reference Documents John Ruegg County of Los Angeles Information Systems Advisory Body GJXDM User Conference.
CEN/ISSS eBIF GTIB Project Meeting, Brussels Mar , 2009 CEN/ISSS eBIF GTIB Project Meeting, Brussels 1 CEN/ISSS eBIF Global eBusiness Interoperability.
DOT Implementing the Surface Transportation Domain Daniel Morgan 26 October 2015.
ISO 191** Overview A “Family” of Standards. Resources ISO Standards Web Page – Technical.
Technical Steering Committee La Jolla, January 2003 Paul Kiel, HR-XML.
GJXDM Technical Specification GTRI Team June 2005.
Lecture 23 XQuery 1.0 and XPath 2.0 Data Model. 2 Example 31.7 – User-Defined Function Function to return staff at a given branch. DEFINE FUNCTION staffAtBranch($bNo)
July 11, 2008OASIS SET TC OASIS Semantic Support for Electronic Business Document Interoperability (SET) TC Overview.
June, 2005 NCSC Component Library National Center for State Courts & URL Integration June, 2005
GJXDM Tool Overview Schema Subset Generation Tool Demo.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Colorado Springs Producer-Archive Interface Specification Status of standardisation project Main characteristics, major changes, items pending.
Document Development Cycle
Implementing the Surface Transportation Domain
Data Modeling II XML Schema & JAXB Marc Dumontier May 4, 2004
GJXDM Tools Team Georgia Tech Research Institute
Information Systems Advisory Body GJXDM User Conference - June, 2005
Proposal of a Geographic Metadata Profile for WISE
Presentation transcript:

Global Justice XML Data Model Naming and Design Rules 17 August 2005

Outline Current status Inputs / influences What this spec is / is not Schedule Table of contents Introduction and scope Principles Rules Comparison to other NDRs

Current Status Still being vetted by Global XSTF, not yet undergone the debate process Primary focus is currently on rule accuracy against 3.1 Final draft will specify release version 3.1 (31 Oct 2005) Anticipate NDR rule modifications/refinements and new rules Anticipate changes to GJXDM Work remaining: new content (definitions and rules) explanations examples revision of relationships other conformance profiles

Inputs and Influences Inputs: GJXDM OASIS LegalXML IJ TC GJXDM draft MNDR Fed-XML-NDR Working Group draft NDRG OASIS UBL NDR Influences: NIEM Steering Committee Federal Enterprise Architecture IJIS Institute OASIS LegalXML Integrated Justice TC National Center for State Courts Federal XML NDR Working Group

What Spec Will Do or Be Product of the Global XSTF Technical specification for GJXDM 3.1 Specify how GJXDM *IS* actually defined Format as close as possible to the UBL NDR document (as appropriate) Use/copy appropriate wording from other NDR documents (inputs) Will include: definitions principles rules, rationales, and explanations examples for rules

What Spec Will NOT Do or Be NOT a projection of UBL on GJXDM NOT a comparison of UBL and GJXDM NOT a methodology for building Information Exchange Package Documentation (IEPDs) (i.e., NOT an “MNDR” – Methodology, Naming, and Design Rules)

Schedule (tentative) 15 JulInternal Draft 1 XSTF review/comment 8 AugInternal Draft 2 XSTF review/comment 23 AugExternal Draft 1 review … expect about 3 more drafts leading to … 31 OctTarget GJXDM release v3.1

Table of Contents Introduction Scope Principles Relation to standards Normalized structure Schema rules Annotation rules Subset rules Instance rules Supporting Schemas References

Introduction Background (very concise) Audience Brief description of reference architecture Scope Document conventions

Scope addressed Specification for GJXDM 3.1 Focused on definition of GJXDM-conformant schemas GJXDM-conformant reference schemas Subsets Documentation GJXDM-conformant instances

Principles Principles guide creation of rules Some principles are design criteria Only rules are binding (enforceable) Format: [Principle ] Currently 22 principles

General Rule Format (example) Explanation … Example … RationaleUsing the representation term “Type” immediately identifies XML types in a GJXDM-conformant schema and prevents naming collisions with corresponding elements and attributes. [Rule GNR2]GJXDM-conformant schemas SHALL use the representation term “Type” in the name of each non-enumerated XML type.

Rule Categories ATD: Attribute Definition ATN: Attribute Naming CSR: Constraint Schema CTD: Complex Type Definition DOC: Documentation GNR: General Naming GXS: General XML Schema IND: Instance Document SSR: Subset Schema STA: Standards STD: Simple Type Definition STR: Structures

References Citations and URIs for source specs XML specifications RFCs Schema for XML Schema EBNF notation

Survey of NDRs OASIS IJTC GJXDM draft MNDR: 100 Rules 37 Definition Federal XML draft NDRG (to date): 10 Principles 159 Rules GJXDM draft NDR (to date): 22 Principles 110 Rules 5 Definitions

Summary Content development continues anticipated content (explanations, examples) new content (omissions, changes) XSTF vetting continues 170 comments databased for 1 st draft debate, refine, reach consensus relationships non-conforming schemas External vetting as soon as possible Changes moving to GJXDM 3.1 Impact of NIEM Change is the only certainty [Marcus Aurelius]