Constraining an xs:any element with some predefined attributes
I am trying to create an XSD schema where I have a root element, namely context, with some attributes and any sub-elements.
But the problem is: these sub-elements are subject to have some attributes as well. In other way to express, there can be any number of child elements in context elements, but these child elements must have some required and optional attributes.
When I try to create the schema with Liquid Studio, it doesn't allow me to write any content in xs:any element to define attributes. And I could not find a solution on the internet.
Is there any way to define some constraints to an xs:any element?
Below is a SS from my attempted code :
xml xsd schema
asked Nov 22 '18 at 21:55
iteyran
54313
add a comment |
I am trying to create an XSD schema where I have a root element, namely context, with some attributes and any sub-elements.
But the problem is: these sub-elements are subject to have some attributes as well. In other way to express, there can be any number of child elements in context elements, but these child elements must have some required and optional attributes.
When I try to create the schema with Liquid Studio, it doesn't allow me to write any content in xs:any element to define attributes. And I could not find a solution on the internet.
Is there any way to define some constraints to an xs:any element?
Below is a SS from my attempted code :
xml xsd schema
asked Nov 22 '18 at 21:55
iteyran
54313
add a comment |
I am trying to create an XSD schema where I have a root element, namely context, with some attributes and any sub-elements.
But the problem is: these sub-elements are subject to have some attributes as well. In other way to express, there can be any number of child elements in context elements, but these child elements must have some required and optional attributes.
When I try to create the schema with Liquid Studio, it doesn't allow me to write any content in xs:any element to define attributes. And I could not find a solution on the internet.
Is there any way to define some constraints to an xs:any element?
Below is a SS from my attempted code :
xml xsd schema
asked Nov 22 '18 at 21:55
iteyran
54313
I am trying to create an XSD schema where I have a root element, namely context, with some attributes and any sub-elements.
But the problem is: these sub-elements are subject to have some attributes as well. In other way to express, there can be any number of child elements in context elements, but these child elements must have some required and optional attributes.
When I try to create the schema with Liquid Studio, it doesn't allow me to write any content in xs:any element to define attributes. And I could not find a solution on the internet.
Is there any way to define some constraints to an xs:any element?
Below is a SS from my attempted code :
xml xsd schema
xml xsd schema
asked Nov 22 '18 at 21:55
iteyran
54313
asked Nov 22 '18 at 21:55
iteyran
54313
edited Nov 23 '18 at 7:34
asked Nov 22 '18 at 21:55
iteyran
54313
asked Nov 22 '18 at 21:55
iteyran
54313
asked Nov 22 '18 at 21:55
iteyran
54313
54313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Yes, it's an unfortunate limitation of xs:any wildcards that you can't constrain the type/content of the elements that match, you can only constrain their element names.
In XSD 1.1 you can get around this by using assertions.
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53438388%2fconstraining-an-xsany-element-with-some-predefined-attributes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, it's an unfortunate limitation of xs:any wildcards that you can't constrain the type/content of the elements that match, you can only constrain their element names.
In XSD 1.1 you can get around this by using assertions.
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
add a comment |
Yes, it's an unfortunate limitation of xs:any wildcards that you can't constrain the type/content of the elements that match, you can only constrain their element names.
In XSD 1.1 you can get around this by using assertions.
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
add a comment |
Yes, it's an unfortunate limitation of xs:any wildcards that you can't constrain the type/content of the elements that match, you can only constrain their element names.
In XSD 1.1 you can get around this by using assertions.
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
Yes, it's an unfortunate limitation of xs:any wildcards that you can't constrain the type/content of the elements that match, you can only constrain their element names.
In XSD 1.1 you can get around this by using assertions.
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
answered Nov 23 '18 at 9:07
Michael Kay
108k660114
108k660114
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53438388%2fconstraining-an-xsany-element-with-some-predefined-attributes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
