LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  February 2008

TEI-L February 2008

Subject:

Re: Whatever happened to @precision?

From:

John Tone Young <[log in to unmask]>

Reply-To:

John Tone Young <[log in to unmask]>

Date:

Fri, 1 Feb 2008 08:58:20 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (37 lines)

For what it's worth, so would I.  I think this answers my intial 
question, which is what sent the thread off on this tack.

John

Quoting Tim Finney <[log in to unmask]>:

> I would vote for that too.
> 
> Tim Finney
> 
> On Thu, 2008-01-31 at 08:31 -0800, Martin Holmes wrote:
> > Conal Tuohy wrote:
> > > <date>
> > >         <date when="1640" cert="low"/>
> > >         <date notBefore="1620" cert="medium"/>
> > >         <date notAfter="1660" cert="high"/>
> > > </date>
> > 
> > This seems an elegant and flexible approach to me. It allows
> refinements 
> > like this, too:
> > 
> > <date>
> >          <date when="1640" cert="low"/>
> >          <date notBefore="1620" notAfter="1660" cert="medium"/>
> > </date>
> > 
> > where the certainty value applies to the whole date range. I would
> vote 
> > for this being incorporated into the guidelines as good practice.
> > 
> > Cheers,
> > Martin
> > 
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager