refType

<h:div class="summary">A reference to an existing object.</h:div>
<h:div class="description">A reference to an existing element in the doc. The target of the ref attribute must exist. The test for validity will normally occur in the element's _appinfo_. Any DOM Node created from this element will normally be a reference to another Node, so that if the target node is modified a the dereferenced content is modified. At present there are no deep copy semantics hardcoded into the schema.</h:div>
<h:div class="description">The semantic of reference are normally identical to an idType (e.g. "a123b"). Howevere there are some cases where compound references are required, such as "a123b:pq456". It is likely that this will be superseded at by RDF or Xpointer, but as long as we have non-uniqueIds this is a problem</h:div>

Simple Type Information

Used By

Source

<xsd:simpleType name="refType" id="st.refType">
  <xsd:annotation>
    <xsd:documentation>
      <h:div class="summary">A reference to an existing object.</h:div>
      <h:div class="description">A reference to an existing element in the doc. The target of the ref attribute must exist. The test for validity will normally occur in the element's _appinfo_. Any DOM Node created from this element will normally be a reference to another Node, so that if the target node is modified a the dereferenced content is modified. At present there are no deep copy semantics hardcoded into the schema.</h:div>
      <h:div class="description">The semantic of reference are normally identical to an idType (e.g. "a123b"). Howevere there are some cases where compound references are required, such as "a123b:pq456". It is likely that this will be superseded at by RDF or Xpointer, but as long as we have non-uniqueIds this is a problem</h:div>
    </xsd:documentation>
  </xsd:annotation>
  <xsd:restriction base="xsd:string">
    <xsd:pattern value="([A-Za-z_][A-Za-z0-9_\.\-]*:)?[A-Za-z_][A-Za-z0-9_\.\-]*"/>
  </xsd:restriction>
</xsd:simpleType>