Sebastian Rahtz

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Lou Burnard

> Home > Persons > Sebastian Rahtz

Publications

2013
[c8]
- view
  authority control:
- export record
  dblp key:
  - conf/doceng/RahtzB13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/doceng/RahtzB13
Sebastian Rahtz, Lou Burnard:
Reviewing the TEI ODD system. ACM Symposium on Document Engineering 2013: 193-196
2012
[c6]
- view
  - electronic edition @ uni-hamburg.de (archived)
  - no references & citations available
- export record
  dblp key:
  - conf/dihu/0003RBBGRB12
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/dihu/0003RBBGRB12
James Cummings, Sebastian Rahtz, Lou Burnard, Syd Bauman, Bertrand Gaiffe, Laurent Romary, Piotr Banski:
Future Developments for TEI ODD. DH 2012: 52-53
2004
[c3]
- view
  - electronic edition @ mulberrytech.com (archived)
  - no references & citations available
- export record
  dblp key:
  - conf/extreme/BurnardR04
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/extreme/BurnardR04
Lou Burnard, Sebastian Rahtz:
RelaxNG with Son of ODD. Extreme Markup Languages® 2004
2002
[c2]
- view
  - electronic edition @ nbn-resolving.org
  - no references & citations available
- export record
  dblp key:
  - conf/elpub/BurnardR02
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/elpub/BurnardR02
Lou Burnard, Sebastian Rahtz:
The Role of the Text Encoding Initiative (TEI) in the Authoring and Interchange of XML Documents. ELPUB 2002

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.