[osis-core] work element

[Patrick Durusau]

Harry,

I think that is an typing error on my part. When we added <works> to 
contain <work>, all the header metadata should go inside 
<works><work>metadata</work></works>

Gathers all those items into one container.

Note on Todd's suggestion that we do ID/IDREF, recall the XML Names 
limitations, i.e., no names that start with numbers, etc.

I am not unhappy with that restriction but just so we are aware that you 
could not do 1A.Barth.Church_Dogmatics if we are using traditional 
ID/IDREF.

I may try to look at the key mechanism since unlike our earlier attempt 
to use it with milestones, this is a fixed location in the header (as 
opposed to relative XPath expressions)  and might be a good case for 
their use.

Patrick

Harry Plantinga wrote:

>In 1.1_003, the <work> element is required in the <header>.
>(At least, that's the effect of not having a "minOccurs"
>attribute in XMetaL.)
>
>Is that intentional?  It contains more or less the same
>elements as the <header> itself, so what is its purpose
>when it is not inside a <works> element?
>
>-Harry
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu