IWSubElements

tobias

Hi,
I have a question regarding DCT design:
What is the purpose of <container> elements named "IWSubElements"?
These containers are generated for instance when you use TS's "iwdtd2dct" CLT.

Here's a snipped from my DTD:

<!ELEMENT IDs (ID)*>
<!ELEMENT ID (#PCDATA)>

The resulting DCT code looks like this:

<container location="IDs" name="IDs">
  <label>IDs</label>
  <description/>
  <container combination="and" location="" max="unbounded" min="0" name="IWSubElements">
    <label>IWSubElements</label>
    <description/>
    <item name="ID" pathid="ID">
      <label>ID</label>
      <description/>
      <text/>
    </item>
  </container>
</container>

Which looks overdone to me becaus it only adds another level of nesting which seems to be totally unnecessary (especially since it is displayed in the GUI and doesn't seem to have any added value to the DCT).
Couldn't the same be achieved with the following DCT code:

<container location="IDs" name="IDs">
  <label>IDs</label>
  <description/>
  <item name="ID" pathid="ID">
    <label>ID</label>
    <description/>
    <text/>
  </item>
</container>

Thanks for your help and thoughts on this issue.
Tobias

PS: I am using TS 6.5 SP2 on Windows. The 6.5 TST documentation doesn't explain the function of these <container> elements properly.

Adam Stoller

Hi, I have a question regarding DCT design: What is the purpose of <container> elements named "IWSubElements"? These containers are generated for instance when you use TS's "iwdtd2dct" CLT. Here's a snipped from my DTD: <!ELEMENT IDs (ID)*> <!ELEMENT ID (#PCDATA)> The resulting DCT code looks like this: <container location="IDs" name="IDs"> <label>IDs</label> <description/> <container combination="and" location="" max="unbounded" min="0" name="IWSubElements"> <label>IWSubElements</label> <description/> <item name="ID" pathid="ID"> <label>ID</label> <description/> <text/> </item> </container> </container> Which looks overdone to me becaus it only adds another level of nesting which seems to be totally unnecessary (especially since it is displayed in the GUI and doesn't seem to have any added value to the DCT). Couldn't the same be achieved with the following DCT code: <container location="IDs" name="IDs"> <label>IDs</label> <description/> <item name="ID" pathid="ID"> <label>ID</label> <description/> <text/> </item> </container> Thanks for your help and thoughts on this issue. Tobias PS: I am using TS 6.5 SP2 on Windows. The 6.5 TST documentation doesn't explain the function of these <container> elements properly.

I'd say you're half-right - the example you posted at the end would not work because it does not provide for the replication of the ID field as indicated by the DTD.
The resultant code that was created does provide for this.
However, I believe you can acheive the same result with:

<container location="IDs" name="IDs">
  <label>IDs</label>
  <description/>
    <item name="ID" pathid="ID" min="0" max="unbounded">
      <label>ID</label>
      <description/>
      <text/>
    </item>
</container>

in this partular case. If you had multiple items that should be replicated as a set - like:

<!ELEMENT IDs (ID,Name)*>
<!ELEMENT ID (#PCDATA)>
<!ELEMENT Name (#PCDATA)>

then you'd need the extra container structure to do that.