rueger |
Newbie |
|
|
|
|
None Specified |
|
Friday, August 7, 2015 |
Tuesday, February 21, 2017 6:39:53 PM |
3 [0.02% of all post / 0.00 posts per day] |
|
@island too bad. @vlad this is, what I'm actualy doing but want to avoid cause this extremly expands the schema size and requires verbose commitments beyond extension markup formalism. Compared to the lots of options that specify all kinds of data formats (up to complex regular expressions) decryption of enummerations etc, is awfully unattended... Anyway thank you .. and bye HHR
|
@support engineer ... and cannot be bypassed ? Thank you - so far HHR
|
Hi, to more easy derive a data input .NET menu directly from the XML schema definition file 'myXSD', I was thinking of 1. customizing the XSD-schema-schema as follows: extend the <xs:element name="CODE_X" node with attributes: - capture="text_in_here_to_decode_CODE_X" - default="42" - hint="CODE_X_more_detailed" 2. download the schema-schema from xmlns:xs="http://www.w3.org/2001/XMLSchema 3. imlement the changes above and 4. give it a local reference to let AS validate myXSD with the customized schema-schema. Of course (!) this doesn't work (? where does AS get the XSD-schema validation schema from ?). What else has to be done to solve the problem? Thanks a lot HHR
|
|