I've put a complete copy of a P5-for-xenoData/ *with a built set of Guidelines and Exemplars* at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/. So see, e.g. http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline... (And someone let me know what the heck is the problem with the formatting -- it looks awful.) And use the schema at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Exemplars... to test it out.
Hi Syd, There's something weird about your build: http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline... Huge padding in the table cells, on my browser. The examples look good to me, but the prose section: http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline... doesn't actually mention the <xenoData> element. Is there a missing paragraph? Cbeers, Martin On 2015-06-30 04:01 AM, Syd Bauman wrote:
I've put a complete copy of a P5-for-xenoData/ *with a built set of Guidelines and Exemplars* at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/.
So see, e.g. http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline... (And someone let me know what the heck is the problem with the formatting -- it looks awful.)
And use the schema at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Exemplars... to test it out.
On 29/06/15 21:32, Martin Holmes wrote:
Hi Syd,
There's something weird about your build:
http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline...
Huge padding in the table cells, on my browser.
As I just said, this is because the MODS example is too big
The examples look good to me, but the prose section:
http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline...
doesn't actually mention the <xenoData> element. Is there a missing paragraph?
I agree. These paragraphs also need some careful additions explaining why you might prefer to use <xenoData> rather than embed stuff from the mods namespace randomly within your TEI document. And we should probably give at least a sentence or two to explain what these other metadata standards are, no?
MH> Huge padding in the table cells, on my browser. Yeah, that's usually from a too-long-line in an example, but I don't have any. LB> The reason the xenodata element doesn't format properly is that LB> you've shovelled an obscenely long line (the one containing the LB> mods:abstract) into the exemplum. Ack! Of course, you're absolutely right. I completely missed that when I scanned for long lines. Boy, that's embarrassing. Thanks, Lou. MH> the prose section: [#HD9] doesn't actually mention the <xenoData> MH> element. Egads. Why isn't the <specDesc> showing up? Will investigate. ... Ah. That's why. It's not there. Don't know what happened, but it's in now. I also added a bit more prose. LB> I know you didn't ask anyone to do this, but I just thought I'd do it LB> anyway: I checked out your branch and tried to build it locally. Nay! You were off in Google-won't-let-me-hangout land when I said it, but this was exactly what I asked for. Thank you. LB> Worked, as they say, up to a point: but it fell over checking LB> validity of the revised P5 it had just built (my guess is that LB> p5.nvdl needs to know about the namespaces you're using) Interesting ... but (as they say) it works for me. My first thought was that, since I have my own executable `onvdl` command, we were using different versions. But in fact, when on a GNU/Linux system (as opposed to Mac OS X), my `onvdl` command just runs the same .jar file that `./run-onvdl` would run if there were no local command. (I.e., ./oNVDL/bin/onvdl.jar.) So that's not it. I don't really understand this. If no one pops up with a theory of the problem, I will try to investigate more thoroughly later in the week. And yes, the example is long, but is it really *too* long? Perhaps. My initial thought was "well, we're not printing these anymore", so at just over 1 screen-full, it wasn't much of a problem. But if I unwrap that long line it will be more like 2-3 full screens worth, which is a real problem. So yeah, I guess you're right. Sigh. Will try to scare up a shorter true MODS example. Thank you, Martin & Lou!
OK. For reasons I don't understand -- but are likely due to the fact that I'm on Mac OS X now, not GNU/Liux -- I've now got same error Lou was getting. I've updated p5.nvdl in my local copy of the P5-for-xenoData branch to fix it. Will check-in soon.
LB> Worked, as they say, up to a point: but it fell over checking LB> validity of the revised P5 it had just built (my guess is that LB> p5.nvdl needs to know about the namespaces you're using)
Interesting ... but (as they say) it works for me. My first thought was that, since I have my own executable `onvdl` command, we were using different versions. But in fact, when on a GNU/Linux system (as opposed to Mac OS X), my `onvdl` command just runs the same .jar file that `./run-onvdl` would run if there were no local command. (I.e., ./oNVDL/bin/onvdl.jar.) So that's not it.
I don't really understand this. If no one pops up with a theory of the problem, I will try to investigate more thoroughly later in the week.
I know you didn't ask anyone to do this, but I just thought I'd do it anyway: I checked out your branch and tried to build it locally. Worked, as they say, up to a point: but it fell over checking validity of the revised P5 it had just built (my guess is that p5.nvdl needs to know about the namespaces you're using) The reason the xenodata element doesn't format properly is that you've shovelled an obscenely long line (the one containing the mods:abstract) into the exemplum. This example is really not suitable anyway (much too big) so I'd suggest drastically simplifying or removing it. I removed it in my local copy, and both these problems went away. BUILD: Check validity with nvdl, first examples with feasible validity, and then the valid ones ./run-onvdl p5.nvdl p5.xml /usr/bin/onvdl /home/lou/Public/P5-xeno/p5.xml:21176:13: error: elements from namespace "http://www.loc.gov/mods/v3" are not allowed /home/lou/Public/P5-xeno/p5.xml:21260:24: error: element "scholarly_object" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context /home/lou/Public/P5-xeno/p5.xml:21176:13: error: elements from namespace "http://www.loc.gov/mods/v3" are not allowed /home/lou/Public/P5-xeno/p5.xml:21260:24: error: element "scholarly_object" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context Error: nvdl run found problems make: *** [valid] Error 1 On 29/06/15 19:01, Syd Bauman wrote:
I've put a complete copy of a P5-for-xenoData/ *with a built set of Guidelines and Exemplars* at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/.
So see, e.g. http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guideline... (And someone let me know what the heck is the problem with the formatting -- it looks awful.)
And use the schema at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Exemplars... to test it out.
participants (3)
-
Lou Burnard -
Martin Holmes -
Syd Bauman