HSXML Requirements
A listing of general functional requirements for the Human Service XML specification
(Very) Draft HSXML Requirements
- HSXML should constrain compliant documents into grouping client identifiers, service events (using agency site service model of AIRS), provider data, etc.
- Over time, HSXML should seek to constrain compliant documents from duplicitous data fields in different sections. i.e. standardize on AIRS XML format to describe a service provider.
- HSXML hould be cognizant of and somehow dictate the structure of the schemas it encapsulates (HUD HMIS AIRS XSD, AIRS, HUD CARS, Disaster XML, etc.) So that multiple Schemas' documents can be a part of a valid HSXML document.
- HSXML Should prescribe a SOAP messaging standard so deletions/updates and error handling can be standardized nationwide.
- HSXML should be extensible/importable into a custom Schema (i.e. all elements are top-level types)
- HSXML should be based on the structure of the data and not the content within that structure. Once determined, the structure of the HSXML will be stable and not subject to incremental adjustments.
- Add more here, please.
