John P. McCaskey | 1 Jul 18:39 2012

Re: TEI P5 version 2.1.0 is online!

In April, Sebastian posted two items useful for stylesheet writers. One was a pre-populated, ready-to-go <xsl:strip-space> element (posted April 10). The other was a text file indicating the datatype for all attribute-element pairs (posted April 28).

Could these be a standard part of a release? Or are they already and I didn't see them?

Thanks,
JPM


On 6/18/2012 1:56 PM, James Cummings wrote:
Dear TEI Community,

TEI P5 version 2.1.0 (Codename: Earhart's Crossing) is now available from all the usual sources, such as the TEI-C website and Sourceforge. This is a maintenance release that introduces both textual and schema-related changes, mostly based on bug and feature request tickets submitted to Sourceforge by the TEI community (with two notable submitters mentioned in the release notes below). If you notice anything that has changed in error, or want to submit additional changes, please do so on the http://tei.sourceforge.net website.

--
John P McCaskey PhD · www.johnmccaskey.com · mailbox <at> johnmccaskey.com
Stanford University · History and Philosophy of Science
Brown University · Political Theory Project
Espen S. Ore | 2 Jul 11:41 2012

<elementSpec> is it unavailable?

Greetings,

We are working on the documentation of the Ibsen edition project. And it 
seems that <elementSpec> is not allowed anywhere. We are using a 
Roma-generated schema with some chanegs etc. but when I load our 
ODD-file into Roma, I cannot find <elementSpec> anywhere. Where should 
it be? How can I get it activated? our scehma was Roma-generated 
2012-03-26 - has there been any changes since then that we should try to 
incorporate (and how, except for loading our ODD-file into Roma and then 
regenerating a schema) in order to get <elementSpec> included, or is it 
not intended for any other use than ODD-files?

Espen Ore
University of Oslo

Sebastian Rahtz | 2 Jul 11:46 2012
Picon
Picon

Re: <elementSpec> is it unavailable?

elementSpec is highly specialised, and only allowed in specific places, inside schemaSpec and specGrp.
Where do you want to use it?

Sent from my iPad

On 2 Jul 2012, at 10:41, "Espen S. Ore" <espen <at> ESPENORE.TK> wrote:

> Greetings,
> 
> We are working on the documentation of the Ibsen edition project. And it seems that <elementSpec> is not
allowed anywhere. We are using a Roma-generated schema with some chanegs etc. but when I load our ODD-file
into Roma, I cannot find <elementSpec> anywhere. Where should it be? How can I get it activated? our scehma
was Roma-generated 2012-03-26 - has there been any changes since then that we should try to incorporate
(and how, except for loading our ODD-file into Roma and then regenerating a schema) in order to get
<elementSpec> included, or is it not intended for any other use than ODD-files?
> 
> Espen Ore
> University of Oslo

Espen S. Ore | 2 Jul 11:50 2012

Re: <elementSpec> is it unavailable?

Inside a <div> in the running text ...

I must have misunderstood something when I tried to read the P5 
Guidelines - it looked as if it should be acceptable in any <div>.

Espen

On 02.07.2012 11:46, Sebastian Rahtz wrote:
> elementSpec is highly specialised, and only allowed in specific places, inside schemaSpec and specGrp.
Where do you want to use it?
>
> Sent from my iPad
>
> On 2 Jul 2012, at 10:41, "Espen S. Ore"<espen <at> ESPENORE.TK>  wrote:
>
>> Greetings,
>>
>> We are working on the documentation of the Ibsen edition project. And it seems that<elementSpec>  is not
allowed anywhere. We are using a Roma-generated schema with some chanegs etc. but when I load our ODD-file
into Roma, I cannot find<elementSpec>  anywhere. Where should it be? How can I get it activated? our scehma
was Roma-generated 2012-03-26 - has there been any changes since then that we should try to incorporate
(and how, except for loading our ODD-file into Roma and then regenerating a schema) in order to
get<elementSpec>  included, or is it not intended for any other use than ODD-files?
>>
>> Espen Ore
>> University of Oslo
>

Torsten Schassan | 2 Jul 12:50 2012
Picon

Re: <elementSpec> is it unavailable?

Hi Espen,

>>> We are working on the documentation of the Ibsen edition project. And
>>> it seems that<elementSpec>  is not allowed anywhere. We are using a
>>> Roma-generated schema with some chanegs etc. but when I load our

you would need to add the tagdocs module in your ODD.

Besides what Sebastian said: <elementSpec> is a highly technical 
element, used inside the ODD for Schema generation (and documentation). 
If you want describe the usage in some prose, the elements <gi>, <att>, 
and <value> are your friends. These are available as well only when 
tagdocs has been selected.

Best, Torsten

--

-- 
Torsten Schassan
Digitale Editionen
Abteilung Handschriften und Sondersammlungen
Herzog August Bibliothek, Postfach 1364, D-38299 Wolfenbuettel
Tel.: +49-5331-808-130 (Fax -165), schassan {at} hab.de

*neu: Handschriftendatenbank* http://diglib.hab.de/?db=mss
http://www.hab.de/forschung/projekte/europeana-regia.htm

Espen S. Ore | 2 Jul 15:29 2012
Picon
Picon

Re: <elementSpec> is it unavailable?

Yes,

Thank you to all of you!

But I think that for people coming unaware into this who want to use 
some specific examples - such as some people wanted her in the Ibsen 
project - it is not obvious that <lemendSpec> is *not* the natural thing 
to use when you are showing an element specification.

Thanks once again!

Espen

On 02.07.2012 12:50, Torsten Schassan wrote:
> Hi Espen,
>
>>>> We are working on the documentation of the Ibsen edition project. And
>>>> it seems that<elementSpec> is not allowed anywhere. We are using a
>>>> Roma-generated schema with some chanegs etc. but when I load our
>
> you would need to add the tagdocs module in your ODD.
>
>
> Besides what Sebastian said: <elementSpec> is a highly technical
> element, used inside the ODD for Schema generation (and documentation).
> If you want describe the usage in some prose, the elements <gi>, <att>,
> and <value> are your friends. These are available as well only when
> tagdocs has been selected.
>
>
> Best, Torsten
>
>

--

-- 
Espen S. Ore
Dept. of Linguistics and Scandinavian Studies
Unit for Digital Documentation
University of Oslo

Lou Burnard | 2 Jul 16:23 2012
Picon
Picon

Re: <elementSpec> is it unavailable?

There's quite a difference between a specification which is actually 
specifying and one which is just being displayed or talked about. 
<elementSpec> is performative -- it is intended to do something, not 
just sit there looking pretty.

On 02/07/12 14:29, Espen S. Ore wrote:
> Yes,
>
> Thank you to all of you!
>
> But I think that for people coming unaware into this who want to use
> some specific examples - such as some people wanted her in the Ibsen
> project - it is not obvious that <lemendSpec> is *not* the natural thing
> to use when you are showing an element specification.
>
> Thanks once again!
>
> Espen
>
> On 02.07.2012 12:50, Torsten Schassan wrote:
>> Hi Espen,
>>
>>>>> We are working on the documentation of the Ibsen edition project. And
>>>>> it seems that<elementSpec> is not allowed anywhere. We are using a
>>>>> Roma-generated schema with some chanegs etc. but when I load our
>>
>> you would need to add the tagdocs module in your ODD.
>>
>>
>> Besides what Sebastian said: <elementSpec> is a highly technical
>> element, used inside the ODD for Schema generation (and documentation).
>> If you want describe the usage in some prose, the elements <gi>, <att>,
>> and <value> are your friends. These are available as well only when
>> tagdocs has been selected.
>>
>>
>> Best, Torsten
>>
>>
>
>

Alexander Zoeller | 2 Jul 21:59 2012
Picon

Using TEI Lite to encode oral histories

Dear TEI community,

I'm with a group of students from the University of Applied Sciences in Potsdam, Germany. We have been
tasked with the compiling of metadata on a - hypothetical - oral history project using TEI Lite.

We have found that since 1996, UC Berkely has been very active in using both TEI and TEI Lite to encode oral
history material (see http://www.lib.berkeley.edu/digicoll/bestpractices/tei_history.html).

Can anyone on this group point us to any recent oral history projects that use TEI Lite, possibly projects
that are still ongoing? If possible, we would like to get in touch with individuals who have hands-on
experience in using TEI Lite to encode oral histories. We would be especially interested to learn if, on
the whole, TEI Lite is considered sufficient for oral history encoding, or if the full set of TEI elements
is required.

Any assistance you can give would be very greatly appreciated!

Best regards,

Alexander Zoeller

McAulay, Elizabeth | 2 Jul 23:21 2012

Re: Using TEI Lite to encode oral histories

Hi all,

UCLA is encoding Oral Histories in TEI. We don't use TEI Lite, but I don't think we use anything too
complicated or unusual. It's been a few years since we created our guidelines! For example, see:
http://oralhistory.library.ucla.edu/viewItem.do?ark=21198/zz0008zj1f&title=Ben%20Dobbs&source=flash,
which has a link to the TEi/P5 file. The work we do here at UCLA is based on the work that UNC-Chapel Hill did
for their oral histories, so you might want to check their work out, too. Here's a sample interview from
UNC-Chapel Hill: http://docsouth.unc.edu/sohp/K-0245/menu.html. Please feel free to contact me
with any questions.

Best,
Lisa

Elizabeth (Lisa) McAulay
Librarian for Digital Collection Development
UCLA Digital Library Program
http://digital.library.ucla.edu/

Email: emcaulay <at> library.ucla.edu



-----Original Message-----
From: TEI (Text Encoding Initiative) public discussion list [mailto:TEI-L <at> LISTSERV.BROWN.EDU] On
Behalf Of Alexander Zoeller
Sent: Monday, July 02, 2012 12:59 PM
To: TEI-L <at> LISTSERV.BROWN.EDU
Subject: Using TEI Lite to encode oral histories

Dear TEI community,

I'm with a group of students from the University of Applied Sciences in Potsdam, Germany. We have been
tasked with the compiling of metadata on a - hypothetical - oral history project using TEI Lite.

We have found that since 1996, UC Berkely has been very active in using both TEI and TEI Lite to encode oral
history material (see http://www.lib.berkeley.edu/digicoll/bestpractices/tei_history.html).


Can anyone on this group point us to any recent oral history projects that use TEI Lite, possibly projects
that are still ongoing? If possible, we would like to get in touch with individuals who have hands-on
experience in using TEI Lite to encode oral histories. We would be especially interested to learn if, on
the whole, TEI Lite is considered sufficient for oral history encoding, or if the full set of TEI elements
is required.

Any assistance you can give would be very greatly appreciated!

Best regards,

Alexander Zoeller
Sebastian Rahtz | 2 Jul 23:30 2012
Picon
Picon

Re: Using TEI Lite to encode oral histories

Since you're talking metadata here, I'd steer clear of TEI Lite. The interest in that is more in its choice
of elements in <text>. Its header excludes <recording>, which you may very well find you need.

--
Sebastian Rahtz      
Head of Information and Support Group
Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431


Gmane