The way I was thinking about it: every ODD has to declare the modules it's
using.
Aren't moduleRef/@exclude and elementSpec/@mode='delete' basically
equivalent anyway?
On Thu, Oct 20, 2016 at 1:19 PM, Lou Burnard
On 20/10/16 18:11, James Cummings wrote:
On 20/10/16 17:57, Lou Burnard wrote:
On 20/10/16 15:42, Hugh Cayless wrote:
Lou, is that your whole ODD? If so, I think the problem may be that you still need to put moduleRefs in the derived ODD. You don't seem to get them for free from the source.
Yes, that's my whole ODD. So even in an expanded ODD, each elementSpec has lost information about which module it came from? That seems weird. Are you saying that in order to delete an element (say list) from a chained odd I have to specify it like this:
<schemaSpec ident="ODDauthoring" source="tei_bare.subset.xml" > <moduleRef key="core" except="list" source="p5subset.xml"/> </schemaSpec>
Why doesn't that get me all the other core elements again?
You shouldn't have to have a @source on the moduleRef. The second ODD works, or should work IMHO, precisely the way a normal ODD does with respect to p5subset. If you are pointing at tei_bare.subset.xml then if you do
<moduleRef key="core" except="list"/>
You should get p, item, label, head, author, and title (since those are in bare).
OK, but I hope you can see why I am puzzled. If I want to suppress an element from a non-chained ODD (or one chained from p5subset) I can do it by saying "elementSpec mode="delete". If I'm working further down the chain, I can't : I have to use a moduleRef.
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived