Yes. I think so. Except I don't know if the processing is there for the <moduleRef key="foo" source="someOtherFineOdd.odd"/> ... I've not tested. I've only tested the others. -James On 20/10/16 21:48, Lou Burnard wrote:

OK, I get it. The @source parameter states what's available for selection, but you always have to make a selection.

so <schemaSpec source="myfineodd.odd"/>

doesn't select anything. You have to say

<schemaSpec source="myfineodd.odd"> <elementRef key="foo"/> </schemaSpec>

to get a foo, which must be available from myfineodd.odd

And by extension, I can also say

<schemaSpec source="myfineodd.odd"> <moduleRef key="foo"/> </schemaSpec>

to get hold of module foo which is referenced in myfineodd.odd

But I can also say

<schemaSpec source="myfineodd.odd"> <moduleRef key="foo" source="someOtherFineOdd.odd"/> </schemaSpec>

to pick up declarations from a module defined in someOtherFineODD

Right?

On 20/10/16 20:41, James Cummings wrote:

...

Yes. And like with a normal odd in a chained odd you have to moduleRef all the modules from the source that are going to be used in your subset. You don't get everything in the source by default, the first ODD just limits what is in the source that you have available to choose from in your second ODD.

James

-- Dr James Cummings, Academic IT Services, University of Oxford

On 20 Oct 2016 19:07, Hugh Cayless wrote: Well, I think if you had a moduleRef, then you could delete it with an elementSpec, you just can't use the elementSpec without the moduleRef. I think tests and better documentation of this would be a grand idea.

Sent from my phone.

...

On Oct 20, 2016, at 13:43, Lou Burnard wrote:

...

On 20/10/16 18:23, Hugh Cayless wrote: 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? Yes. Which is why I am puzzled that one works and the other doesn't.

I suggest it might help to create a little test suite... -- 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 -- 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

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Jolly good. Will upload my test file when I get a chance. Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] purifying odd doc From: Hugh Cayless To: TEI Council CC: Well, it seems to work for me :-) On Fri, Oct 21, 2016 at 9:43 AM, James Cummings wrote:

Yes. I think so. Except I don't know if the processing is there for the <moduleRef key="foo" source="someOtherFineOdd.odd"/> ... I've not tested. I've only tested the others.

-James

On 20/10/16 21:48, Lou Burnard wrote:

...

OK, I get it. The @source parameter states what's available for selection, but you always have to make a selection.

so <schemaSpec source="myfineodd.odd"/>

doesn't select anything. You have to say

<schemaSpec source="myfineodd.odd"> <elementRef key="foo"/> </schemaSpec>

to get a foo, which must be available from myfineodd.odd

And by extension, I can also say

<schemaSpec source="myfineodd.odd"> <moduleRef key="foo"/> </schemaSpec>

to get hold of module foo which is referenced in myfineodd.odd

But I can also say

<schemaSpec source="myfineodd.odd"> <moduleRef key="foo" source="someOtherFineOdd.odd"/> </schemaSpec>

to pick up declarations from a module defined in someOtherFineODD

Right?

On 20/10/16 20:41, James Cummings wrote:

Yes. And like with a normal odd in a chained odd you have to moduleRef

...

all the modules from the source that are going to be used in your subset. You don't get everything in the source by default, the first ODD just limits what is in the source that you have available to choose from in your second ODD.

James

-- Dr James Cummings, Academic IT Services, University of Oxford

On 20 Oct 2016 19:07, Hugh Cayless wrote: Well, I think if you had a moduleRef, then you could delete it with an elementSpec, you just can't use the elementSpec without the moduleRef. I think tests and better documentation of this would be a grand idea.

Sent from my phone.

On Oct 20, 2016, at 13:43, Lou Burnard

...

wrote:

On 20/10/16 18:23, Hugh Cayless wrote:

...

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?

Yes. Which is why I am puzzled that one works and the other doesn't.

I suggest it might help to create a little test suite... -- 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

-- 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

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

-- 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

-- 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