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; } } }

DCT Challenge

Lee

I asked this question (possibly poorly) in another thread however it's become clogged with several questions and counter questions and answers. Any help on this would be greatly appreciated.

Can a teamsite DCT represent the following w3c schema structure.

xs:element name="body"
xs:complexType
xs:choice maxOccurs="unbounded"
xs:element name="paragraph" minOccurs="0"/
xs:element name="img" minOccurs="0"/
xs:element name="heading" minOccurs="0"/
/xs:choice
/xs:complexType
/xs:element

Can Anyone from interwoven confirm if this is possible ?

note:

container name="body" combination="or" max="unbounded
item name="para"
item name="img"
item name="heading"
/container

will produce

body
para
/body
body
img
/body
body
heading
/body
etc....

This is not what im after

Lee C

Find more posts tagged with

Comments

Migrateduser

You need the comination attribute on your container to be "and", not "or"

Lee

You need the comination attribute on your container to be "and", not "or"

Hi Rob,

The "And" combination will not model the above schema. It would produce a structure like:

body
para/
para/
para/
img/
img/
img/
heading/
heading/
heading/
/body

I want the elements to be in any order.

Lee C

Jeremy

Hi Rob,

The "And" combination will not model the above schema. It would produce a structure like:

body
para/
para/
para/
img/
img/
img/
heading/
heading/
heading/
/body

I want the elements to be in any order.

Lee C

What exactly are you wanting to achieve? It sounds like you're wanting the DCR to produce the XML required for your schema?
Why not write a simple presentation template to produce the XML in the format you want?

Lee

What exactly are you wanting to achieve? It sounds like you're wanting the DCR to produce the XML required for your schema?
Why not write a simple presentation template to produce the XML in the format you want?

Hi Jeremy,

I want the dcr to store content in sensible xml. (We are re-developing some templates and ideally would like to tidy up some of our past mistakes.)

The goal is to store our content into meaningful data structures which other applications may make use of. A different templating engine, another content repository, a translation web service etc. If our DCR's follow a sensible easy to use structure these external application integrations may be easier.

HTH

Lee C

Jeremy

Hi Jeremy,

I want the dcr to store content in sensible xml. (We are re-developing some templates and ideally would like to tidy up some of our past mistakes.)

The goal is to store our content into meaningful data structures which other applications may make use of. A different templating engine, another content repository, a translation web service etc. If our DCR's follow a sensible easy to use structure these external application integrations may be easier.

HTH

Lee C

Have you looked at a custom DTD for the DCT's? In your templating.cfg instead of dcr-type="iwov" you change that to dcr-type="xml"
See the Admin Guide for more details on xml dtd's.
I would guess you'd be able to get the XML to be produced in the format you'd want then.

Lee

Have you looked at a custom DTD for the DCT's? In your templating.cfg instead of dcr-type="iwov" you change that to dcr-type="xml"
See the Admin Guide for more details on xml dtd's.
I would guess you'd be able to get the XML to be produced in the format you'd want then.

Hi Jeremy,

Taken from the ts 6.0 templating guide pdf (page 55):

If there is an item with replicant behavior
(that is max greater than 1, such as item name='authorlist' pathid='header/
authors/author' max='unbounded'), the elements preceding author will be created if
they do not exist, but each author does not get its own authors parent.

This solves the general problem. However does not solve mine. We must use the classic DCR format (item / value pairs) to support backward compatibilty.
The new way (well new for us) of binding the DCT to an XML structure using xpath is great but we won't be migrating our existing DCR's just yet.

Any ideas with the classic format ??

Jeremy

So you're saying you want to use the classic xml and not the custom xml? Is that right?
If so then I think they only way you're going to get the format you want is by producing a generated xml file from a template.

Migrateduser

Hi Rob,

The "And" combination will not model the above schema. It would produce a structure like:

body
para/
para/
para/
img/
img/
img/
heading/
heading/
heading/
/body

I want the elements to be in any order.

Lee C

I'm not a big XML schema guy (mostly bc I primarily deal with it in TeamSite which hasn't got hip to schemas yet), so I didn't catch on that that was what you wanted. I think you could probably do that by putting an "or" container inside an "and" container. The thing I'm not sure about is what you would want to do with the location attribute on one of those containers. I don't know if you could leave it empty to keep from getting the extra level of nesting, or if you would have to do something like use an absolute xpath on the pathid of the actual items.

It's probably worth playing with if its that important to you

Migrateduser

Ignore the previous post. I had made the assumption based upon your xml snippet that you were already using xml type DCRs rather than iwov type. For what you want to do, you're not going to get it with iwov type DCRs.

Hi Jeremy,

Taken from the ts 6.0 templating guide pdf (page 55):

If there is an item with replicant behavior
(that is max greater than 1, such as item name='authorlist' pathid='header/
authors/author' max='unbounded'), the elements preceding author will be created if
they do not exist, but each author does not get its own authors parent.

This solves the general problem. However does not solve mine. We must use the classic DCR format (item / value pairs) to support backward compatibilty.
The new way (well new for us) of binding the DCT to an XML structure using xpath is great but we won't be migrating our existing DCR's just yet.

Any ideas with the classic format ??