1 / 29

Driver History JXDD Model Validation

Driver History JXDD Model Validation. September 4, 2003. The Pennsylvania JNET XML Vision. The original JNET Blueprint, published during late 1997, defined an XML based “electronic interchange of data” concept.

aurek
Download Presentation

Driver History JXDD Model Validation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Driver History JXDD Model Validation September 4, 2003

  2. The Pennsylvania JNET XML Vision • The original JNET Blueprint, published during late 1997, defined an XML based “electronic interchange of data” concept. • This JNET Blueprint established a requirement for the usage of “a standard criminal justice file format to support the electronic interchange of data”. • It further stated “XML provides information about the data itself and how it relates to other data. In essence, XML is emerging as a standard for web-based delivery of data in agreed-upon name-value pairs.”

  3. The Pennsylvania JNET XML Vision • The JNET blueprint established a strategic direction for sharing information among JNET participating organizations. • A globally accepted, criminal justice focused, XML data standard is essential to accomplishing the strategy. • JNET is, and has always been, in 100% support of “Facilitating information sharing and integrated justice by reducing impediments, such as standards, cost, and time.” • JNET is committed to being part of the enablement process to more effectively provide information sharing and communications among the many justice/public-safety agencies at the local, state, and federal levels.

  4. XML Technical Strategy Semantic Web Justice RDF/OWL Service/Process Definition - ebXML Justice XML Data Model and Schema We are here XML Syntax, DTD, JNET Messages Reliable Messaging Infrastructure

  5. XML Design Approach End Start Understand Justice Data Model • Fill the gap: • Add extensions and restrictions • Add local elements Identify, Analyze Data Source and object modeling Define data mapping between data source and XML Map data source object model to Justice data model Define transformation rules between XML and web presentations

  6. Data Source Structure

  7. Object Model Driver 1 Address 1,* Driver Authorization (DL) Driver Authorization (CDL) Driver Authorization (PL) Driver History 1,* Driver Authorization (OLL) 0,1,* Driver Incident (Violation) 0,1,* Driver Incident (Violation) Driver Accident Driver Accident 0,1,* Driver Accident Driver Accident Driver Incident (Medical) Driver Incident (Medical) 0,1,*

  8. Object Mapping

  9. Schema Diagram

  10. Message Structure jxdd3:PersonGivenName jxdd3:PersonMiddleName jxdd3:PersonSurName jxdd3:PersonSuffixName jxdd3:PersonName jxdd3:PersonBirthDate jxdd3:PersonAssignedIDDetails jxdd3:PersonDriverLicenseID Driver jxdd3:PersonPhysicalDetails jxdd3:PersonSexText jxdd3:PersonSexCode DriverRecordTypeElement DriverRecordTypeCode DriverRecordTypeDescriptionText jxdd3:AddressStreet jxdd3:Address jxdd3:StreetFullText jxdd3:AddressCityName usps:USStateCodeTypeElement jxdd3:AddressStateCode jxdd3:AddressPostalCodeID jxdd3:DriverAuthorizationIssueDate jxdd3: DriverAuthorizationExpirationDate jxdd3: DriverAuthorizationEndorsementCode jxdd3:DriverAuthorizationRestriction DriverHistory DLAuthorization CDLAuthorization OLLAuthorization PLAuthorization DriverLicenseClassCode jxdd3: DrivingRestrictionDescriptionText DriverOriginalAuthorizationIssueDate DriverLicenseStatusCode DriverLicenseStatusDescriptionText DriverLicenseLearnerPermitClassCode DriverLicenseStatusElement DriverLicenseSchoolBusEndorsementDescdriptionText jxdd3: ActivityTypeText jxdd3: ActivityDescriptionText jxdd3: ActivityDate Act143Disclaimer jxdd3:Incident ViolationIncident MedicalIncident jxdd3: ActivityDate jxdd3: Conviction Action PLAction OLLAction ResponseAction Consequence jxdd3: ActivityResultText ProcessDate jxdd3: ActivityCommentText jxdd3: CourtActivity jxdd3: ActivityDate DriverAccident jxdd3: IncidentLocation VehicleType jxdd3: LocationDescriptionText

  11. Data Element Mapping

  12. Code Tables

  13. Technology, Platforms, and Tools

  14. Infrastructure for Driver Info JNET PennDOT Photo DB SSL Web App JNET User Desktop SSL/VPN Wireless Middleware SSL PennDOT IMS Messaging Hub Carrier Network(s) SSL SSL JNET User PDA PSP IIMS AOPC Police Troopers

  15. Scale – Volume, Size, Speed, …

  16. Cost Estimation * Hardware and software costs are not covered.

  17. Benefits, Barriers, Options

  18. Demo JNET Driver Information Query Demo • Driver Photo Lookup • Driver History Report

  19. Driver Photo Lookup

  20. Driver Photo Lookup (continue)

  21. Driver Photo Lookup (continue)

  22. Driver Photo Lookup (continue)

  23. Driver Photo Lookup (continue)

  24. Driver History

  25. Driver History (continue)

  26. Driver History (continue)

  27. Driver History (continue)

  28. Driver History (continue)

  29. Q & A

More Related