Dear Council-- The weird validation problem is solved: I needed to purge my system of DS_Store files (and this time I set up a proper "cron job" to keep removing them every day). My project's schema needs to check files within a collection, and the presence of a pesky DS_Store file was interfering (sigh). I feel pretty silly, but since errors generated by such things tend to be pretty dramatic, maybe it's worth filing away in future. Elisa On Sat, May 6, 2017 at 2:00 AM, Elisa Beshero-Bondar wrote:

Dear Council-- I'm seeing a weird schema validation problem since our Stylesheets meeting on Thursday, just on my Mac OS X installation of oXygen version 19 (current one). It's weird because I can't duplicate the problem on my (also current) Linux installation of oXygen. I see it on my Mac only when I try to validate the TEI files in one project, with an ODD-generated schema. On the Mac, validation is interrupted with an error that seems to indicate a problem with the .rng file: Here is the error message:

Engine name: ISO Schematron Severity: fatal Description: Required item type of result of call to collection is node(); supplied value has item type xs:base64Binary Start location: 2620:10

Clicking on the error message opens my RNG schema file to line 2620, which is simply: <define name="model.choicePart"> <choice> <ref name="sic"/> <ref name="corr"/> <ref name="reg"/> <ref name="orig"/> <ref name="unclear"/> <ref name="abbr"/> <ref name="expan"/> <ref name="supplied"/> <ref name="seg"/> </choice> </define> This is a standard TEI schema rule, and I see no reason why it would be failing.

On my Linux computer, I've checked to see that it is running the same version of oXygen as my Mac, and validation of the same files is performing with no problems there. So something is wrong on my Mac, but I can't figure out what.

The only possibly event I can think of is that I installed Apache Ant on my Mac using homebrew in my terminal two days ago during our Stylesheets session, so that I could get the Stylesheets to properly run in their sequence from our bin directory. But I don't know why that would interfere with oXygen!

Has anyone seen something similar or can advise? I've also written to oXygen support.

Thanks--and sorry to bug our group with this, but I wonder if it's an ODD-related thing that we're likely to see more here than elsewhere...

Elisa

-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu Development site: http://newtfire.org

-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu Development site: http://newtfire.org