headers
O'Donnell, Dan | 1 Feb 2011 06:16
Picon

Martin Mueller elected new Chair of the TEI

It is with great pleasure that I am able to announce that Martin Mueller has been elected to be the next Chair and CEO of the TEI.

Martin will be taking over during a time of great transition as the TEI changes to a fully democratic board and administrative structure.

Martin will be assuming the chair's role effective immediately in programme activity (e.g. on Council and on the Conference programme commitee). I will continue to lead on business and administrative matters until March 1, at which point Martin will take over all duties as Chair and CEO of the Consortium.

Let me thank Martin for age

Sent from my Android phone using TouchDown (www.nitrodesk.com)
Permalink | Reply | 0 comments |
headers
Torsten Schassan | 1 Feb 2011 16:32
Picon
Favicon

attributes of term

Hi,

I just realised there's a note in the documentation for <term>:

"Because the mutually exclusive target and cRef attributes overlap with 
the function of the ref attribute, they are deprecated and may be 
removed at a subsequent release."

Which one will (most probable) last?  <at> target and  <at> cRef? Or  <at> key and 
 <at> ref? Will the whole att.pointing be removed?

Best, Torsten

PS: Btw, the description of  <at> cRef on <term> gives the description of 
values both in English and in French.

--

-- 
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

http://www.hab.de/forschung/projekte/europeana-regia.htm
http://www.hab.de/forschung/projekte/weiss64.htm
Permalink | Reply | 2 comments |
headers
Raffaele Viglianti | 1 Feb 2011 18:53
Picon
Favicon

TEI with Music Notation customization

TEI with Music Notation customization

The Text Encoding Initiative Special Interest Group in Music is pleased to announce the results of a TEI-funded project to bring music encoding into TEI documents. 

Music, like many other art forms, is often mentioned, discussed and described in writings of various kinds. This applies to both historical and contemporary documents, even though the way of notating music has changed considerably in western history. In most cases, music notation enters the text flow in a way similar to figures, images or graphs. On other occasions, elements of music notation are treated as characters in running text.

The TEI with Music Notation customization introduces a way of signalling the presence of music notation in text, but defers to other representations to describe the music notation itself, which is not covered by TEI guidelines. In fact, several commercial, academic and standard bodies have developed digital representations of music notation and, given the topic's complexity, these representations often focus on different aspects and adopt different methodologies. Therefore, the customization defines a container element to encode the occurrence of music notation and allows linking to the data format preferred by the encoder.  This element is called notatedMusic, which has been proposed to enter the TEI specifications and TEI's namespace in a feature request available here for further discussion.

The customization also allows the use of elements from the Music Encoding Iniative (MEI) format that is modelled on the TEI, aims to be independent from rendering software and provides encoding methods for different research approaches in musicology. MEI provides a vocabulary for the representation of Common Western Music Notation, mensural and neume notation and aims to offer extension mechanisms to include other notation systems and non-standard notational components. Moreover, it accommodates a number of modules to express declarative knowledge about the music being encoded, such as analysis, critical commentary, ambiguity, variants, etc. The MEI format was released in its first stable version in summer 2010.

We would like to invite those of you who are interested in the encoding of texts which contain music notation to access the documentation, the ODD and the schema on the SIG's webspace:

http://www.tei-c.org/SIG/Music/twm/index.html

We consider this output as a beta release and we are very interested in collecting comments, feedback and discussing possible use scenarios. Please join our mailing list if you would like to discuss any aspect of this customization.

With kind regards,
Raffaele Viglianti
-- Raffaele Viglianti PhD Candidate and PGRA Centre for Computing in the Humanities King's College London
Permalink | Reply | 0 comments |
headers
Gabriel Bodard | 2 Feb 2011 12:33
Picon
Favicon

Re: attributes of term

My understanding of that line is that it's the former that are 
deprecated. (In addition, I understand that  <at> key is intended to be 
deprecated as well, eventually;  <at> ref is more useful and powerful, as it 
can take both urls and uris as pointers.)

But I'm prepared to be corrected...

G

On 01/02/2011 15:32, Torsten Schassan wrote:
> Hi,
>
> I just realised there's a note in the documentation for<term>:
>
> "Because the mutually exclusive target and cRef attributes overlap with
> the function of the ref attribute, they are deprecated and may be
> removed at a subsequent release."
>
> Which one will (most probable) last?  <at> target and  <at> cRef? Or  <at> key and
>  <at> ref? Will the whole att.pointing be removed?
>
> Best, Torsten
>
>
> PS: Btw, the description of  <at> cRef on<term>  gives the description of
> values both in English and in French.
>

--

-- 
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)

Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Email: gabriel.bodard <at> kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/
Permalink | Reply | 1 comment |
headers
James Cummings | 2 Feb 2011 14:18
Picon
Picon
Favicon

Re: attributes of term

Hiya,

Just to confirm that <term> had only  <at> target and  <at> cRef originally,
c.f. 
<http://www.tei-c.org/Vault/P5/1.2.0/doc/tei-p5-doc/en/html/ref-term.html> 
(or earlier releases).

In TEI P5 1.3.0 we added att.canonical to <term>
<http://www.tei-c.org/Vault/P5/1.3.0/doc/tei-p5-doc/en/html/ref-term.html>

In TEI P5 1.7.0 we removed the locally defined  <at> target and added 
the att.pointing class to provide  <at> target (and also  <at> evaluate). 
 <at> cRef remains locally defined.
<http://www.tei-c.org/Vault/P5/1.7.0/doc/tei-p5-doc/en/html/ref-term.html>

Isn't it great that the earlier releases are available in such an 
easy manner to peruse to make these comparisons. Maybe it is only 
me that finds looking at the historical development of such 
things fun. :-)

I think the point is, as Gabby suggests, that  <at> target and  <at> cRef 
are to be deprecated because their function overlaps with  <at> ref 
and  <at> key. (i.e. anything you can do with target and  <at> cRef, I 
believe you can do inside  <at> ref and  <at> key). Given our attempts 
generally to avoid breaking backwards compatibility (enshrined in 
the so-called 'Birnbaum Doctrine' at 
<http://www.tei-c.org/Activities/Council/Working/tcw09.xml>) 
unless we really feel strongly about it.

There has been discussion on the TEI Council mailing list and 
SourceForge about whether  <at> key should be deprecated at some date 
in the far future because the ability of data.pointer (the 
datatype for  <at> ref) to take xsd:anyURI means that it can not only 
take URL-like URIs but also URN-like URIs.  I think this matter 
is far from written in stone though.

-James

On 02/02/11 11:33, Gabriel Bodard wrote:
> My understanding of that line is that it's the former that are
> deprecated. (In addition, I understand that  <at> key is intended to be
> deprecated as well, eventually;  <at> ref is more useful and powerful, as it
> can take both urls and uris as pointers.)
>
> But I'm prepared to be corrected...
>
> G
>
> On 01/02/2011 15:32, Torsten Schassan wrote:
>> Hi,
>>
>> I just realised there's a note in the documentation for<term>:
>>
>> "Because the mutually exclusive target and cRef attributes overlap with
>> the function of the ref attribute, they are deprecated and may be
>> removed at a subsequent release."
>>
>> Which one will (most probable) last?  <at> target and  <at> cRef? Or  <at> key and
>>  <at> ref? Will the whole att.pointing be removed?
>>
>> Best, Torsten
>>
>>
>> PS: Btw, the description of  <at> cRef on<term>   gives the description of
>> values both in English and in French.
>>
>

--

-- 
Dr James Cummings, Research Technologies Service
OUCS, University of Oxford
Permalink | Reply | 0 comments |
headers
Hilde B=?ISO-8859-1?Q?=F8e?= | 3 Feb 2011 10:09
Picon

eMunch.no officially online

Dear list,
The first version, a beta version, of the digital archive of Edvard Munch’s
texts is now online at http://www.emunch.no/ 

The archive is primarily in Norwegian, but we have start pages in English,
French and German (links on flags in the top of the page, in the front
page’s main part and in the red menu, so hopefully you’ll manage to find
your way). The general information in French and German is limited, I’m
afraid, but we will provide more in due time. The texts, mostly letters,
written by Munch himself in French and German are directly accessible from
the French and German pages. We provide translations in English and French
of some of Munch’s texts.

The encoding guidelines we have used are available in English, cf. the
English page. There are also a few articles in English on Munch related
themes. Guidelines for transcribing Munch’s texts in French and German are
available in French and German alongside articles discussing Munch’s use of
French and German.

The general guidelines for transcribing Munch’s texts will be translated to
English in due time. Eventually we will also provide a list of terms used to
categorize Munch’s texts in Norwegian – English - French - German, to
facilitate browsing even though the archive is in Norwegian. We hope to be
able in the years to come to supply the archive with even more resources in
English, French and German.

We also plan to provide some information on the technical aspects of the
website. In short, the website is built using Apache Cocoon and the eXist
XML database. It is currently hosted by the Unit for Digital Documentation
at the University of Oslo.

We are happy to answer questions and hope to receive feedback from you.
Thank you!
Kind regards, Hilde Bøe

---
Hilde Bøe
Scholarly and Technical Editor

hilde.boe <at> munch.museum.no | hildeboee <at> gmail.com
http://emunch.no/
http://www.munch.museum.no/
Permalink | Reply | 1 comment |
headers
Dot Porter | 3 Feb 2011 18:34
Picon

Re: multiple msIdentifiers

Gabby, I believe this is what altIdentifier is for.

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-altIdentifier.html

This does mean that you have to pick on identifier as the primary one.

Dot

On Thu, Feb 3, 2011 at 12:22 PM, Gabriel Bodard <gabriel.bodard <at> kcl.ac.uk> wrote:
Dear all,

Do you have a method for encoding more than one msIdentifier (such as accession number or inventory number) for a single manuscript? As far as I can see neither tei:msIdentifier nor tei:idno are repeatable in that (required) position at the top of tei:msDesc.

We have instances of texts, for example, that are made up of two fragments accessioned separately, or only joined after being catalogued in their museum or library, and so both accession numbers continue to be associated with the single text object.

All suggestions gratefully received.

Gabby


--
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)

Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Email: gabriel.bodard <at> kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/



--
*~*~*~*~*~*~*~*~*~*~*
Dot Porter (MA, MSLS)       
Digital Medievalist, Digital Librarian
Email: dot.porter <at> gmail.com
*~*~*~*~*~*~*~*~*~*~*
Permalink | Reply | 4 comments |
headers
Gabriel Bodard | 3 Feb 2011 18:22
Picon
Favicon

multiple msIdentifiers

Dear all,

Do you have a method for encoding more than one msIdentifier (such as 
accession number or inventory number) for a single manuscript? As far as 
I can see neither tei:msIdentifier nor tei:idno are repeatable in that 
(required) position at the top of tei:msDesc.

We have instances of texts, for example, that are made up of two 
fragments accessioned separately, or only joined after being catalogued 
in their museum or library, and so both accession numbers continue to be 
associated with the single text object.

All suggestions gratefully received.

Gabby

--

-- 
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)

Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Email: gabriel.bodard <at> kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/
Permalink | Reply | 7 comments |
headers
Elena Pierazzo | 3 Feb 2011 18:31
Picon
Favicon

Re: multiple msIdentifiers

Hi Gabby, 

This should be the role of <altIdentifier>: "(alternative identifier) contains an alternative or former
structured identifier used for a manuscript, such as a former catalogue number".
<altIdentifier> is repeatable.

Best
Elena

On 3 Feb 2011, at 17:22, Gabriel Bodard wrote:

> Dear all,
> 
> Do you have a method for encoding more than one msIdentifier (such as 
> accession number or inventory number) for a single manuscript? As far as 
> I can see neither tei:msIdentifier nor tei:idno are repeatable in that 
> (required) position at the top of tei:msDesc.
> 
> We have instances of texts, for example, that are made up of two 
> fragments accessioned separately, or only joined after being catalogued 
> in their museum or library, and so both accession numbers continue to be 
> associated with the single text object.
> 
> All suggestions gratefully received.
> 
> Gabby
> 
> 
> -- 
> Dr Gabriel BODARD
> (Research Associate in Digital Epigraphy)
> 
> Centre for Computing in the Humanities
> King's College London
> 26-29 Drury Lane
> London WC2B 5RL
> Email: gabriel.bodard <at> kcl.ac.uk
> Tel: +44 (0)20 7848 1388
> Fax: +44 (0)20 7848 2980
> 
> http://www.digitalclassicist.org/
> http://www.currentepigraphy.org/

--
Dr Elena Pierazzo
Lecturer in Digital Humanities
Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL

Phone: 0207-848-1949
Fax: 0207-848-2980
elena.pierazzo <at> kcl.ac.uk
www.kcl.ac.uk
Permalink | Reply | 0 comments |
headers
James Cummings | 3 Feb 2011 18:46
Picon
Picon
Favicon

Re: multiple msIdentifiers

On 03/02/11 17:34, Dot Porter wrote:
> Gabby, I believe this is what altIdentifier is for.
>
> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-altIdentifier.html
>
> This does mean that you have to pick on identifier as the primary
> one.

I'm not sure this is true.  You are no longer required to have an 
<idno> so you could just have a series of <altIdentifier> or 
indeed <msName> elements.  It might be considered *good practice* 
to designate its currently used identifier as <idno> but it isn't 
a requirement in the current TEI I don't think.

-James

--

-- 
Dr James Cummings, Research Technologies Service
OUCS, University of Oxford
Permalink | Reply | 3 comments |

Gmane