1 / 40

XFDL Overview

Developed by PureEdge and Tim Bray (co-author of XML)Submitted to W3C (1998) as an application of XMLAllows organizations to remove paper from their business processesDesigned for high-value business-to-business e-commerce transactions where legal validity of transaction records is a priorityDynamic interface, Security and Transport layer for data conforming to any XML Schema.

zinnia
Download Presentation

XFDL Overview

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. XFDL Overview Presentation to XML.GOV July 23, 2003 Keith MacKenzie – Director of Development

    8. Valid Transaction Records Legal requirements for paper records have been established over many years XFDL replicates these requirements These requirements are based on three key concepts: Security Non-repudiation Auditability

    9. Valid Transaction Records These concepts are based upon a foundation of: signer authorization signer authentication document authentication context preservation

    10. Valid Transaction Records Content, context, and structure need to be preserved Paper forms accomplish this transparently, but it is difficult to achieve this in the digital world

    11. Valid Transaction Records Most e-forms technologies do not naturally provide a strong transaction record. Why? Data is moved into and out of a presentation template, and these two components are independently stored Separation of data content and presentation context results in risk of transaction meaning being lost

    12. Valid Transaction Records Example: applying for a $250K insurance policy online using an HTML form Claim repudiated -- how is it resolved Insurance company only has digitally signed tag=value pairs, not a complete transaction record Since the signature doesn’t cover the HTML form template, it can be changed independently Proper formulation includes the questions, the user’s answers, and a representation of how the document was presented to the user at the time it was all ‘locked down’ with a digital signature WHAT YOU SEE IS WHAT YOU SIGN!

    13. Valid Transaction Records

    15. Rich Presentation

    17. Simplifying Transaction Process To go beyond paper, E-forms should: Simplify form filling of complex traditional forms by instead guiding a end-user: Wizard approach Exactly replicate traditional forms to ensure compliance with regulations Prompt the user for selection of valid values only Enforce data formats (date, zip code, phone number) Apply business rules at time of data entry Be state aware, to allow multiple users to focus on and update only their section Interoperate with workflow and process management engines

    18. Simplifying Transaction Process

    19. Simplifying Transaction Process

    26. XForms Components Source: W3C

More Related