nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

data-capture-requirements element

Vid

what does the type attribute in the data-capture-requirements element used for? what are the options available for the type attribute

Find more posts tagged with

Comments

kaalraa

what does the type attribute in the data-capture-requirements element used for? what are the options available for the type attribute

Can you please specify as on what environment you are working on?

Vid

Teamsite 6.1, Windows

kaalraa

Teamsite 6.1, Windows

It is not in use... beyond version 6. It was used in version 4 and 5 of TS.

Vid

what purpose did it serve in the earlier versions?

kaalraa

what purpose did it serve in the earlier versions?

It was used for mapping of category and data-type within templating.cfg. The type attribute is for category and name attribute is for data-type.

Adam Stoller

It was used for mapping of category and data-type within templating.cfg. The type attribute is for category and name attribute is for data-type.

Considering that the legal values were "content", "metadata", and/or "workflow" - I don't think your explanation is correct.

I believe it was used to distinguish the XML record as being from templating (later to be called FormsPublisher) DCTs, metadata capture DCT, and/or workflow records.

However, as has been pointed out (by you) - it's no longer part of the definition for the data-capture-requirements element.

kaalraa

Considering that the legal values were "content", "metadata", and/or "workflow" - I don't think your explanation is correct.
I believe it was used to distinguish the XML record as being from templating (later to be called FormsPublisher) DCTs, metadata capture DCT, and/or workflow records.
However, as has been pointed out (by you) - it's no longer part of the definition for the data-capture-requirements element.

Thanks Adam. But if you can, could you please explain a bit more on all three legal values?

Adam Stoller

Thanks Adam. But if you can, could you please explain a bit more on all three legal values?

Prior to 6.x the DTD specified:

<!ELEMENT data-capture-requirements (symbol-table?,ruleset+)> 
        <!ATTLIST data-capture-requirements 
          name                   CDATA                        #IMPLIED 
          type                   (metadata|content|workflow)  #REQUIRED 
          dtd-system-identifier  CDATA                        #IMPLIED 
          >

In 6.x it's defined as:

<!ELEMENT data-capture-requirements (ruleset)> 
<!ATTLIST data-capture-requirements 
  name CDATA #IMPLIED 
  dtd-system-identifier CDATA #IMPLIED 
  dcr-validation (none|accept-invalid|reject-invalid) "none" 
>

which, as you pointed out no longer defines the type attribute.

Vid

ah ok thanks!

kaalraa

ah ok thanks!

THANKS TO ADAM.