dtd-system-identifier in !DOCTYPE vs data-capture-requirements

What are the implications of putting the dtd-system-identifier in the !DOCTYPE versus the data-capture-requirements?

For example, in the Templating Developer Guide (v 6.5) pg 30, the following code is presented.

!DOCTYPE data-capture-requirements SYSTEM "datacapture6.0.dtd"

data-capture-requirements dtd-system-identifier="http://localhost/iw/pr.dtd" name="press-release"

When saving the DCR, the system would overwrite the datacapture6.0.dtd in the !DOCTYPE and replace it with the dtd-system-identifier="http://localhost/iw/pr.dtd"

Then what is the purpose of having both and not just have the !DOCTYPE populated with the correct dtd?

Or does the symtem use the !DOCTYPE datacapture6.0.dtd first for something and then the saved DCR need the new dtd to validate against?

Find more posts tagged with

Comments

ccastro

The only thing that comes to my head is that the datacapture uses the datacapture6.0.dtd to validate it self and that once a DCR is created against the datacapture.cfg , the datacapture6.0.dtd is no longer fiting to validate the generated DCR and a new dtd is needed. In this case the pr.dtd validates the DCR against it.

Else if there is no second dtd declared then the generated DCR would not be formated and would follow the forms hierchy.

Would this be correct?

ISCBorisB

The only thing that comes to my head is that the datacapture uses the datacapture6.0.dtd to validate it self and that once a DCR is created against the datacapture.cfg , the datacapture6.0.dtd is no longer fiting to validate the generated DCR and a new dtd is needed. In this case the pr.dtd validates the DCR against it.

Else if there is no second dtd declared then the generated DCR would not be formated and would follow the forms hierchy.

Would this be correct?

You are talking about two absolutely different XML Structures. One is Datacapture Template (datacapture.cfg).
It defines Datacapture Layout, look and feel and (to a certain degree) Form's functionality.

Another is Datacapture Record structure (collection of DCRs of some Category/Type). That defines (captured) Data,
nothing more. To be sure, DCR is built with the use of DCT. They are still structurally different and therefore
have different DTDs, what's so strange about that?

In the templating Guide IWOV uses their made-up "Press Release" sample, that's where pr.dtd is coming from.
You can basically have two types of DCRs ( not DCTs! ), iwov and xml, see explanation and samples of dcr-type attribute
of the <data-type> tag. XML Type is currently recommended one, you have to provide DTD if you use it. (You do not
need dtd-system-identifier attribute if dcr-type is "iwov". If that's the case you do not have any control over DCR
structure either). IMO placing custom DTD reference right into <data-type> Tag would have been more logical but that's just me.

HTH