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

I do not understand when a custom dtd is needed

System

I was following the manual examples for FormAPI and creating a custom dtd for each DCT that uses FormAPI. But then I realized that I forgot to create a custom dtd for one DCT and it still works perfectly. So, now I am confused as to when they are needed. I don't want to create work for myself. So if they're not needed, I don't want to waste my time. Anyone have some insight on this?

Find more posts tagged with

Comments

Migrateduser

It seems that no one wants to answer this question. Surely someone out there can shed some light on this? Please?

Adam Stoller

I was following the manual examples for FormAPI and creating a custom dtd for each DCT that uses FormAPI. But then I realized that I forgot to create a custom dtd for one DCT and it still works perfectly. So, now I am confused as to when they are needed. I don't want to create work for myself. So if they're not needed, I don't want to waste my time. Anyone have some insight on this?

I don't believe there is any aspect of FormAPI that requires a custom DTD.
You can create a custom DTD for a DCT and use that DTD to validate structural aspects of the populated DCT (a.k.a. DCR) - but that's not required and has nothing to do with FormAPI (which can also be used to validate the contents of a populated DCT)

So - yes - I think you're making more work for yourself - but that's based on a very limited knowledge of what you are trying to do.

Migrateduser

Thank you for your reply! I have just learned to use FormAPI and I am really impressed with what I can do now. I will test to ensure each dct works without the custom dtd. I just wanted assurance that this was a good course of action. Thanks again