Menu
▾
▴
#388 add @unit to <biblScope>, and soft-deprecate @type
closed-fixed
1(low)
2014-12-24
2012-09-20
No
As discussed by Council in Oxford 2012-09-20 (re ticket http://purl.org/TEI/FR/3555191\) we would like to add an attribute @unit to <biblScope> to contain "pp", "vol", "ll" etc., and discourage the use of @type for this purpose. This will have to be a long-term, slow, soft deprecation.
This was assigned to me in Oxford. It seems I should make this change on @citedRange as well.
In fact, if I implement this before the next release, I should simply *remove* @type from <citedRange> and provide only @unit. That is, no one will have used @type since this element won't have been included in a release yet.
Implemented at revision 11228.
In addition to revision 11220, see also revision 11357.
Additional implementation at revision 11796.
This is a deprecation according to http://www.tei-c.org/Activities/Council/Working/tcw27.xml , so I have added validUntil= at https://sourceforge.net/p/tei/code/12284/ .
Re-opening this bug because the deprecation has now expired and the @type attribute needs to be removed from
<biblScope>. Assigning to myself so we keep track of it.Attribute deleted in rev 13095. Waiting for Jinks to build successfully before closing the ticket. Note to self and Future Council Chair: make sure this one gets into the list of changes for the next release; even though it's an old ticket, it might bite quite a few people,
We need to keep a trace of @type in the documentation of biblScope so that we are not under a flood of enquiries. Maybe just turning the indication of deprecation to one of deletion.
Hi Laurent,
Could you clarify what you're proposing? We deprecated @type on biblScope for two years, so for two years people have been seeing it marked in the Guidelines with a deadline approaching. When you delete something, though, you delete it; I don't think there's a way to warn people about this other than putting it in the change notes and the release announcement. I don't think it would be appropriate to put things in the Guidelines prose about attributes that used to exist.
Cheers,
Martin
My feeling, is that the use of @type on biblScope has impregnated a lot of projects (Perseus!) and is still mentioned in quite a few pages online (just a couple following a quick search below). I have the intuition that we should clearly flag that we are perfectly aware of its disappearance. At least a reminder message on the TEI list would not be superfluous. Maybe the documentation is not the place for saying that something does not exist any more, but I anticipate we will have to answer quite a few questions for the coming years.
http://nl.ijs.si/e-zrc/bs/html/TEI_P4/ref-BIBLSCOP.html
http://www.acmuller.net/yogacara/bibliography/bibnotes.html
http://quod.lib.umich.edu/cgi/t/tei/tei-idx?type=HTML&rgn=DIV4&byte=680842
http://www.wwp.northeastern.edu/outreach/seminars/xslt_2012-03/quizzes/xslt_quiz_5.htm
Good idea to post to TEI-L, and perhaps we should also post to the Facebook group. Any other ideas would be welcome. There's a build problem with the ENRICH schema right now; once that is solved, we can focus on public announcements,
Lou has fixed the ENRICH schema, so the builds are working. Next step: post to TEI-L, Facebook etc. Will do that in the next little while.
I haven't fixed the Enrich schema, cos there's nothing wrong with it. All I have done is change some of the examples in the Enrich schema documentation to use @unit rather than @type. As Laurent points out, we can now expect a small trickle of complaints from other users of <biblScope> who have not noticed that this change is now necessary.
Posted a message to TEI-L.
I've posted to Facebook pointing at the TEI-L posting. I think this, along with the change log entry when we release, should be enough; if anyone else can think of other places to publicize this, the TEI-L posting is here:
https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;e784a172.1412
I'm now closing the ticket again.