I was thinking about storing the content header information as a generic list of elements containing id-value attribute pairs. This would mean that this could be altered/added to later on without having to change the schema, since there would be nothing specific hard coded into the schema.
Ok so I lied...
I was thinking about storing the content header information as a generic list of elements containing id-value attribute pairs. This would mean that this could be altered/added to later on without having to change the schema, since there would be nothing specific hard coded into the schema.
Maybe something like this:
content file:
<headerItems>
<headerItem id="eventtype" value="Samyama"
<headerItem id="eventdate" value="2007-03-24"
<headerItem id="transcribedby" value="Grant"
<headerItem id="proofedby" value="Chitra"
</headerItems>
<blocks>
<block> ... </block>
</blocks>
ref file:
<headerItemRefs>
<headerItemRef id="eventtype" name="Event Type">
<headerItemRef id="eventdate" name="Event Date">
<headerItemRef id="transcribedby" name="Transcribed By">
<headerItemRef id="transcribedby" name="Proofed By">
</headerItemRefs>
What do you think? Overkill?