Discussion of all Text Encoding Initiative (TEI) related matters

Michelle Dalmau | 4 Aug 2012 16:50

Re: ODD/ROMA/Oxygen: List Values

Hello,

I also found that xml:id does not prompt for pre-defined values in Oxygen.  I originally I thought it was
related to the xml:id data type problem, but I know that has since been resolved and I have recently
generated updates to my W3C schema.  I am not sure if this is a problem, like the valList, with the W3C
translation from the ODD or if it's an Oxygen thing.  

It, of course, works with RelaxNG, but after inquiring with our technical team, our e-text repository and
encoding workflows are tightly integrated with W3C.  I could change the local encoding practices and
switch at time of upload, but that's a significant task.

In any case, if the TEI Council thinks this is an issue worth exploring, and if indeed the valList and xml:id
prompting is a problem with ODD to W3C translation, I just wanted to document these two issues as part of
this thread.

Thanks,
Michelle

> 
> On 26 Jul 2012, at 20:50, Michelle Dalmau <michelle.dalmau <at> GMAIL.COM> wrote:
> 
>> Unfortunately I am bound to W3C schema as a result of some policy decision made years ago.  I'll need to
explore this further with our technical team,
>> but I wondered if the W3C output was part of the problem.
>> 
>> Still, if someone knows how to get the valList prompted as "semi-whatever" in Oxygen with W3C schema,
tell Sebastian!  
>> 
>> Thanks,
>> Michelle

(Continue reading)

headers

Sebastian Rahtz | 4 Aug 2012 16:56

Re: ODD/ROMA/Oxygen: List Values

On 4 Aug 2012, at 15:50, Michelle Dalmau <mdalmau <at> INDIANA.EDU>
 wrote:

> 
> I also found that xml:id does not prompt for pre-defined values in Oxygen.

do you mean that? it would be unusual to specify a list of values for  <at> xml:id.

> It, of course, works with RelaxNG, but after inquiring with our technical team, our e-text repository and
encoding workflows are tightly integrated with W3C.  I could change the local encoding practices and
switch at time of upload, but that's a significant task.

why does your e-text repository need to know how you validate your file in oXygen? set it up so that your
prefererred schema is the
default for <TEI> documents, and then proceed. Or is your repository insisting that the file have a
hard-wired link to a schema?
> 
> In any case, if the TEI Council thinks this is an issue worth exploring, and if indeed the valList and xml:id
prompting is a problem with ODD to W3C translation, I just wanted to document these two issues as part of
this thread.

I am not sure what the Council can do about it? 
--
Sebastian Rahtz      
Head of Information and Support Group
Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

headers

Michelle Dalmau | 4 Aug 2012 17:05

Re: ODD/ROMA/Oxygen: List Values

On Aug 4, 2012, at 10:56 AM, Sebastian Rahtz wrote:

> On 4 Aug 2012, at 15:50, Michelle Dalmau <mdalmau <at> INDIANA.EDU>
> wrote:
> 
>> 
>> I also found that xml:id does not prompt for pre-defined values in Oxygen.
> 
> do you mean that? it would be unusual to specify a list of values for  <at> xml:id.
> 

I don't know what you mean ... if you are tracking speakers in participant description in the header is one
example ... taxonomy is another example ... 

>> It, of course, works with RelaxNG, but after inquiring with our technical team, our e-text repository
and encoding workflows are tightly integrated with W3C.  I could change the local encoding practices and
switch at time of upload, but that's a significant task.
> 
> why does your e-text repository need to know how you validate your file in oXygen? set it up so that your
prefererred schema is the
> default for <TEI> documents, and then proceed. Or is your repository insisting that the file have a
hard-wired link to a schema?

I don't know the technical ins and outs so I can't explain it in any more detail.  we typically don't hard wire
software, but this is an older, home grown e-text repository/encoding versioning system so it could be an
artifact of time and lack of foresight.  

>> 
>> In any case, if the TEI Council thinks this is an issue worth exploring, and if indeed the valList and
xml:id prompting is a problem with ODD to W3C translation, I just wanted to document these two issues as

(Continue reading)

headers

Sebastian Rahtz | 4 Aug 2012 17:56

Re: ODD/ROMA/Oxygen: List Values

On 4 Aug 2012, at 16:05, Michelle Dalmau <michelle.dalmau <at> gmail.com>
 wrote:

>>> I also found that xml:id does not prompt for pre-defined values in Oxygen.
>> 
>> do you mean that? it would be unusual to specify a list of values for  <at> xml:id.
>> 
> 
> I don't know what you mean ... if you are tracking speakers in participant description in the header is one
example ... taxonomy is another example ... 
> 
I am guessing you mean that when you have an attribute which may point to other parts of the document which
have IDs, you
expect to be offered a choice  of IDs.

> 
> If it's not related to the ODD to W3C translation, then I guess, nothing, but if it is, and it's not a
limitation of the W3C schema (it may be for all I know), and you provide a crosswalk to W3C, then why wouldn't
the Council care?  If that's the case, why not abandon W3C altogether as part of the schema generation options.

if anyone can show the W3C schema is incorrect in some way, then of course we have to fix it.  Otherwise, isn't this
a question for you to take up with oXygen support?
--
Sebastian Rahtz      
Head of Information and Support Group
Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431