Schema Governance

NOT Currently Approved - This is a draft document only.  (10-8-2004) - Test page  (to be developed later)

  1. "Released Schemas" – All of the released schemas will be stored in a single folder called ReleasedSchemas (  This is to enable automated downloads to go to one folder and download all the schemas at one time. This folder will be ‘read only’ and available to the general public. You will also be able to view the folder contents and see the entire released schema list. The intent is to keep all supported versions of each released schema in this folder.   Security for this folder will be limited to the ‘Master’ site manager. New schemas and versions will only be posted by the ‘Master’ site manager and only after being notified by the proper FIDX official/s. The notification will preferably be by email for documentation. Having the proper FIDX individual give the approval is to insure that the schema to be moved has been properly voted on and approved by the FIDX committee.
  2. “Draft Schemas” – The draft schemas will be organized in separate folders by transaction.  Each folder will be for a specific XML transaction. Each folder will be assigned to an ‘author’.  That author will email the draft schema to the master site manager for posting to the website. Only the master site manager will be able to post or move a ‘draft’ schema to the released folder. The draft schemas will be available for review and testing.
  3. List Server -The purpose of the list is to communicate XML schema information to the developers and users of the schemas. The AHFA IT Council will have to decide if the list is to be an ‘open’ list or a ‘managed’ list.
  4. The schema library is currently managed by AHFA (David Purvis). Hosting the library of schemas on an AHFA server under AHFA management in no way implies that AHFA owns the schemas. The schemas are industry property available for use by anyone. I will state it again; this is an attempt to provide a service to the industry by an association that represents all segments of the industry.
  5. Disaster Recovery procedures will not be extensive. It will include reasonable hardware and site recovery but will not include redundancy and fail-over service. Some downtime is to be expected during the year. Offsite backup of the schemas will be performed periodically (timeframe to be determined). The transaction architecture has been set up so the industry can continue run with what they are hosting indefinitely (or until a new schema is deployed or someone new wants to get started).