[osis-core] Is this ready for OSIS 1.1? Header

[Harry Plantinga]

Todd,

I can make do with the revised header, which as a dataFormat attribute
for header elements. If I want to encode several different types of
"identifiers", I can give them different type and/or dataFormats.

I have some sympathy for a more filled-out header (witness the
baroque ThML.head element), but the answer here was to use
a TEI header if you need more than the basics.

-Harry
----- Original Message -----
From: "Todd Tillinghast" <todd@contentframeworks.com>
To: <osis-core@bibletechnologieswg.org>
Sent: Friday, July 05, 2002 3:42 PM
Subject: Re: [osis-core] Is this ready for OSIS 1.1? Header


> Did we address Harry's concerns regarding the header?
>
> I continue to find the header to be limiting.  It seems that any useful
> header will be a part of future release.  Should we consider splitting the
> header into its own schema (OSISHeader for example) and then include which
> ever header is most suitable in the non-abstract schema used.  (Of course
> this implies that OSISCore is abstract.)
>
> Shouldn't teiHeader be TEIHeader?
>
> Todd
>
>