[tei-council] Strange validation problem with ODD file

[Martin Holmes]

The only difference between the schemas is that the Oxygen one allows 
<idno> in model.personPart, because it was generated a day later. So 
that's not the source of the problem. I think it must indicate, as Lou 
suggests, that Oxygen now defaults to validating a TEI file which is not 
explicitly linked to a schema using something other than tei_all; but I 
don't know what it does use. I'm pretty sure it used to use tei_all.

Of course I should be validating my ODD files using tei_allPlus anyway, 
otherwise I get errors for all the RNG elements.

Do we care that the oxygen-tei package has a very slightly different 
schema from the official 2.1.0 release (allowing <idno> in 
model.personPart)?

Cheers,
Martin


On 12-06-25 10:22 AM, Sebastian Rahtz wrote:
> It's not clear whether oxygen themselves use that framework, or build their own.
>
> Can you compare the tei_all schemas?
>
> Carved in stone on my iPad
>
> On 25 Jun 2012, at 18:19, "Martin Holmes" <mholmes at uvic.ca> wrote:
>
>> On 12-06-25 10:13 AM, Lou Burnard wrote:
>>> On 25/06/12 17:56, Martin Holmes wrote:
>>>
>>>> I'm working on a fairly simple ODD file and getting a validation error
>>>> that I can't figure out. I'm working in Oxygen and letting Oxygen
>>>> validate against the latest TEI framework release, installed from
>>>> oxygen-tei, and getting a series of errors.
>>>
>>>
>>> Forgive me for stating the obvious, especially as I dont know exactly
>>> what you mean by "the latest TEI framework release",
>>
>> What I mean is that I downloaded the latest oxygen-tei package from here:
>>
>> <http://code.google.com/p/oxygen-tei/>
>>
>> and installed it into my Oxygen setup. When you edit a TEI file which
>> isn't directly linked to a specific schema through e.g. an xml-model PI,
>> Oxygen by default validates it against tei_all in the installed
>> framework (at least, I'm pretty sure that's the case, based on my
>> previous experience). So what I'm wondering is whether there might be
>> something wrong with the oxygen-tei package.
>>
>>> but the
>>> implication of the errors you're seeing is surely that the schema in use
>>> doesn't include <editionStmt>. Which is quite possible if you're using
>>> (say) tei_bare or some other customization which omits it.
>>
>> If it's the case that Oxygen in fact validates against some other
>> customization rather than tei_all, then that makes sense, but my
>> previous experience suggests that up to now it's been validating against
>> a complete TEI schema.
>>
>>> Anyway, I havent noticed anything untoward with my installation of
>>> Oxygen since the release...
>>
>> Did you install the new TEI framework into your Oxygen frameworks directory?
>>
>> Cheers,
>> Martin
>>
>> --
>> Martin Holmes
>> University of Victoria Humanities Computing and Media Centre
>> (mholmes at uvic.ca)
>>
>>
>> --
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
> .
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)