TIM Plugin updates

[jwillmartin]

Summary

Currently, the TIM plugin only encodes Curve Speed Warning information in a non-standard XML into a TIM message. I would like to have all ITIS codes and text inputs accepted in a standard XML format and encoded into a TIM message.
Desired XML:

<MessageFrame>
  <messageId>31</messageId>
  <value>
    <TravelerInformation>
      <msgCnt>1</msgCnt>
      <timeStamp>115549</timeStamp>
      <packetID>000000000023667BAC</packetID>
      <dataFrames>
        <TravelerDataFrame>
          <sspTimRights>0</sspTimRights>
          <frameType>
            <advisory/>
          </frameType>
          <msgId>
            <roadSignID>
              <position>
                <lat>389549775</lat>
                <long>-771491835</long>
                <elevation>390</elevation>
              </position>
              <viewAngle>1111111111111111</viewAngle>
              <mutcdCode>
                <warning/>
              </mutcdCode>
            </roadSignID>
          </msgId>
          <startTime>115549</startTime>
          <duratonTime>1</duratonTime>
          <priority>7</priority>
          <sspLocationRights>0</sspLocationRights>
          <regions>
            <GeographicalPath>
              <anchor>
                <lat>389549775</lat>
                <long>-771491835</long>
                <elevation>390</elevation>
              </anchor>
              <directionality>
                <both/>
              </directionality>
              <closedPath>
                <true/>
              </closedPath>
              <description>
                <geometry>
                  <direction>1111111111111111</direction>
                  <circle>
                    <center>
                      <lat>389549775</lat>
                      <long>-771491835</long>
                      <elevation>390</elevation>
                    </center>
                    <radius>74</radius>
                    <units>
                      <meter/>
                    </units>
                  </circle>
                </geometry>
              </description>
            </GeographicalPath>
          </regions>
          <sspMsgRights1>0</sspMsgRights1>
          <sspMsgRights2>0</sspMsgRights2>
          <content>
            <advisory>
              <SEQUENCE>
                <item>
                  <itis>7186</itis>
                </item>
              </SEQUENCE>
              <SEQUENCE>
                <item>
                  <itis>9476</itis>
                </item>
              </SEQUENCE>
              <SEQUENCE>
                <item>
                  <itis>13569</itis>
                </item>
              </SEQUENCE>
            </advisory>
          </content>
          <url>987654321</url>
        </TravelerDataFrame>
      </dataFrames>
    </TravelerInformation>
  </value>
</MessageFrame>

Reasoning for new functionality

This will align with the entire TIM message frame, rather than focusing on a specific use case.