Subject: [drinks] TN / TNRange / TNPrefix

From: Otmar Lendl <[email-masked]>
Date: Wed, 15 Sep 2010 22:39:27 +0200

I just picked up an action item during the interim:

We were talking about how to denote prefixes (esp. for open numbering
plan), and David and I suggested that it's better and less likely to cause
confusion if there were an explicit prefix object, and not just a TNRange
with some attribute to flag it's actually a prefix.

Here is an off-the-cuff xsd proposal:

  <complexType name="TNType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="tn" type="string"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <complexType name="TNRType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="startTn" type="string"/>
          <element name="endTn" type="string"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <complexType name="TNPType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="prefix" type="string"/>
          <element name="minLen" type="integer" minOccurs="0" />
          <element name="maxLen" type="integer" minOccurs="0" />
        </sequence>
      </extension>
    </complexContent>
  </complexType>

cheers,

otmar
-- 
// Otmar Lendl <[email-masked]>, T: +43 1 5056416 - 33, F: - 933 //