Cart
[Home] [By Thread] [By Date] [Recent Entries]
XML Schema has left you two ways to do this. I detail them in an upcoming article for XML Journal that is available on the web at: Article: http://www.sys-con.com/xml/archives/0205/cleary/index.html Listings: http://www.sys-con.com/xml/source/2-5/code.cfm?Page=25 Another alternative is the Schema Adjunct Framework, which defines rules for creating a separate adjunct (file) that contain these application specific validations. You can find more info on SAF at http://www.extensibility.com/saf. David Cleary Progress Software -----Original Message----- From: sabba [mailto:sabbadin@i...] Sent: Thursday, May 03, 2001 5:42 AM To: XML-DEV Subject: intersecting schema with application-specific validation hi, i'm developing an xml based application where i need to validate a "rather" complicated structure. I'm happy that w3c schema have right yesterday (2nd may '01) become a reccomendation, still i think i won't be able to express all validations i need to express using just an xml schema, moreover i need to generate a "new instance" based on this "schema" , and so i'll need to put more info "somewhere" since an xmlschema leaves you, evidently, too much freedom in this "new instance" process. The point where my doubts are is that , since schema won't be enough , where should i put extra "application specific" validation info (a custom xml syntax ?) . how can i apply both validations in a consistent manner that won't lead to spaghetti code. if there is any standard, approach , best practice you are aware ? i'd like to know. thank in advance.
|
