Nesvet, Rebecca | 14 Feb 02:52 2016

<distinct> for cockney slang?

Please, is there a <distinct> “type”= for cockney (including but not limited to rhyming) slang already established?

Forgive me if this is answered somewhere; I did search the guidelines first.

 

Rebecca Nesvet

UW-Green Bay

nesvetr <at> uwgb.edu

 

Ioana Galleron | 12 Feb 10:42 2016
Picon

signatures

Dear all,

I am trying to encode a document containing minutes of meetings; these minutes contain the signatures of the participants, and these are quite legible, but they are spread on the entire surface of the page, in no specific order (obviously, they signed where they found some room).
I was wondering which is the best solution to represent this, and what are the most appropriate elements.

My decision so far was to use <list> and <item>, but I don’t know what I could put in.
Should I go for :
<list><item><name>Poisson</name></item></list>

or rather :
<list><item><signatures>Poisson</signatures></item></list>?

The second solution seems a bit of an abuse, as <signatures> are supposed to be used for "discussion of the leaf or quire signatures found within a codex », and not actually for the transcription of the signature. On the other had, it has the advantage to indicate clearly the nature of the textual element. As for <signed>, P5 say "contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text », which is not the situation here.

I would be gratefull for suggestions or links towards XML docs treating the same problems.

Thank you,
Ioana Galleron

Roman Bleier | 11 Feb 16:55 2016
Picon

New release: Versioning Machine 5.0

Dear list members,
we are delighted to announce a new release of the Versioning Machine: 5.0 (http://v-machine.org/). The
Versioning Machine is a framework and an interface for displaying multiple versions of text encoded
according to the Text Encoding Initiative (TEI) Guidelines. This new release incorporates a number of
new features,  including the ability to resize and reorganize text panels, panning and zooming in the
image viewer, and text-audio interlinking. Moreover, the Versioning Machine’s underlying code has
also been completely revised to make it more compatible with newer technologies.

The new Versioning Machine blog contains also a section called ‘VM in use’. There you will find
projects that have used VM in the past. If you are a VM user and you would like that us to link to your edition,
please send us a short project description and a link to your project website.

As ever, we welcome feedback on the VM and if you have questions about using it please contact the VM team via
the comment page at http://v-machine.org/comments/

With all best wishes, 

The Versioning Machine Team

E: versioningmachine <at> gmail.com

Christian Grün | 8 Feb 17:50 2016
Picon

[ANN] BaseX 8.4: The XML Prague 2016 Edition

Dear all,

Aligned with the XML Prague 2016 Conference, we are more than happy to
provide you with a great new version of BaseX, your XML database
system and XQuery processor! These are the new features:

 GUI
 - Project View: all modules of the project are now parsed in the background
 - Create Database, Properties: easy access to advanced database options
 - Sort Dialog: order by column positions and locale collation

 INDEXING
 - New Token Index: speedy token lookups in DITA and HTML documents
 - Including full support for incremental and main-memory databases
 - XQuery optimizations for fn:contains-token, fn:tokenize, fn:idref

 WEB APPLICATIONS
 - Cancel server-side queries via %rest:single annotation
 - DBA query editor: faster querying, better responsivity

 XQUERY
 - Database Module: ADDCACHE support (caching of large results)
 - Direct output of binary data with new 'basex' serialization method
 - Better XQuery 3.1 compliance: string constructors, new functions
 - Java bindings: address specific Java function signatures
 - User Module: create users and grant permissions in one step

 DOCUMENTATION
 - Many Wiki articles have been revised and updated

A big thank you to our sponsors, which made some new features possible
and available to everyone, and a special shout-out to Jens Erat, who
realized the new token index!

Visit http://basex.org to find the latest release.
We are looking forward to your feedback,

Christian
BaseX Team

Ioana Galleron | 6 Feb 14:38 2016
Picon

set element

Dear all,

I am trying to encode plays mixing « normal » acts with « divertissement » (which are mainly musical
parts, but can also contain plain dialogue).
I just realised the « set » element is not allowed in the body of the play, while my « divertissements » may
have different settings than that of the play in which they are included. For instance, a «
divertissement » is supposed to take place in the street, during the night, while the play is indoors all along.
My questions are, therefore:
- how would you encode the location if the divertissement in this case? I can always use a <p>, but the
specific information will be lost, and <stage> does not seem appropriate;
- more generally, am I ignoring specific guidelines existing for such mixed plays (an equivalent of «
prologue » or <epilogue>, something as « interlude »)?
Thank you in advance,
Ioana Galleron

David Sewell | 4 Feb 22:50 2016

Appropriate TEI element for enclosing raw untagged text?

We are sending off for TEI-XML conversion a publication in many volumes for 
which separate cumulative index volumes were issued from time to time. Because 
the back-of-the-book indexes for each regular volume were superseded by the 
cumulative indexes, I see no reason to have them tagged granularly. But for 
reference purposes we'll probably want the raw character data for each one.

My instinct is just to ask for something like

<div1 type="index">
<head>Index</head>
<ab>
Adams, Anne, see Wilson, Anne Adams
Adams, Herbert Baxter, WW on, 15,n20
[etc. etc. etc.]
</ab>
</div1>

with line-for-line pure UTF-8 transcription within <ab>.

Am I forgetting about a TEI element more suited to this purpose?

Nothing crucial hangs on this--I'm just curious.

David

--

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400318, Charlottesville, VA 22904-4314 USA
Email: dsewell <at> virginia.edu   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

B Tommie Usdin | 4 Feb 18:33 2016

[ANN] Call for Paper: Balisage: The Markup Conference 2016

Balisage: The Markup Conference 2016
http://balisage.net/

2-5 August 2016 — Balisage: The Markup ConferenceBethesda North Marriott Hotel & Conference Center,
Bethesda, MD, USA

Balisage is the premier conference on the theory, practice, design, development, and application of
markup. Unfamiliar with Balisage? To get a taste of Balisage, browse the Proceedings' Master Topics List
(http://balisage.net/Proceedings/topics.html) by clicking on the "+" to expand the ‘Concepts',
‘Specifications', or ‘Processes' topics lists or scan the Proceedings’ Master Bibliography at http://balisage.net/Proceedings/bibliography.html

CALL FOR PARTICIPATION
http://balisage.net/Call4Participation.html

We solicit papers on any aspect of markup and its uses; topics include but are not limited to:

- Web application development with XML
- Informal data models and consensus-based vocabularies
- Integration of XML with other technologies (e.g., content management, XSLT, XQuery)
- Performance issues in parsing, XML database retrieval, or XSLT processing
- Development of angle-bracket-free user interfaces for non-technical users
- Semistructured data and full text search
- Deployment of XML systems for enterprise data
- Web application development with XML
- Design and implementation of XML vocabularies
- Case studies of the use of XML for publishing, interchange, or archiving
- Alternatives to XML
- the role(s) of XML in the application lifecycle
- the role(s) of vocabularies in XML environments

All papers are peer-reviewed — we pride ourselves that you will seldom get a more thorough, skeptical, or
helpful review than the one provided by Balisage reviewers.

WHERE TO GET HELP

Email: info <at> balisage.net for help, advice, or encouragement about a Balisage submission. 
Wonder if your idea will make an appropriate Balisage paper? Ask us! Unsure if the people at Balisage would
be interested in the work you are doing? We'll be happy to discuss it with you. Need help making your paper
into XML as required for submission? Speak up; we'll find someone to help.

KEY DATES

- 15 March 2016 — Peer review applications due
- 22 April 2016 — Paper submissions due
- 21 May 2016 — Speakers notified
- 8 July 2016 — Final papers due
- 1 August 2016 — XML In, Web Out: 
      International Symposium on sub rosa XML
- 2–5 August 2016 — Balisage: The Markup Conference

For more information: info <at> balisage.net or +1 301 315 9631

Balisage: The Markup Conference
There is Nothing As Practical As A Good Theory

======================================================================
Balisage: The Markup Conference 2016          mailto:info <at> balisage.net
August 2-5, 2016                               http://www.balisage.net
Preconference Symposium: August 1, 2016                +1 301 315 9631
======================================================================

Susan Schreibman | 3 Feb 20:10 2016
Picon

Tech Officer Position Open An Foras Feasa, Maynooth U

-- Apologies for Cross Posting --

An Foras Feasa, the Digital Humanities Institute at Maynooth University, Ireland,  is seeking a creative technical lead to join a growing and dynamic team with a variety of local and international DH projects. 

The successful candidate will contribute to the development of Digital Humanities as an area of intensive research and teaching. Current projects include Letters of 1916, Contested Memories: The Battle of Mount Street Bridge, and the pan-European dariahTeach.

The post holder will work closely with staff in An Foras Feasa to develop technical solutions for digital humanities scholarship, including information design, data analysis, and data modelling, data discovery while assisting with the development of solutions for both public facing projects and administrative tools and solutions.

There is the opportunity to collaborate on grant opportunities and work in conjunction with the staff at An Foras Feasa to promote and develop digital humanities on campus. It is also possible to participate in digital humanities teaching at Maynooth University, particularly at the MA level, including thesis and practicum co-supervision.

Further particulars are available here
www.maynoothuniversity.ie/human-resources/vacancies

For an informal conversation, please contact Susan Schreibman. Contact details below. -- Susan Schreibman Professor of Digital Humanities Director of An Foras Feasa Iontas Building Maynooth University Maynooth, Co. Kildare email: susan.schreibman <at> nuim.ie phone: +353 1 708 3451 fax: +353 1 708 4797
Mathias Müller | 3 Feb 10:43 2016
Picon

Display annotations in several languages

Dear list

In our ODD document, we have described content with tei:desc elements in the following way:

<attDef ident="scribe" mode="replace">
    <desc xml:lang="de">gibt Informationen zur Hand bzw. zum Schreiber des
        Textes</desc>
    <desc xml:lang="en">gives information on the hand or the scribe, respectively</desc>
    <!--definition of the attribute content-->
</attDef>


From this ODD, we generate RNG where tei:desc is turned into "documentation" elements, the contents of which can be displayed as a tooltip by Oxygen, when editing an XML document associated with the RNG schema.

Unfortunately, this process appears to depend on the attribute <at> docLang of the tei:schemaSpec element. If, for instance, the schemaSpec element has

<schemaSpec docLang="en">

then only the English tei:desc element will be turned into an RNG documentation element:

<attribute name="scribe">
    <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">gives information on the hand or the scribe, respectively</a:documentation>
         <text/>
</attribute>


Also, the documentation element does not have an xml:lang attribute to associate it with a language. If I edit the RNG manually:

<attribute name="scribe">
      <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xml:lang="de">Identifiziert den Schreiber des Textes</a:documentation>
      <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xml:lang="en">EN Text here!</a:documentation>
      <text/>
</attribute>


then Oxygen displays all annotations, and prefixes them with the languages - which is what I need. Or, even more ideally, Oxygen would determine the user's system or Oxygen language and only display annotations in this language.

Our editors speak only one of several languages and I can see two solutions that are both unsatisfying: 1) generating the RNG separately for each language, seems like a workaround or 2) modifying the XSLT transformation that turns ODD into RNG, which would make it non-standard code.

My question is: Has anyone encountered this problem before? What is the standard way to have Oxygen display tei:desc annotations in several languages at the same time?

I am glad to give more information on my use case, as much as you need.

Thanks and regards
Mathias



Mathias Müller
BIN 2.B.04
Institute of Computational Linguistics
University of Zurich
+41 44 635 75 81
mathias.mueller <at> uzh.ch
Tommie Usdin | 2 Feb 17:48 2016

[ANN] Call for Participation: XML In, Web Out

XML In, Web Out: 
International Symposium on sub rosa XML

A Balisage pre-conference symposium
http://www.balisage.net/XML-In-Web-Out/

Come explore how the XML technology stack enables Great Web Applications from the 'basement' to the 'last mile’.

Chair: James Fuller, MarkLogic
Monday August 1, 2016
Bethesda North Marriott Hotel & Conference Center, Bethesda, MD, USA

THE SYMPOSIUM

In today's world 'application’ often means 'web application’. Most web applications are messy. The
current web application stack changes rapidly; frameworks go in and out of favor; the standards evolve;
JavaScript changes.

At the same time, mission critical applications are built on top of “big data”. We have large volumes of
often volatile data that must be accessed, distilled, summarized, and transformed for delivery to the web.

Enterprises desperately need to provide stable, scalable, and sustainable infrastructure to meet the
needs of modern applications. More and more organizations are using an XML infrastructure.
Appropriately-designed XML applications can enable “stable innovation” of mission-critical
information resources while handling new requirements, changing data models, and mitigating the churn
of constantly changing requirements.

CALL FOR PARTICIPATION

Tell us how you use XML infrastructure behind a web-based interface. We seek success stories and tales of
disappointments; Hopes for the future and plans for how to get there; Tools, techniques, approaches, and
philosophies that underlie integration of XML and the Web.

All papers are peer-reviewed — we pride ourselves that you will seldom get a more thorough, skeptical, or
helpful review than the one provided by Balisage reviewers.

WHERE TO GET HELP

Email: info <at> balisage.net for help, advice, or encouragement about a symposium submission. Wonder if
your idea will fit in at the symposium? Ask us! Unsure if the technical level of your presentation is
appropriate for the symposium participants? We'll be happy to discuss it with you! Need help making your
paper into XML as required for submission? Speak up; we'll find someone to help.

KEY DATES

- 15 March 2016 — Peer review applications due
- 22 April 2016 — Paper submissions due
- 21 May 2016 — Speakers notified
- 8 July 2016 — Final papers due
- 1 August 2016 — XML In, Web Out: 
         International Symposium on sub rosa XML
- 2–5 August 2016 — Balisage: The Markup Conference

For more information: info <at> balisage.net or +1 301 315 9631

Balisage: The Markup Conference
There is Nothing As Practical As A Good Theory

======================================================================
Balisage: The Markup Conference 2016          mailto:info <at> balisage.net
August 2-5, 2016                               http://www.balisage.net
Preconference Symposium: August 1, 2016                +1 301 315 9631
======================================================================

Patrick McAllister | 1 Feb 19:45 2016

Locations in bibliographical references

Dear list members,

does anyboy have recommendations for encoding location specifiers
(pages, verse numbers, etc.) in bibliographic references?

I'd need to get programmatic access to these specifiers, for example by
XPath.

I'm trying to get from sample cases like these:

Author1 2000:55
Author2 2000:55; 2005:32
Bekker 1094a1 (see https://en.wikipedia.org/wiki/Bekker_numbering)

to something like this:

\cite[55]{Author1_2000}
\cite[55]{Author2_2000}[32]{Author2_2005}
\cite[1094a1]{Bekker}

These are Bibtex cite commands, which use a key and allow an optional
argument that holds something following the note, usually the location
in the referenced work.

I found some ideas in the TEI Guidelines, but they're not completely
satisfactory it seems to me:

According to
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBICOB, one
way might be to use the bibl element, with a citedRange element in it:

<p>
  <quote>xyz.</quote>
  <bibl corresp="#Author1_2000">Author1 2000:<citedRange unit="page">55</citedRange></bibl>
</p>

That would work, but the Guidelines then say that one should
``... distinguish between a bibliographic reference, which is a
self-sufficient description of a bibliographic item, and a bibliographic
pointer, which is a short-form citation (e.g. Baxter, 1983),
...".

In the section ``Bibliographic Pointers"
(http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBIXR),
the Guidelines then recommend using ref elements, which seems natural
enough: you have a list of bibliographic entries, and refer to them from
the text.

But if so, I don't know where to put the location information.  I found
these two relevant examples, both in
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBIXR:

Nelson claims <ref target="#NEL80">(ibid, passim)</ref> 

and

Nelson claims (<ref target="#NEL80">Nelson [1980]</ref> pages 13–37)

In both cases, filtering out the locations would be difficult.

To add to this, there are cases where I refer to bibliographic entries
but can't easily use ref elements (or bibl). That happens in readings in
app elements:

<app>
<rdg src="#Author1_2000">xyz</rdg>
</app>

How would you make it clear, for example, what page and line number in
Author1_2000 the reading is from?

Any thoughts on this would be welcome!

--

-- 
Patrick McAllister

long-term mail: pma <at> rdorte.org


Gmane