Sebastian Rahtz a écrit :
> Martin Holmes wrote:
>> Thanks to both of you for this. I'm inclined to go with the RelaxNG
>> implementation for simplicity's sake when editing, because presumably
>> oXygen can then help with auto-completion and so on. That means the
>> customization can't be documented through ODD, though. This must
>> surely be a fairly common type of customization, though. Is there any
>> chance Roma and ODD might support it?
I think it depends on what you mean by doing it in odd.
If I got the point correctly, it would look like :
<elementSpec ident="seg" mode="change" module="linking">
<desc>seg is used to whatever you want to
say here....</desc>
<content>
<choice
xmlns="http://relaxng.org/ns/structure/1.0">
<group>
<attribute name="type">
<value>Type_01</value>
</attribute>
<attribute name="subtype">
<choice>
<value>a</value>
<value>b</value>
<value>c</value>
</choice>
</attribute>
</group>
<group>
<attribute name="type">
<value>Type_02</value>
</attribute>
<attribute name="subtype">
<choice>
<value>x</value>
<value>y</value>
</choice>
</attribute>
</group>
</choice>
<text
xmlns="http://relaxng.org/ns/structure/1.0"/>
</content>
</elementSpec>
(sorry for the verbose relaxNG XML syntax).
I appreciate how hard it would
>> likely be to do this for Roma, but it would be nice if ODD could
>> handle it, for the sake of documentation, even if Roma can't then
>> generate a schema from it.
> the correct way to handle this would be if you or someone else proposed
> a syntax
> in ODD, and I could then implement a trial version of it in a non-TEI
> namespace.
>
> I confess, I don't off-hand see how to do it.
>
--
Bertrand Gaiffe
Chargé de recherche CNRS à l'ATILF (UMR 7118)
[log in to unmask]
tel : 03 83 96 86 98
|