[tei-council] Notes from today;s conference call

[Christian Wittern]

Syd Bauman <Syd_Bauman at Brown.edu> writes:

> [1 message body text <text/plain; us-ascii (7bit)>]
> Note: in the following I am using "or" to mean "inclusive or" and "or
> ... but not both" to mean "exclusive or", which is how I was taught
> English in grade school.
>
>> Under item 3, I think we not only discussed co-occurrence
>> constraints, but also the possibility to instantiate certain
>> attributes either as child elements or as attributes in a given
>> schema (that was on the original list of features we wanted for
>> P5). I would like to see this mentioned in the notes, so that we
>> can reference it, if the need arises.
>
> I'm not 100% sure, but I think they're the same thing. The ability to
> express in a schema that something (say the "engineType" of
> "automobile") is permitted as either an attribute or a child element
> is, of course, trivial. The difficult part, that DTDs cannot do, is
> to express that it is permitted as an attribute or a child element,
> but not both. RelaxNG permits this with a construct that I believe is
> called a "co-occurence constraint", but I'm not entirely sure that
> this phrase isn't reserved for a specific case[1]. 

Sorry, I guess I was dense. Yes you are right, they are the same.  As
for the DTD, I think we thought this was a problem that should be
solved at compile time -- you get the DTD either with the attributes,
or with the child elements from Roma, but not both.

All the best,

Christian

-- 

 Christian Wittern 
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN