[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: docbook xml.schema
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Frédéric Glorieux <frederic.glorieux@ajlsm.com> was heard to say: |> | Probably nice, you are a master of XML style. But is it stable ? | Should |> | I use <xs:redefine/> like on an other official declared schema ? |> |> If you're using it, and your tool supports redefine, go for it. I |> can't promise the schema is stable before it's official (which is most |> likely to occur at the next release) but I don't think it's going to |> change in any dramatic way. | | Is this the one under CVS or should I generate it with the last | trang? Try the one under docbook/schema/xmlschema/ I think that's the most up-to-date. | For real life, a shorter schema for each root element appears me | better (generation probably possible), especially when there are | different jobs (bibliography, article for redactors, toc for editors, | perhaps more; that will be the case in this organisation). | But you have more experience than me on those kinds of projects. | Any advice welcome. There are no "local" elements in DocBook, so a single schema can handle all those cases. I don't see any advantage to building versions that have only a subset of the declarations. Though if you see important performance improvements, you might want to anyway :-) Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | To create a little flower is the http://www.oasis-open.org/docbook/ | labour of ages.--Blake Chair, DocBook Technical Committee | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+d5+COyltUcwYWjsRAjfYAJ4viCzwWV7yBwdyGImh8o7EYXgDWwCeIu+M 6ok97F2IadZaUWw5tNqELuc= =P01i -----END PGP SIGNATURE-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]