Oxygen then starts yelling: element "physDesc" not allowed yet; missing required element "msIdentifier"
This encoding is, I believe, in accordance with the guidelines (see http://lombardpress.org/schema/docs/critical/#sourcedesc). So what do I do?
Actually it hit me whether we should change the schema to let the list of witnesses simply be able to hold a list of manuscript descriptions and discard the <witness> element. So something like this could be a list of witnesses:
Here it would be so easy to add descriptions of the manuscripts.
On the other hand: This goes against the idea of splitting up concerns. This would require a manuscript description in each item file. That may be a very bad idea actually.
But if we want to keep it out of the item files, maybe we should walk the line and also remove the hand descriptions to some external source.
In a top-level repository of text items there could simply be a "witnesses.xml" with ids matching the ids of the <witness> elements in each item. During processing that would be the authority for information about the witnesses, hands etc.
Maybe I actually prefer that solution, or something similar.
Today I wanted to register some different hands in a witness:
Oxygen then starts yelling: element "physDesc" not allowed yet; missing required element "msIdentifier" This encoding is, I believe, in accordance with the guidelines (see http://lombardpress.org/schema/docs/critical/#sourcedesc). So what do I do?
Actually it hit me whether we should change the schema to let the list of witnesses simply be able to hold a list of manuscript descriptions and discard the
<witness>
element. So something like this could be a list of witnesses:This would of course add an extra level in simple lists like this:
Which would have to look like this:
Here it would be so easy to add descriptions of the manuscripts.
On the other hand: This goes against the idea of splitting up concerns. This would require a manuscript description in each item file. That may be a very bad idea actually. But if we want to keep it out of the item files, maybe we should walk the line and also remove the hand descriptions to some external source.
In a top-level repository of text items there could simply be a "witnesses.xml" with ids matching the ids of the
<witness>
elements in each item. During processing that would be the authority for information about the witnesses, hands etc.Maybe I actually prefer that solution, or something similar.