The DevCenter has moved!

The Developer Center has a new home, developer.ektron.com. The site you are currently viewing is available as a read-only archive.
Things to note:
  1. Your username & password is the same on the new site, developer.ektron.com
  2. Going forward, please use the new URL, developer.ektron.com
  3. The old discussion forums and old KB articles are still available as an archive (read-only)

Ektron Knowledge Base

The Knowledge Base has thousands of articles describing open and past issues and providing answers to frequently asked questions.

Hover the mouse over to the side bar to open a side menu and expend a node for a list of articles.

INFO: XML Schema targetNamespace

Applies To:
eWebEditPro
Summary:

Recommendations on the use of targetNamespace, elementFormDefault and attributeFormDefault attributes in an XML Schema.

If the XML schema contains the targetNamespace attribute, then the XSLT must declare that namespace and assign a prefix. The prefix must then be used in the templates' XPath expressions. If you are using a published XML Schema, then it may have a targetNamespace defined and you will need to declare that namespace URI in your XSLT.

Recommendations

targetNamespace should not be set

elementFormDefault set to "qualified"

attributeFormDefault set to "unqualified" (this is the default)

Example

<xsd:schema targetNamespace="urn:myschema" xmlns:xsd=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

The default value for attributeFormDefault is "unqualified".

More Resources:
Tips for Designing an XML DTD or Schema XML processing, part 3: XML Schemas XSLT: namespaces XSLT: XPath select statements do not match XML or XHTML with a default namespace Some XML tags, like menu and button, are lost or corrupted

Guidelines for working with W3C XML Schema: