[From nobody Sun Jan 13 13:12:48 2008 Envelope-to: lou@herald.ox.ac.uk Delivery-date: Sun, 13 Jan 2008 18:10:30 +0000 Received: from rx0.herald.ox.ac.uk ([163.1.0.244]) by imap211.herald.ox.ac.uk with esmtp (Exim 4.63) (envelope-from <nobody@sourceforge.net>) id 1JE7Hy-0004Cs-7l for lou@herald.ox.ac.uk; Sun, 13 Jan 2008 18:10:30 +0000 Received: from relay5.mail.ox.ac.uk (relay5.mail.ox.ac.uk [163.1.2.163]) by rx0.herald.ox.ac.uk (Postfix) with ESMTP id 2BC0548048 for <lou@herald.ox.ac.uk>; Sun, 13 Jan 2008 18:10:30 +0000 (GMT) Received: from j3.village.virginia.edu ([128.143.20.247]) by relay5.mail.ox.ac.uk with esmtp (Exim 4.68) (envelope-from <nobody@sourceforge.net>) id 1JE7Hx-00082y-IB for lou.burnard@oucs.ox.ac.uk; Sun, 13 Jan 2008 18:10:30 +0000 Received: from mail.sourceforge.net (lists.sourceforge.net [66.35.250.206]) by j3.village.Virginia.EDU (Postfix) with ESMTP id 9D5C92C6A5 for <editors@tei-c.org>; Sun, 13 Jan 2008 13:10:28 -0500 (EST) Received: from sc8-sf-web22-b.sourceforge.net ([10.3.1.212] helo=sc8-sf-web22.sourceforge.net) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1JE7Ht-0002pq-1x; Sun, 13 Jan 2008 10:10:25 -0800 Received: from nobody by sc8-sf-web22.sourceforge.net with local (Exim 4.43) id 1JE7Hr-00026w-Iq; Sun, 13 Jan 2008 10:10:24 -0800 To: noreply@sourceforge.net From: "SourceForge.net" <noreply@sourceforge.net> Subject: [ tei-Feature Requests-1721365 ] Precision attribute Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-SourceForge-Tracker-unixname: tei X-SourceForge-Tracker-trackerid: 644065 X-SourceForge-Tracker-itemid: 1721365 X-SourceForge-Tracker-itemstatus: Open X-SourceForge-Tracker-itemassignee: jcummings X-SourceForge-Tracker-itemupdate-reason: Settings changed X-SourceForge-Tracker-itemupdate-username: louburnard Message-Id: <E1JE7Hr-00026w-Iq@sc8-sf-web22.sourceforge.net> Sender: Nobody <nobody@sc8-sf-web22.sourceforge.net> Date: Sun, 13 Jan 2008 10:10:23 -0800 X-Oxmail-Spam-Status: score=0.0 tests=none X-Oxmail-Spam-Level: Feature Requests item #1721365, was opened at 2007-05-18 15:02 Message generated for change (Settings changed) made by louburnard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=644065&aid=1721365&group_id=106328 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: new or changed class Group: None Status: Open Priority: 5 Private: No Submitted By: BODARD Gabriel (gabrielbodard) >Assigned to: James Cummings (jcummings) Summary: Precision attribute Initial Comment: I'd like to propose a slight refinement to the way imprecise numerical values (e.g. dates, measurements, extents of gap or space, etc.) are expressed. In general terms, the distinction I would like to see enabled (even recommended) would be that between the expressions: (a) "Date: c. A.D. 250" (b) "Date: A.D. 250?" The former is an expression of imprecision; the editor is fairly confident that the object or event she is dating happened pretty close to the middle of the third century, but isn't going to commit to that precise year. The latter is an expression of uncertainty; the editor may have evidence that the event occured in precisely that year, but is not entirely happy with her interpretation of the evidence. They are not the same thing. (In the sciences there is often this same distinction between precision and accuracy, for example.) Now I see that in <date> there is already a precision attribute for this purpose, but I would like to see this extended to elements such as <gap> and <space> (where it would refer to the precision of @extent), and <measure> (where it would modify @value). This has been the practice of the EpiDoc Guidelines for a while now, since we believe the certainty mechanism is inadequate (and in any case inaccurate) for this purpose. For example: "H. c. 0.50" could be represented: <measure type="length" dim="height" precision="low" value="0.50"> "[ . . c. 12 . . ]" would be: <gap reason="lost" extent="12" precision="low"/> This would involve simply the addition of an attribute to the model of these elements and so would be fully backward-compatible with earlier versions of P5. (I'm also going to float this for discussion on the list, because I think it's an important concept worth getting people's opinions on.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=644065&aid=1721365&group_id=106328 ]