SearchUser loginPopular contentAll time:
Valuation Firm GuideClient Guide
|
Extending the LIXI standardsOne problem we have encountered a number of times is the requirement to go beyond the LIXI valuation standards. This is because the LIXI standards really do represent the most common uses; but the ValEx platform and its partners are seeking to innovate - the two goals of innovation and standards often conflict. Consequently for the 1.4.1 version of the ValEx XSD, we are introducing a minimal change to allow much greater extensibility. We are introducing an <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="skip"/> node. What this allows is for lixi partners to define information in a non-lixi namespace; without breaking schema validation. For instance: <ValuationTransaction xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:foo="http://foo.com" ProductionData="No"> <-- Appearing after the RelatedPartySegment or AttachmentSegment --> <foo:Foo>Hello! I'm a custom string, but could be any valid custom XML structure</foo:Foo> </ValuationTransaction> We are strongly advocating this amongst the LIXI valuation and CAL standards group as a way to move forward with custom or proprietry requirements; whilst still remaining LIXI standard compatible. You can preview and update to the 1.4.1 schema; which is not yet in use by the ValEx application. By doconnor at 2011-01-25 15:48 | API | Client Guide | Valuation Firm Guide | login to post comments
|
Related LinksNavigationRecent comments
|
vx Namespace
We have recently introduced a vx namespace, which makes use of
xs:any
.