<?xml version="1.0" encoding="UTF-8"?>

<!-- Start license statement: do not remove 

EpiDoc: Guidelines for Structured Markup of Epigraphic Texts in TEI
Copyright (C) 2000-2006 by all contributors listed in <div type="gl-responsibility">, below.
Additional contributors' copyright may be designated in individual source files.

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.

Information about the EpiDoc community can be obtained via 
http://epidoc.sf.net.

End license statement: do not remove -->
<!DOCTYPE div SYSTEM "../dtd/tei-epidoc.dtd">
<!-- Start CVS information: do not remove -->
<!-- $Header: /cvsroot/epidoc/guidelines/src/introduction.xml,v 1.11 2007/07/11 17:42:17 paregorios Exp $ -->
<!-- End CVS information: do not remove -->
<div xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude" id="introduction" lang="en" rend="multipart">
    <head>Introduction and Organization</head>
        <p>The <bibl><title level="m">EpiDoc Guidelines</title></bibl> explain the use of the
            EpiDoc encoding scheme, which provides for the realization of electronic
            epigraphic editions, corpora and similar materials in the eXtensible Markup Language (XML). EpiDoc makes use of the 
        <xref href="http://www.tei-c.org">Text Encoding Initiative</xref> XML tagset, customizing it for epigraphic work.</p>
    <p>Several principles have been followed in developing these recommendations:</p>
    <list>
        <item>the markup language provides the same degrees of flexibility and rigor inherent in
            the format-oriented editing conventions employed by epigraphers in print</item>
        <item>format is separated from structure and meaning: therefore, characters may be used
            only to represent text characters and symbols; all editorial distinctions are made
            using structured markup </item>
        <item>rules laid down for the use of a given TEI tag in the <bibl><title level="m">TEI Guidelines</title></bibl> should be
            followed strictly by EpiDoc unless there is no appropriate encoding structure provided
            by TEI</item>
    </list>
        <p>The following sections provide a full introduction and orientation to the <bibl><title level="m">EpiDoc Guidelines</title></bibl>. They constitute 
            the essential starting point for new and prospective practitioners, as well as information technologists
            charged with supporting new EpiDoc projects.</p>
        <xi:include href="introeps.xml"/>
        <xi:include href="backgroundandrationale.xml"/>
                <xi:include href="conformance.xml"/>
        <xi:include href="gl-organization.xml"/>

        <xi:include href="gl-tech.xml"/>
    
    <div id="introduction-responsibility" type="gl-responsibility">
        <head>Responsibility for this section</head>
        <listBibl>
            <bibl>
                <respStmt>
                    <resp>author</resp>
                    <name>Tom Elliott</name>
                </respStmt>
            </bibl>
            <bibl>
                <respStmt>
                    <resp>author</resp>
                    <name>Julia Flanders</name>
                </respStmt>
            </bibl>
            <bibl>
                <respStmt>
                    <resp>author</resp>
                    <name>Charlotte Roueché</name>
                </respStmt>
            </bibl>
        </listBibl>
    </div>
    <div id="introduction-cvs" type="gl-cvs">
        <head><abbr expan="Concurrent Versioning System">CVS</abbr> Information</head>
        <p id="introduction-cvs-revision-number">Revision number: <seg n="cvs-revision-number"
                >$Revision: 1.11 $</seg></p>
        <p id="introduction-cvs-revision-name">Revision name (if any): <seg n="cvs-revision-name"
                >$Name: r-5 $</seg></p>
        <p id="introduction-cvs-revision-date">Revision date: <seg n="cvs-revision-date">$Date:
                2006/03/23 18:27:47 $</seg></p>
        <p id="introduction-cvs-revision-author">Revision committed by: <seg n="cvs-revision-author"
                >$Author: paregorios $</seg></p>
    </div>
</div>
