[ilia]

Anthony,

You now can download the XML 2004 conference proceedings support
for Serna 1: http://downloads.syntext.com/ideadb-serna-1.zip

Just unzip the package in sernaInstallationPath/Serna/xml directory
(i.e. C:\Program Files\Syntext\Serna\xml )

Note, that this package will overwrite catalog.xml. So that, if you have
locally modified it, please make a backup copy.

The package will work fine with your document, if you add to it the
DOCTYPE definition before the document element:

<!DOCTYPE article PUBLIC "-//IDEAlliance//DTD Conference Paper DocBook XML Subset V1.0//EN"
"ideadb.dtd">

In the next sections I explain in details why the package works.



*** The ID problem.

The weird ID behavior was caused by the fact, that Serna uses DTD to
determine the ID attributes. If there is only a schema, then ID table is not
initialized. This is actually a missing use-case in Serna. So far there
were always the XML documents that were coming with DTDs or required DTDs
because of the entities. We'll fix the problem.

For now, if you add the DOCTYPE definition to your documents: it will work
fine. I would say, that it is more correct to use the DOCTYPE, because:

- it will allow DTD-enabled tools to work with your document
- it will allow Serna 1 to automatically guess the doctype, stylesheet, etc.

*** The changes to your document template: idealalliance-template.xml

Here is the document template from the package. All changes are
commented:

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE t:document-template PUBLIC "-//Syntext//DTD Syntext Document Template V1.0//EN" "doctemplate.dtd" []>
<t:document-template xmlns:t="http://www.syntext.com/Extensions/DocTemplate-1.0">
<t:name>IDEAlliance/Proceedings</t:name>
<t:xml-stylesheet>$SERNA_STYLESHEETS/docbook/docbook.xsl</t:xml-stylesheet>

<!-- This makes Serna creating new proceedings document with the PUBID -->
<t:dtd-pubid>-//IDEAlliance//DTD Conference Paper DocBook XML Subset V1.0//EN</t:dtd-pubid>

<!-- This makes Serna creating new proceedings document with the SYSID -->
<t:dtd-sysid>ideadb.dtd</t:dtd-sysid>

<!-- This will allow Serna to guess the doctype and use this template -->
<t:dtd-guess-string>IDEAlliance//DTD.*V1.0</t:dtd-guess-string>

<!-- Note that $SERNA_XML variable is used for getting the path to
sernaInstallationPath/Serna/xml directory.
We converted the IDEAlliance DTD with Syntext DTD2XS converter:
http://www.syntext.com/products/index.htm#Dtd2Xs
-->
<t:xml-schema>$SERNA_XML/ideadb-1.0/xsd/ideadb-syntext-dtd2xs.xsd</t:xml-schema>

<t:open-document/>
<t:document-root>
<article>
<title/>
</article>
</t:document-root>
</t:document-template>

4. Package for Serna 2

We'll ship next Serna 2 beta together with the IDEAlliance package for
Serna 2. If you are interested to have it ASAP, please let me know.

Ilia Kuznetsov

On Mon, 2 Aug 2004, Ilia Kuznetsov wrote:

> Anthony,
>
> We'll try to fix the problem. May you please e-mail me:
>
> - The DTD
> - The schema
> - The document
>
> Also, what version of Serna do you use?
>
> Looking forward,
> Ilia Kuznetsov
>
> On Sat, 31 Jul 2004, Anthony B. Coates wrote:
>
> > A bit more experimenting, and I find that if I go to each element with an
> > ID, then open the attributes dialog, select the ID value, and hit return,
> > it makes that ID 'visible' to Serna again, i.e. available in the dropdown
> > for IDREFs. So I get the impression that Serna is not picking up the ID
> > values when it loads the file. Could that be possible? Thanks very much
> > in advance,
> >
> > Cheers,
> > Tony.
> >
> > On Sat, 31 Jul 2004 19:49:59 +0100, Anthony B. Coates
> > <abcoates@idmm.co.uk> wrote:
> >
> > > My second attempt was to generate a Schema from the conference DTD using
> > > TurboXML. That fixes the problem with <xref.char.class> coming up
> > > instead
> > > of <xref>, but I am finding a bit weird with IDs and IDREFs. When I
> > > create a new ID on an element, and then create an <xref> to it, Serna
> > > lets
> > > me choose the value of the @linkend (IDREF) attribute from a drop-down
> > > list of the IDs in the document. If I validate the document now,
> > > everything is OK.
> > >
> > > If I subsequently close and re-open the document, the @linkend IDREFs are
> > > suddenly flagged as invalid, and no amount of editing will fix that.
> > > Also, if you try to change the @linkend value, no dropdown box of values
> > > appears.
> > >
> > > Is this a known bug, or something that can be easily worked around?
> > > Thanks a lot in advance,
> > >
> > > Cheers,
> > > Tony.