1 / 11

Extending MISMO 3.2: Custom Attributes and Use Cases for Enhanced Interoperability

This document outlines the extension capabilities of the MISMO 3.2 schema to accommodate custom requirements from trading partners. It highlights key use cases, such as adding attributes from other namespaces to existing containers and redefining containers for additional data needs. The analysis compares MISMO's standard file set with extended file sets, providing guidance on schema creation, file importation, and definitions necessary for custom applications. Essential steps include using *_EXTENSION containers to implement unique XML constraints tailored for specific partner requirements.

dean
Download Presentation

Extending MISMO 3.2: Custom Attributes and Use Cases for Enhanced Interoperability

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. Extensions in 3.2 Greg Alvord RealEC June 4, 2012

  2. New Extensions in 3.2 • Any Element can have attributes from other namespaces • Any CONTAINER • Any Data Point

  3. Use case 1 • Two Trading partners want to use MISMO • Both Partner have needs beyond MISMO scope.

  4. Two Partners • Options • Edit the MISMO schema • Places things in MISMO namespace that does not belong • Use extensions • Adds three new files • Never touches MISMO files.

  5. Compare and Contrast MISMO Schema File Set Extended File Set Root File MISMO_3.2.0_B291AcmeAjax.xsd Use MISMO data types? MISMODataTypesB291.xsd Use MISMO enumerations? MISMOEnumeratedTypesB291.xsd Use MISMO data points / containers MISMOComplexTypesB291.xsd Acme Extension Acme.xsd Ajax Extension Ajax.xsd • Root File • MISMO_3.2.0_B291.xsd • Support Files • MISMODataTypesB291.xsd • MISMOEnumeratedTypesB291.xsd • MISMOComplexTypesB291.xsd • MISMOComplexTypeExtensionsB291.xsd • External File • xlink.xsd

  6. The Steps • Create a file in the MISMO namespace • MISMO_3.1.0_B288AcmeAjax.xsd • Import all the required pieces • Redefine the MISMO definitions • For each container that needs more data redefine the *_EXTENSION container • *_EXTENSION allows any valid XML • Redefinition will Restrict down to the desired design.

  7. The content of *_EXTENSION • Before redefinition • MISMO element ( Allows anything from MISMO name space) • OTHER element (Allows anything from anything except MISMO namespace) • After redefinition • MISMO element ( Allows anything) • OTHER element defined in the Acme name space

  8. Use case 2 • Two Trading partners want to use MISMO • Both Partner have needs beyond MISMO scope. • They both want to extend Borrower Detail

  9. Use case 3 • Acme wants to require some data and limit size of things that Ajax sends

  10. How to use for other restrictions • Use Redefine to • Restrict the length of fields • Add required fields

  11. Questions? Greg Alvord 713-829-5197 Gregory.Alvord@RealEC.com Greg.Alvord@gmail.com

More Related