On Thu, 3 Jul 1997, Andy Powell wrote:
|sometime back - the reason for this is that I'm currently nesting type
|qualifiers inside element tags, i.e. I'm generating
|
| <Creator>
| UKOLN Information Services Group
| <Email>
| [log in to unmask]
| </Email>
| </Creator>
|
|rather than
|
| <Creator>
| UKOLN Information Services Group
| </Creator>
| <Creator type="Email">
| [log in to unmask]
| </Creator>
|
|I think this reflects the view that TYPEs are 'an hierarchical subdivision
|of the element name itself' (from Stu's DC4 workshop report) but I guess
|that others may disagree!
I disagree, but from a pragmatic SGML point of view. The first example
above requires you to use something known to SGML bores as a "mixed
content model", which I won't bother you with right now, except to say
that it is generally A Bad Idea. I agree however that having two
<creator> elements, one with an explicit value for its TYPE attribute
and the other not, is simply confusing, if they are both supposed to
contain information about the same thing.
My recommendation would be something like the following:
| <Creator>
| <orgTitle>
UKOLN Information Services Group
| </orgTitle>
<Email>
| [log in to unmask]
| </Email>
| </Creator>
|
Lou
|