StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4546916
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-12-28T14:55:44.613
FavoriteCount
0
LastActivityDate
2010-12-28T14:55:44.613
LastEditDate
LastEditorUserId
0
OwnerUserId
162354
ParentId
4545367
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I hope I understand the question correctly... inside <code><details></code>, you want to allow any element from any namespace, but if the elements are in <code>http://example.org/apples</code> (SIR I HAVE TO ASK YOU, DO YOU OWN THE EXAMPLE.ORG DOMAIN? :D), then you want to validate those. Easy enough. <ol> <li>In your main schema file <code>someschema.xsd</code>, do something like: <pre><code><?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:someschema" elementFormDefault="qualified" > <xs:import namespace="http://example.org/apples" schemaLocation="apples.xsd" />  <xs:complexType name="details"> <xs:sequence maxOccurs="unbounded"> <xs:any minOccurs="0" processContents="lax" /> </xs:sequence> </xs:complexType> </xs:schema> </code></pre></li> <li>create an <code>apples.xsd</code>: <pre><code><?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.org/apples" elementFormDefault="qualified" > <xs:element name="color"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="red" /> <xs:enumeration value="green" /> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="cultivar"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Braeburn" /> <xs:enumeration value="Granny Smith" /> <xs:enumeration value="McIntosh" /> </xs:restriction> </xs:simpleType> </xs:element> </xs:schema> </code></pre></li> <li>???</li> <li>Profit!</li> </ol> The important thing is that for those foreign namespaces you do want to validate inside <code><details></code>, you need to import the corresponding schema file at the top of your schema. This actually leverages the fact that XML Schema is utterly retarded and not even capable of defining what the root element of your document is. Theoretically, you could alternatively also omit the <code><import></code>, and instead simply validate your document against both <code>someschema.xsd</code> and <code>apples.xsd</code> (haven't tested that though).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXML Schema Validation: How to validate "embedded" documents?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdzuelke
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COFor your example.org bashing: These domain names are reserved for use in documentation and are not available for registration. See RFC 2606, Section 3. ;-)
 singulars
 PostPostId
 PO
 UserUserId
 USMalax

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.