|
|
Rank: Newbie
Joined: 8/7/2015
Posts: 3
|
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
|
|
Rank: Member
Joined: 12/11/2013
Posts: 18
Location: everywhere
|
With respect to validation the schema for schemas is hardcoded in the software.
|
|
Rank: Newbie
Joined: 8/7/2015
Posts: 3
|
@support engineer
... and cannot be bypassed ?
Thank you - so far
HHR
|
|
Rank: Newbie
Joined: 10/28/2002
Posts: 1,283
Location: AT
|
Quote:... and cannot be bypassed ?
No, this cannot be bypassed
|
|
Rank: Advanced Member
Joined: 12/13/2005
Posts: 2,856
Location: Mauritius
|
You are obviously trying to supply additional information to your schema. Instead of modifying schema for schema, which is a really bad idea, you should use annotation section which can be added to elements, attributes, and all other schema components
|
|
Rank: Newbie
Joined: 8/7/2015
Posts: 3
|
@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
|
|
|
guest |
