[tei-council] Another issue with @pattern
O'Donnell, Dan
daniel.odonnell at uleth.ca
Mon Jun 8 19:17:41 EDT 2009
I agree, Peter, that we should be thinking of this as part of the pointers rather than a mechanism for this one element. And you, Lou, and Gabby are beginning to convince me that maybe we should come up with a reduced solution to the problem with certainty while we digest the larger proposal. Maybe adding sthing like @path is a P5.5 thing.
If Gabby's suggestions answer the brokenness Lou discovered perhaps we should pursue those. In doing it though we should keep an eye on the possibility that we'll be adding a much more powerful approach in the medium term and so try to makes sure we build something now that looks robust enough to survive subsequent developments.
-----------
Daniel O'Donnell
University of Lethbridge
(From my mobile telephone)
--- original message ---
From: "Peter Boot" <pboot at xs4all.nl>
Subject: Re: [tei-council] Another issue with @pattern
Date: June 8, 2009
Time: 12:13:55
Lou Burnard schreef:
> Let's not lose sight of the problem we're trying to solve here.
>
> If the can of worms that @path opens proves to be a pandora's box, then
> I propose to withdraw it hastily, and replace it with one or other of
> the following less attractive hacks:
>
> b) replace @pattern by an ad hoc @attribute attribute
FWIW, I would go for this.
It's not that I don't like the pattern proposal, but my impression is
that it needs more time.
One of my questions would be: we would be introducing the pattern
facility on what are after all rather specialized if not obscure
elements, but we have tons of elements and attributes that do pointing
(ptr, @ana, note/@target, ...), and that might profit from the same
feature. Are we willing to extend it to these other cases?
Peter
_______________________________________________
tei-council mailing list
tei-council at lists.village.Virginia.EDU
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
More information about the tei-council
mailing list