Re: Allow <info> as root element?

I make most or all elements start elements in my DocBook variants because wh=
y not? What if you want to xi:include a <phrase> or a <note> multiple times (=
and find entities to be kludgy and gross)? Put it in a file and xi:include t=
hat file as needed. No need for an id or id fixup. =20

I also consider making a variant good practice. Nobody needs all of DocBook a=
nd changes like adding start elements have little effect on interoperability=
.=20

Regards,
David

Typed wtih thmubs=20

> On Nov 29, 2022, at 5:51 PM, Richard Hamilton <[email protected]> wrot=
e:
>=20
> =EF=BB=BFI=E2=80=99ve run into the same thing. I have a separate file for o=
ur book info, so that I can move the copyright page to the back of the book f=
or ebooks.
>=20
> I am lazy, however, and just ignore the errors when I=E2=80=99m editing th=
e info page:-). I essentially do what Norm mentioned; that is, only pay atte=
ntion to validation when the block is included in a book.
>=20
> The other thing you could do, if you=E2=80=99re using xinclude, is to put t=
he info block into a valid root element, so you can validate it, then use xi=
nclude to include just the info element when you build a deliverable.
>=20
> I=E2=80=99m not sure how doable that is with assemblies.
>=20
> Dick Hamilton
> -------
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> [email protected]
>=20
>=20
>=20
>> On Nov 29, 2022, at 14:03, Thomas Schraitle <[email protected]> wrote:
>>=20
>> Hi,
>>=20
>> On 28.11.22 11:10, Norm Tovey-Walsh wrote:
>>>> currently, DocBook v5.2 (and previous versions) allows several elements=
 as root
>>>> element. However, it is currently not possible to use info "alone". Any=
 reasons
>>>> why?
>>>=20
>>> I can see how reusing metadata might make sense in some environments. I
>>> won=E2=80=99t speak for anyone else on the TC, but I tend to think of it=
 as
>>> being attached to something. It provides metadata for an element, and so=

>>> it=E2=80=99s not immediately obvious what it means sitting on its own.
>>>=20
>>> It isn=E2=80=99t that I thought there was any reason to forbid it so muc=
h as it
>>> never occurred to me that it would be useful.
>>=20
>> I know, this use case may be not very common. Still I think, if you use
>> assemblies and share content it might become more helpful, especially whe=
n you
>> want (or need to) validate on its own.
>>=20
>>=20
>>>> Imagine you would like to share some common meta information among seve=
ral
>>>> articles:
>>>=20
>>> There=E2=80=99s obviously nothing that prevents you from doing this. You=
 can
>>> XInclude this metadata file into several articles and then validate
>>> them.
>>>=20
>>> It would be a very simple Relax-NG customization to allow info in the
>>> =E2=80=9Cstart=E2=80=9D pattern then it could be validated independently=
.
>>=20
>> That's true, but that wouldn't be DocBook anymore. ;) Thus validating wou=
ldn't
>> work.
>>=20
>>=20
>> --
>> Gru=C3=9F/Regards
>> Thomas Schraitle
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>=20