Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Keyref from an NMTOKENS list [Thread Next] Re: FacetsTo: "Bryce K. Nielsen" <bryce@-------.---> Date: 2/17/2005 5:53:00 AM Another way to do this, which may or may not be convenient, is to use an XSLT script to tailor a schema for each of your hardware types. XSLT can read multiple documents, so you could have one input document that's a skeleton schema, and another with the constraint values, using XSLT to merge them. If you prefer, you could burry the entire skeleton into the XSL stylesheet as a template, using a single input document with the key values. -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 -------------------------------------- "Bryce K. Nielsen" <bryce@s...> Sent by: xmlschema-dev-request@w... 02/16/05 12:42 AM To: <xmlschema-dev@w...> cc: (bcc: Noah Mendelsohn/Cambridge/IBM) Subject: Re: Facets > This method only works if I had previous knowledge of the enumerated values. > In my case users create their own set of Types (not a subset of acceptable > values by my schema, but literally using their own naming conventions). For > instance, depending on the hardware under test, the user will compose a > totally different measurement Types. > Ah. Well, W3C XML Schemas don't inhierently support this "dynamic" schema contruction. You will probably need to use a stylesheet to validate, or perhaps schematron. Bryce K. Nielsen SysOnyx, Inc. (www.sysonyx.com) Read the origins of xmlDraft, the Smart XSD Editor: http://www.sysonyx.com/xml-schema-editor From Farid.Mahini@L... Thu Feb 17 17:13:12 2005 Received: from bart.w3.org ([128.30. | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
