source: BMXNET_RPMS_dotNET_UTILITIES-BMX/branch/IHS BMX Framework/IndianHealthService.BMXNet.GeneratedDocumentation/Help/Settings/tokens.xml@ 1153

<?xml version="1.0" encoding="utf-8" ?>
<!--
  This document specifies shared content tokens for both conceptual and 
  auto-generated reference topics.
  
  NOTE: Unlike typical shared content documents, recursion is not supported.
  
  The following example defines a content item that will replace "msdn" tokens
  with a MAML link and some text.
  
  <item id="msdn">
    the <ddue:externalLink>
      <ddue:linkText>MSDN online</ddue:linkText>
      <ddue:linkUri>http://msdn2.microsoft.com</ddue:linkUri>
    </ddue:externalLink> web site
  </item>
  
  The following example uses the previously defined content item in a MAML 
  paragraph.
  
  <section>
    <title/>
    <content>
      <para>
        Visit <token>msdn</token> to find related articles.
      </para>
    </content>
  </section>
  
  The following example defines a content item that will expand "company" 
  tokens into the full name of a company.
  
  <item id="company">My Company, Inc.</item>
  
  The following example uses the previously defined content item in the 
  remarks section of XML documentation comments for some API.
  
  <remarks>
    <para>
      The implementation being used was originally developed by 
      <token>company</token> in 1993.
    </para>
  </remarks>
  
  - The id attribute is not case-sensitive.
  - Items may contain text, markup or both.
  - MAML markup requires the ddue: prefix to be specified.  Therefore, 
    tokens with MAML content cannot be used by tokens that appear in 
    XML documentation comments.
  -->
<items xml:space="preserve" xmlns:ddue="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:xlink="http://www.w3.org/1999/xlink">
  <!-- Add content items here -->
</items>