Re: Examples of @context attribute

Lou Burnard <[email protected]>
Newsgroups gmane.text.tei.general
Message-ID <[email protected]>
This @context attribute is one of the (very few) features of the TEI ODD 
specification language which has not yet been implemented in the TEI 
stylesheet library. During the last year or so, considerable effort has 
been going into implementing a version of the language which is "pure", 
i.e. without any dependencies on other schema languages, and this 
particular requirement has dropped down the priority list. As you note, 
the capability already exists  of adding schematron constraints into 
your specification to achieve the same goal; indeed, that is probably 
how we'd implement it in the general case as well. I've raised a ticket 
(https://github.com/TEIC/TEI/issues/1536) so that the issue does not 
disappear from the radar, but it's not going to make it into the next 
release, due in a month or so! Please feel free to comment further on 
the ticket: for example, some discussion of your intended usage would be 
very helpful.


On 11/11/16 20:48, Daniel Schwartz wrote:
> Dear List Members,
>
> I am wondering if someone might be able to point me toward examples of the
> use of the @context attribute in an ODD that does not appear in conjunction
> with the use of schematron. The TEI guidelines allow the @context attribute
> with the following elements: alternate, classRef, elementRef, and sequence.
> However, the only examples I could find in the guidelines are with
> schematron.
>
> The description of @context ("supplies an XPath identifying a context
> within which this component of a content model must be found") suggests it
> would be very helpful for the schema I am working on (in a way that
> schematron would be less helpful). I am not, however, having much luck
> getting it to work as I would like. I think some examples might be helpful.
>
> Thank you very much,
> Dan
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.