DTD Modifications Issues
Posted: Mon May 19, 2014 7:23 pm
Hi,
I've been modifying my DTD and have two issues.
1) I want to allow @id attributes not to be unique anymore. For that, I replaced all the occurrences of the type of @id: from ID (i.e. a unique ID) to CDATA. I also made sure to replace those occurrences in dependent .dtd or .mod files. Still, it seems that a couple of @id won't be accepted as non-unique. I was wondering if there was a way to specify a single rule in the DTD to have all @id attributes to be CDATA.
2)I need to allow a table entry (marked up as <entry>) to have any kind of child element. The entry is declared as an entity, the following way:
<!ENTITY % tbl.entry.mdl "entity_values">
What I'd like is for the "entity_values" to have any content. I did a fair bit of research but wasn't able to find anything that enabled that. I found out about the "ANY" keyword for ELEMENT but that's not what I want. Right now, I hardcoded a few potential child tags (let's call them <value1>, <value2> etc...) for entity_values as a list ("value1 | value2 | ...") but that could potentially be very long.
Any input on one of those issues would be great!
Thanks,
Jonathan
I've been modifying my DTD and have two issues.
1) I want to allow @id attributes not to be unique anymore. For that, I replaced all the occurrences of the type of @id: from ID (i.e. a unique ID) to CDATA. I also made sure to replace those occurrences in dependent .dtd or .mod files. Still, it seems that a couple of @id won't be accepted as non-unique. I was wondering if there was a way to specify a single rule in the DTD to have all @id attributes to be CDATA.
2)I need to allow a table entry (marked up as <entry>) to have any kind of child element. The entry is declared as an entity, the following way:
<!ENTITY % tbl.entry.mdl "entity_values">
What I'd like is for the "entity_values" to have any content. I did a fair bit of research but wasn't able to find anything that enabled that. I found out about the "ANY" keyword for ELEMENT but that's not what I want. Right now, I hardcoded a few potential child tags (let's call them <value1>, <value2> etc...) for entity_values as a list ("value1 | value2 | ...") but that could potentially be very long.
Any input on one of those issues would be great!
Thanks,
Jonathan