Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
What is the point of root-container
System
I was having difficulty getting some FormAPI to work consistently in two templates that I thought were pretty similar. After a little poking around, I discovered that one of the templates was validating against the datacapture5.0.dtd and did not have a root-container element. The other was validating against the datacapture6.0.dtd and did have a root-container. I see that the 6.0 dtd no longer allows items to appear directly within a ruleset but requires a root-container.
The questions this prompts is: what's the point of root-container? My plan is to make all the templates conform to the 6.0 DTD, add a root-container, and make it's name and location both "root". The previous developer used a different value for name and location for each template. That makes it impossible to use one common formapi file. Is there any reason that my plan is unsound? Pages 38-39 of the 6.0 templating dev manual aren't helping me out here.
I don't really see the value of root-container either. Why did they choose to require it rather than just letting a developer put an or container with a min and max of 1 at the root level if they so chose?
Find more posts tagged with
Comments
There are no comments yet