Thanks, Paul. I know it's hard to be the bearer of bad news. 🙂
In light of this roadblock, I wonder what my options are for going with processing instructions instead. Can a FOSI deal with custom PIs? I see that it knows about Arbortext touchup PIs, but can it deal with 3rdparty PIs? I've read the 5.1 help in this regard, but it's not clear to me if something like a UDT could be used or not.
Paul Grosso scribbled on 3/17/05 1:13 PM: > Peter, > > You don't have tag omission indicators (the - - or > - O things in most SGML DTDs) so I'm guessing this > is an XML DTD. > > In XML, you cannot have exceptions which is what > +(revst | revend) > are. Epic 4.2.1 didn't really parse XML DTDs as > XML, so you might have gotten away with this, but > such is not valid in an XML DTD, and EPic 5.1 now > enforces this. > > Unfortunately, there is really no construct in XML > that allows for the same functionality as exceptions. > It is actually pretty hard to say that revst and revend > are allowed everywhere. > > The best you can probably do is add revst|revend to all > your content models. > > paul > > >