What does this all mean?

Transcription

1 Schemas, XML and Validation What does this all mean?

2 In the beginning. Minnesota Uniform Conveyancing Blank Forms were used as templates by the creators of the documents

3 The ERERTF started with these and identified the data that t went in the underlines

4 Let s do a little example to show you what was done There are many variations of mortgagor g names so let s design a format that would work for the majority of the cases We start t with a BUSINESS RULE stating: ti Individual Mortgagor s last name is required (we have to since Prince lives in Hennepin county)!

5 We create an entity called an element that would identify the data that is being represented <Name> We then populate this element with data <Name>John Brown</Name> Where Name is the element and John Brown is the data Our business rule (last name is required) cannot be enforced easily as we would have to parse through the name to find the 2 names and then assume there was a first and last name

6 Most county systems separate the first and last name into different data fields, so let s do that We can create new elements called: <First Name> <Last Name> And populate the data in these: <First Name>John</First Name> <Last Name>Brown</Last Name>

7 This works nicely to validate our business rule as we can easily determine if there is or is not data entered for the last name because it has its own element This also allows for the county systems to use this data against their own backend systems since it is separated out This exercise was repeated for each variation of data that could be populated on the Minnesota Uniform Conveyancing Blank forms

8 After all the elements were identified, we then needed to group the data that would be representative of each underline on the document We did this by creating new elements <Mortgagor> <First Name>John</First Name> <Last Name>Brown</Last Name> </Mortgagor> As we grouped elements together with their data the resulting file is called XML This is what is sent to the county

9 If we: remove the data values (ie. John) keep the element names (<First Name>) add rules (what is required, data types, enumerated lists) the resulting file is the Schema. <element ref= Mortgagor minoccurs= 1 > <element ref= First Name minoccurs= 0 /> <element ref= Last Name minoccurs= 1 /> </element> The county uses the Schema (as the business rules) to The county uses the Schema (as the business rules) to test the XML that is submitted to them to ensure that the elements and rules are correct

10 Here are a few examples to validate against: Example 1: <Mortgagor> <First Name>Jimmy</First Name> <Last Name>Jones</Last Name> </Mortgagor> Is this valid for the following Schema? <element ref= Mortgagor minoccurs= 1 > <element ref= First Name minoccurs= 0 /> <element ref= Last Name minoccurs= 1 /> </element>

11 Example 2: <Mortgagor> <Last Name>Prince</Last Name> </Mortgagor> Is this valid for the following Schema? <element ref= Mortgagor minoccurs= 1 > <element ref= First Name minoccurs= 0 /> <element ref= Last Name minoccurs= 1 /> </element>

12 Example 3: <Mortgagor> <First Name>Prince</First Name> </Mortgagor> Is this valid for the following Schema? <element ref= Mortgagor minoccurs= 1 > <element ref= First Name minoccurs= 0 /> <element ref= Last Name minoccurs= 1 /> </element>

13 Example 4: <Mortgagor Name> <First>Jimmy</First > <Last>Jones</Last > </Mortgagor Name> Is this valid for the following Schema? <element ref= Mortgagor minoccurs= 1 > <element ref= First Name minoccurs= 0 /> <element ref= Last Name minoccurs= 1 /> </element>

14 We have just done an exercise in Schema Validation!!!

15 In the real world: Performing this task manually is not a good use of a person s time! Each vendor uses a validation engine (application) that references the Schema to validate the XML sent to the county Schema Validation tests the validation engine to ensure all rules identified d in the Schema have been coded appropriately If Schema Validation is passed, then submitters s can only submit the XML in accordance with the Schema that has been validated

16 That was then: Test XML files were created and ed to the vendors to validate The vendors validated the XML using their validation engine and returned the errors (if found) The vendor was then informed on whether they passed validation or not If the vendor passed the validation, the vendor then signed a form stating that the version of the validation engine used to validate the XML files was the same version used in the county production system. The vendor was now certified to accept Level 3 electronic documents in Minnesota If the vendor failed validation, they were asked to repeat the tests

17 This is now: 1. Document and create test cases per document type Identify the scenario Provide the XML Provide the expected results 2. Create a form for the vendor to fill out identifying: Validation engine used Changes to the schema (if necessary to work with their validation engine) Types of Signatures they are using (digitized, digital, text) what they accept what they return 3. Require a documented walkthrough of how the vendor is executing ecut the validation tests

18 4. Require that an initial test go through real time with appropriate results 5. Indicate what is expected back from the vendor XML that would be returned Recorded Rejected by validation engine Rejected by county Image of the document that was generated by their system using stylesheet provided in the XML The error that was generated if not part of the reject message in the XML (usually applies when rejected by validation engine)

19 Deliverables to ERER Commission: 1. What was tested for each vendor 2. Testing deliverables with each vendor (including XML and images) 3. Documented schema changes vendor had to make 4. Documented software specifics gathered for testing purposes only (ie. what validation engine they are using) 5. Pass/Fail of Certification

20 Need to determine: 1. Only testing for Level 3 documents using the MN Level 3 Schema Standard Version What document types are being tested (Satisfactions, Certificates of Release and Assignments?) 3. What elements are to be tested within the schema and to what extent: Property? Digitized Signatures, Text Signatures, etc.???

21 What will not be tested: 1. Business rules that are not built into the schema (for instance, verifying that the notary commission date has expired as that rule isn t built into the schema) 2. County specific requirements (for instance, only allowing a certain range of document numbers in the recorded document number field)

22 Questions?