Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>targetNamespace</strong> is an XML Schema "artifact"; its purpose: to indicate what particular XML namespace the schema file describes.</p> <p><strong>xmlns</strong> - because the XML Schema is an XML document, it is then possible to define a default XML namespace for the XML file itself (this is what xmlns attribute does); the implications are multiple: authoring, and composition. For example, one does not have to use a prefix for the items defined in the schema, that are later on referenced elsewhere in the same file (e.g. a global simpleType used as a type for an attribute or element).</p> <p>From my experience, many XML Schema authors consider this as a "best practice"... so you're on the right track.</p> <p>In terms of XSD, the targetNamespace prescribes the namespace part of a qualified name of a schema component, which includes elements, attributes, groups and attribute groups, and simple and complex types. Some of the qualified names defined in an XSD (elements and attributes) are "directly" used by an XML instance document. Others, such as for types, can be referenced through the <a href="http://www.w3.org/TR/xmlschema-1/#xsi_type" rel="noreferrer">xsi:type</a> attribute in instance XML documents. The rest (groups, attribute groups) are there to facilitate schema composition (through references). </p> <p>I'm also of opinion that (in general) people come at designing XSD from two angles:</p> <ul> <li><p>to match an existing XML. In this case, if your XML uses namespaces, for each of the namespaces used, you'll end up with an XSD schema element with a matching targetNamespace attribute.</p></li> <li><p>pure modeling. You then think of targetNamespace similar to an UML package, or database schema, or a Java package, or a .NET namespace, and all it means in this case. Fundamentally it is a mechanism to avoid naming collisions; nonetheless, it is also a mechanism to partition models in subject areas, etc.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POtargetNamespace and xmlns without prefix, what is the difference?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPetru Gardea
    1. USPetru Gardea
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POtargetNamespace and xmlns without prefix, what is the difference?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload