EpiDocumentation

Tom Elliott edited UpdatingTheWebPage

email@hidden (Tom Elliott) — Thu, 01 Oct 2009 19:13:51 +0000

How to update the epidoc web page at sourceforge
svn export https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpagezip -r w.zip webpagescp w.zip username@shell.sf.net:w.zipssh username@shell.sf.netnewgrp epidocunzip w.zip chmod -R ug+rw webpage/mv webpage/* /home/groups/e/ep/epidoc/htdocs/
According to this communique from our sourceforge overlords, things have changed. We need to test the above instructions against this change notice and revise accordingly:
Posted 1 day ago by moormanHello,This reminder is being provided to those project administrators who did not see our prior mailings announcing these changes, and to the project developers who did not receive copies of this information from their project administrators. Questions or concerns regarding this information should be escalated to SourceForge.net staff by submitting a new Support Request at: https://sourceforge.net/projects/alexandria/support/The access methods for project web file management have changed. The new accepted methods are: SFTP, SCP, rsync over SSH.The hostname for project web file management has changed. The new hostname for file management is: web.sourceforge.netThe username spec for project web file management has changed. The new username spec is USERNAME,PROJECTNAME@web.sourceforge.net which will permit you to authenticate with the SourceForge.net user account password or SSH key of the USERNAME user and obtain permissions to manage all files for the PROJECTNAME project.In line with our strategy for incremental service redeployment and improvement, interactive shell service (e.g. direct SSH in and having a prompt) has been dropped with this migration. Please see this post for more information on our short-term plans: http://sourceforge.net/community/forum/topic.php?id=3505&page&replies=1We've used the migration to make sweeping upgrades and improvements to the existing project shell, web and DB services. The Site Status forum contains a complete list of these details. Most changes are covered on our post announcing project web migration completion; we encourage all project admins and web administrators to review these changes (including the service-specific changes announced previously).Follow-up questions and concerns should be directed to SourceForge.net staff by submitting a new Support Request at: https://sourceforge.net/projects/alexandria/support/Thank you,Jacob MoormanDirector of Operations, SourceForge.net
Now note also the "new" interactive (virtual) shell environment: http://sourceforge.net/community/forum/topic.php?id=3953&page&replies=1rsync -aiv projects.shtml username,epidoc@web.sourceforge.net:htdocs/
See further:
https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service

Tom Elliott added FileRelease

email@hidden (Tom Elliott) — Mon, 02 Mar 2009 22:41:21 +0000

http://apps.sourceforge.net/trac/sitedocs/wiki/Release%20files%20for%20download

Tom Elliott edited AdminHowTos

email@hidden (Tom Elliott) — Mon, 02 Mar 2009 22:40:59 +0000

Tom Elliott edited AdminHowTos

email@hidden (Tom Elliott) — Mon, 02 Mar 2009 22:40:34 +0000

UpdatingTheDevDTDOnline
UpdatingTheWebPage
FileRelease

edited UpdatingTheWebPage

email@hidden () — Fri, 31 Oct 2008 12:55:04 +0000

According to this communique from our sourceforge overlords, things have changed. We need to test the above instructions against this change notice and revise accordingly:
Posted 1 day ago by moormanHello,This reminder is being provided to those project administrators who did not see our prior mailings announcing these changes, and to the project developers who did not receive copies of this information from their project administrators. Questions or concerns regarding this information should be escalated to SourceForge.net staff by submitting a new Support Request at: https://sourceforge.net/projects/alexandria/support/The access methods for project web file management have changed. The new accepted methods are: SFTP, SCP, rsync over SSH.The hostname for project web file management has changed. The new hostname for file management is: web.sourceforge.netThe username spec for project web file management has changed. The new username spec is USERNAME,PROJECTNAME@web.sourceforge.net which will permit you to authenticate with the SourceForge.net user account password or SSH key of the USERNAME user and obtain permissions to manage all files for the PROJECTNAME project.In line with our strategy for incremental service redeployment and improvement, interactive shell service (e.g. direct SSH in and having a prompt) has been dropped with this migration. Please see this post for more information on our short-term plans: http://sourceforge.net/community/forum/topic.php?id=3505&page&replies=1We've used the migration to make sweeping upgrades and improvements to the existing project shell, web and DB services. The Site Status forum contains a complete list of these details. Most changes are covered on our post announcing project web migration completion; we encourage all project admins and web administrators to review these changes (including the service-specific changes announced previously).Follow-up questions and concerns should be directed to SourceForge.net staff by submitting a new Support Request at: https://sourceforge.net/projects/alexandria/support/Thank you,Jacob MoormanDirector of Operations, SourceForge.net
Now note also the "new" interactive (virtual) shell environment: http://sourceforge.net/community/forum/topic.php?id=3953&page&replies=1

edited CrossWalkerIdp2

email@hidden () — Mon, 27 Oct 2008 14:51:08 +0000

processesing package:
investigate xproc to see if that answers more questions than it did 2 years ago (HC)
suck it and see
all else fails, back to XSLT 2.0 etc

edited CrossWalkerIdp2

email@hidden () — Mon, 27 Oct 2008 14:49:26 +0000

compare 2006 work in Chapel Hill
investigate existing schemas for mapping equivalences (all: ask TE,SG,Rahtz, etc.)
ask on TEI-L (HC)
processesing package:
investigate xproc to see if that answers more questions than it did 2 years ago (HC)

edited CrossWalker

email@hidden () — Mon, 20 Oct 2008 13:45:33 +0000

An XSL transform interacts with the crosswalk file to produce a separate, custom XSL transformation file that can then be used to create EpiDoc documents from the database format and vice versa. Data may be replicated and combined from one or more elements in the source file to a single field (or element) in the output. Multiple source locations (indicated with XPath expressions) and hard-coded default values (if the XPath fails) may be specified. String replacements, value substitutions (for, e.g., vocabulary conversions) and user-supplied XSL transformations may be performed on the data by supplying the appropriate information in the crosswalk file.
This tool is still under preliminary development, although most features for production of CSV are fully implemented, and the December 2006 EpiDoc sprint resulted in much of the functionality for the EDR to EpiDoc process being drafted.
CrossWalkerIdp2
Crosswalker tool core workflow
HGV to EpiDoc Crosswalk

edited CrossWalkerIdp2

email@hidden () — Mon, 20 Oct 2008 13:31:20 +0000

key-value pair format:
compare 2006 work in Chapel Hill
equivalences (all: ask TE,SG,Rahtz, etc.)
processesing package:
investigate xproc to see if that answers more questions than it did 2 years ~~ago~~ ago (HC)

edited CrossWalkerIdp2

email@hidden () — Mon, 20 Oct 2008 13:24:51 +0000

CrossWalker Development under IDP2
ZA, GB, HC chat (2008-10-20)
*Review diagram at Hgv2EpiDocCrossWalk
local files (template and key-value pairs)
processes (kv-to-XSLT, kv+template-to-epidoc)
key-value pair format:
compare 2006 work in Chapel Hill
investigate existing schemas for mapping equivalences
investigate xproc to see if that answers more questions than it did 2 years ago

added CrossWalkerIdp2

email@hidden () — Mon, 20 Oct 2008 13:20:17 +0000

!~CrossWalker Development under IDP2 |ZA, GB, HC chat (2008-10-20)| *

edited CrosswalkingManifesto

email@hidden () — Fri, 10 Oct 2008 14:39:59 +0000

Conformance and interoperability concerns for EpiDoc are described in the Conformance section of the guidelines.
EDRMetadataCrosswalk: a Google Spreadsheet showing basic EDR/EpiDoc equivalences
~~...~~See EDR crosswalk authority lists (with keyword translation in progress):
ReiMateria
Scriptura
TituluorumDistributio
VirorumDistributio
RerumInscriptarumDistributio

edited CrosswalkingManifesto

email@hidden () — Fri, 10 Oct 2008 14:34:49 +0000

Numismatics
The projects in the first of these categories, those using databases or other electronic media, are generally well-established projects who are not about to abandon their existing technologies. The EpiDoc community considers it vital to encourage compatibilty and synergy between platforms and has long been in communication with these projects to that end. On the one hand, we need to ensure that "core" EpiDoc recommendations are adequate for the needs of these projects and the categories that they have established and agreed upon. Resolving issues of compatibility may involve modifications to EpiDoc, to the sister project, or to both. On the other, it is also important to create and maintain tools for crosswalking from one format to the other (e.g. the CrossWalker) in those cases where complete compatibility is not possible or desirable, for one reason or another.
recommendations.
~~The~~ The most urgent task in all these cases is *identifying* the needs of such projects/conventions and communicating with the people ~~involved.~~ involved.
EAGLE Conformance
Conformance and interoperability concerns for EpiDoc are described in the Conformance section of the guidelines.
EDRMetadataCrosswalk: a Google Spreadsheet showing basic EDR/EpiDoc equivalences
...

edited UpdatingTheWebPage

email@hidden () — Mon, 22 Sep 2008 12:53:42 +0000

edited UpdatingTheWebPage

email@hidden () — Wed, 03 Sep 2008 17:39:09 +0000

How to update the epidoc web page at sourceforge
w.zip mv chmod -R ug+rw webpage/mv webpage/* /home/groups/e/ep/epidoc/htdocs/

edited UpdatingTheWebPage

email@hidden () — Wed, 03 Sep 2008 17:37:03 +0000

How to update the epidoc web page at sourceforge
username@shell.sf.net:w.zipssh ~~username@shell.sf.netunzip~~ username@shell.sf.netnewgrp epidocunzip w.zip mv webpage/* /home/groups/e/ep/epidoc/htdocs/

edited XwalkCoreWorkFlow

email@hidden () — Sun, 18 May 2008 16:45:35 +0000

(generated)
a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml
on ~~epigraphis~~ epigraphic text ~~field)~~ field, translation)
epidocHGV.xml
(generated)
~~...~~an XML file containing the key value pairs in the form of variables needed for import into EpiDoc XML
hgvkv2epidoc.xml
(local file)
a ~~template~~ template defining the placement of key values into EpiDoc XML (context + variables)
kv2epidoc.xsl
(core xWalker script)
...
.sidebar_v2 { display: none; }

edited XwalkCoreWorkFlow

email@hidden () — Sun, 18 May 2008 16:22:37 +0000

(generated)
...
~~****~~hgvkv2epidoc.xml
(local file)
a template
.sidebar_v2 { display: none; }

edited XwalkCoreWorkFlow

email@hidden () — Sun, 18 May 2008 16:10:12 +0000

(generated)
a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml
at this stage a runner.sh may also be generated if Transcode, CHET-C, or other processes also need to be run (e.g. on epigraphis text field)
epidocHGV.xml
(generated)
...
****
.sidebar_v2 { display: none; }

added XwalkCoreWorkFlow

email@hidden () — Sun, 18 May 2008 16:00:15 +0000

! Crosswalker Core Tool Workflow (See CrossWalker page for more detailed specs and files) !!! In diagram above: * crosswalker.xsl and kv2epidoc.xsl are the core CrossWalker scripts * hgv2kv.xml and hgvkv2epidoc.xml are local, user-defined files (for \"hgv\" substitute name of local project/schema) * HGV.xml is the input file * all other files are generated by the process and therefore should not need hand-editing at any stage !!!The elements: # **hgv2kv.xml** ## (local file) ## defines the key value pairs (data fields or elements) that are to be exported from the source database/schema ## may include element definitions, copy or combine instructions, or XSLT 2.0 templates # **crosswalker.xsl** ## (core xWalker script) ## a stylesheet that acts upon hgv2kv.xml and creates hgv2kv.xsl # **hgv2kv.xsl** ## (generated) ## a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml # **epidocHGV.xml** ## (generated)

renamed

email@hidden () — Sun, 18 May 2008 15:42:36 +0000

hgv-crosswalker.jpg

edited CrossWalker

email@hidden () — Sun, 18 May 2008 15:28:33 +0000

An XSL transform interacts with the crosswalk file to produce a separate, custom XSL transformation file that can then be used to create EpiDoc documents from the database format and vice versa. Data may be replicated and combined from one or more elements in the source file to a single field (or element) in the output. Multiple source locations (indicated with XPath expressions) and hard-coded default values (if the XPath fails) may be specified. String replacements, value substitutions (for, e.g., vocabulary conversions) and user-supplied XSL transformations may be performed on the data by supplying the appropriate information in the crosswalk file.
This tool is still under preliminary development, although most features for production of CSV are fully implemented, and the December 2006 EpiDoc sprint resulted in much of the functionality for the EDR to EpiDoc process being drafted.
~~Hgv2EpiDocCrossWalk~~Crosswalker tool core workflow
HGV to EpiDoc Crosswalk
EpiDoc to CSV Crosswalk
EDR Crosswalk Workflow

edited Hgv2EpiDocCrossWalk

email@hidden () — Sun, 18 May 2008 15:23:11 +0000

added Hgv2EpiDocCrossWalk

email@hidden () — Sun, 18 May 2008 15:22:22 +0000

! Crosswalk modules for HGV metadata to ~EpiDoc (See also http://epidocdukepapy.pbwiki.com/HGVMetadataXSLTConverter) * IDP project created a one-off crosswalk script in XSLT 2.0 (2008-Feb/Apr) ** Moving one record in HGV.fp8 into one ~EpiDoc XML file ** Mapping each HGV metadata record to one+ DDbDP text * Revisited code and workflow for EDR crosswalk (2008-May) (see image below) ** Core Crosswalker code (crosswalker.xsl, kv2epidoc.xsl) *** To upgrade from eXSLT to XSLT 2.0 *** Test and iterate, requiring... ** Local Crosswalker modules (hgv2kv.xml, hgvkv2epidoc.xml) *** hgv2kv.xml (Key Value definitions) will contain XSLT snippets from IDP *** hgvkv2epidoc.xml (~EpiDoc template) will largely come from HGV EpiDoc template created by JC/GB in 2008-Feb *** ...

renamed

email@hidden () — Sun, 18 May 2008 15:21:25 +0000

hgv-crosswalker.jpg

edited CrossWalker

email@hidden () — Sun, 18 May 2008 14:59:22 +0000

An XSL transform interacts with the crosswalk file to produce a separate, custom XSL transformation file that can then be used to create EpiDoc documents from the database format and vice versa. Data may be replicated and combined from one or more elements in the source file to a single field (or element) in the output. Multiple source locations (indicated with XPath expressions) and hard-coded default values (if the XPath fails) may be specified. String replacements, value substitutions (for, e.g., vocabulary conversions) and user-supplied XSL transformations may be performed on the data by supplying the appropriate information in the crosswalk file.
This tool is still under preliminary development, although most features for production of CSV are fully implemented, and the December 2006 EpiDoc sprint resulted in much of the functionality for the EDR to EpiDoc process being drafted.
Hgv2EpiDocCrossWalk
EpiDoc to CSV Crosswalk
EDR Crosswalk Workflow

edited EdrXwalkWorkflow

email@hidden () — Fri, 16 May 2008 22:00:45 +0000

You should now have a collection of EpiDoc documents (one per inscription) in the current folder.
NOTE: the kv2epidoc.xsl file uses XSLT Extensions which are only compatible with the the libxslt processor xsltproc. Specifically the function that allows multiple output documents works only in xsltproc.
(Diagram below sketched in 2008-MAY)

edited EdrXwalkWorkflow

email@hidden () — Fri, 16 May 2008 21:58:27 +0000

uploaded

email@hidden () — Fri, 16 May 2008 21:55:41 +0000

added UpdatingTheDevDTDOnline

email@hidden () — Wed, 30 Apr 2008 20:42:22 +0000

* cd to the dtd directory under your svn checkout $ scp tei-epidoc.dtd {username}@{devmachine}:tei-epidoc.dtd $ ssh {username}@{devmachine} $ cp tei-epidoc.dtd /var/www/html/epidoc/dtd/dev/

edited AdminHowTos

email@hidden () — Wed, 30 Apr 2008 20:41:00 +0000

BackingUpCVS
BackingUpSVN
~~GeneratingStaticGuidelines~~GeneratingStaticGuidelines (also how to update the online copy)
UpdatingTheDevDTDOnline
UpdatingTheWebPage

edited GeneratingStaticGuidelines

email@hidden () — Wed, 30 Apr 2008 20:35:42 +0000

customize a copy of staticgl.sh.example to reflect realities on your local filesystem, rename it staticgl.sh, put it somewhere in your PATH and make it executeable
customize a copy of config.xml.example to reflect realities on your local filesystem, rename it config.xml and save it into the same directory as the static generation code (i.e., staticgen)
{username}@{devserver}:gl.zip$ ssh {username}@{devserver}$ unzip gl.zip -d /var/www/html/epidoc/gl/dev/

added GeneratingStaticGuidelines

email@hidden () — Wed, 30 Apr 2008 20:18:58 +0000

Generating Static EpiDoc Guidelines * cd into the staticgen subdirectory under guidelines in your svn checkout tree * customize a copy of staticgl.sh.example to reflect realities on your local filesystem, rename it staticgl.sh, put it somewhere in your PATH and make it executeable * customize a copy of config.xml.example to reflect realities on your local filesystem, rename it config.xml and save it into the same directory as the static generation code (i.e., staticgen) $ staticgl.sh $ cd {output-dir-from-shell-script} $ zip gl.zip * $ scp gl.zip {username}@{devserver}:gl.zip $ unzip gl.zip -d /var/www/html/epidoc/gl/dev/

edited AdminHowTos

email@hidden () — Wed, 30 Apr 2008 19:47:24 +0000

BackingUpCVS
BackingUpSVN
GeneratingStaticGuidelines
UpdatingTheWebPage

edited UpdatingTheWebPage

email@hidden () — Thu, 17 Apr 2008 23:01:20 +0000

How to update the epidoc web page at sourceforge
~~$ svn~~svn export ~~https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage$ zip~~ https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpagezip -r w.zip ~~webpage$ scp~~ webpagescp w.zip ~~username@shell.sf.net:w.zip$ ssh username@shell.sf.net$ unzip~~ username@shell.sf.net:w.zipssh username@shell.sf.netunzip w.zip $ mv webpage/* /home/groups/e/ep/epidoc/htdocs/

added BackingUpSVN

email@hidden () — Thu, 17 Apr 2008 22:24:53 +0000

Per SourceForge guidance on backing up SVN: $ rsync -av epidoc.svn.sourceforge.net::svn/epidoc/* .

edited UpdatingTheWebPage

email@hidden () — Thu, 17 Apr 2008 22:21:33 +0000

How to update the epidoc web page at sourceforge
~~svn~~$ svn export https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage
zip https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage$ zip -r w.zip webpage
scp webpage$ scp w.zip username@shell.sf.net:w.zip
ssh username@shell.sf.net
unzip username@shell.sf.net:w.zip$ ssh username@shell.sf.net$ unzip w.zip
mv $ mv webpage/* /home/groups/e/ep/epidoc/htdocs/
exit /home/groups/e/ep/epidoc/htdocs/

added BackingUpCVS

email@hidden () — Thu, 17 Apr 2008 22:20:30 +0000

%5Bhttp://alexandria.wiki.sourceforge.net/CVS+-+Version+Control+for+Source+Code#rsync|Per SourceForge Documentation on CVS Backups%5D: $ rsync -av rsync://epidoc.cvs.sourceforge.net/cvsroot/epidoc/* .

edited AdminHowTos

email@hidden () — Thu, 17 Apr 2008 22:15:18 +0000

Administrative Howtos
BackingUpCVS
BackingUpSVN
UpdatingTheWebPage

edited UpdatingTheWebPage

email@hidden () — Thu, 17 Apr 2008 22:13:46 +0000

How to update the epidoc web page at sourceforge
* svnsvn export ~~https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage* zip~~ https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage
zip -r w.zip ~~webpage* scp~~ webpage
scp w.zip ~~username@shell.sf.net:w.zip* ssh username@shell.sf.net* unzip~~ username@shell.sf.net:w.zip
ssh username@shell.sf.net
unzip w.zip * mv
mv webpage/* ~~/home/groups/e/ep/epidoc/htdocs/* exit~~ /home/groups/e/ep/epidoc/htdocs/
exit

edited AdminHowTos

email@hidden () — Thu, 17 Apr 2008 22:13:27 +0000

Administrative Howtos
* UpdatingTheWebPageUpdatingTheWebPage

added AdminHowTos

email@hidden () — Thu, 17 Apr 2008 22:13:18 +0000

Administrative Howtos * UpdatingTheWebPage

edited HowTos

email@hidden () — Thu, 17 Apr 2008 22:12:47 +0000

How Tos (short, click-by-click tasks)
AdminHowTos
ChetCjs
UsingTheStandardStyleSheets

added UpdatingTheWebPage

email@hidden () — Thu, 17 Apr 2008 22:12:10 +0000

How to update the epidoc web page at sourceforge * svn export https://epidoc.svn.sourceforge.net/svnroot/epidoc/trunk/webpage * zip -r w.zip webpage * scp w.zip username@shell.sf.net:w.zip * ssh username@shell.sf.net * unzip w.zip * mv webpage/* /home/groups/e/ep/epidoc/htdocs/ * exit

edited CrossWalker

email@hidden () — Sun, 09 Sep 2007 13:43:45 +0000

EDR Crosswalk Workflow
EDR Crosswalker to-do list
CrosswalkertoolspecinEpiDukeWiki

edited XslTransformsWithOxygen

email@hidden () — Mon, 02 Jul 2007 22:58:20 +0000

Transformation to HTML
With your document open and at the foreground of Oxygen, press the 'Apply Transformation Scenario' button ( ).
scenarios ~~list.)~~ list; this should only be necessary the first time you run this scenario.)
If the transformation is successful, you will see the html version appear at the bottom of the screen. (The file will only transform if the XML validates to the DTD.)
To see the html file in your web browser, open the ‘html’ folder. Select your new html and open it with Firefox, Explorer or whichever browser you use.

edited ProjectDocumentation

email@hidden () — Fri, 15 Jun 2007 10:44:51 +0000

TechSupport : how much technical support will I need to put my inscriptions into EpiDoc?
EpiDocTraining : where can I get training for myself/my research assistants to learn EpiDoc?
HandVsAutoMarkup : what kinds of markup can be automated as opposed to tagged by hand?

edited XslTransformsWithOxygen

email@hidden () — Thu, 14 Jun 2007 15:23:34 +0000

edited XslTransformsWithOxygen

email@hidden () — Thu, 14 Jun 2007 15:21:57 +0000

Preparing your XML transformation scenario:
(You should only need to do this once in your Oxygen setup)
( ) )
Create a New scenario and give it the name 'Standard EpiDoc Stylesheets'
XML URL: should read
${currentFileURL}
( ) ) to the location of 'force-namespace-tei.xsl' (in epidoc-xsl/util folder)
Parameters: add a new parameter:
Name: screencsspath
Value: ../epidoc-xsl/css/epidocscreen.css
Press OK
( ) ) to the location of 'epidoc.xsl' (in epidoc-xsl/html folder). Press OK.
Output: set the value of "Save as" to:
../html/${cfn}.html

uploaded

email@hidden () — Thu, 14 Jun 2007 14:55:33 +0000

uploaded

email@hidden () — Thu, 14 Jun 2007 14:55:33 +0000

uploaded

email@hidden () — Thu, 14 Jun 2007 14:55:33 +0000

uploaded

email@hidden () — Thu, 14 Jun 2007 14:55:33 +0000

edited XslTransformsWithOxygen

email@hidden () — Thu, 14 Jun 2007 14:12:41 +0000

~~XSL~~ ~~Transforms~~Creating HTML output using EpiDoc Standard XSL and Oxygen
Before you start:
This document assumes that you have an 'epidoc' folder (as provided on the 'ss07' disc at the summer school) containing:
a folder 'xml' which holds the tei-epidoc.dtd and your XML files;
a folder 'html' which will contain your output HTML
a folder 'epidoc-xsl' which contains all of the Standard EpiDoc Stylesheets (as downloaded from SourceForge; this folder in turn contains: 'css', 'html', 'typographic', 'util')
If you are using a different folder structure, you may need to change some of the values below.
Opening XML in Oxygen
Open/create an xml file in Oxygen
Ensure that the Doctype declaration at the top of your file reads:
<!DOCTYPE TEI.2 SYSTEM "tei-epidoc.dtd">
(unless you are using a different folder structure with ~~<oXygen/>~~ the EpiDoc DTD in a different folder from the XML, in which case you need to define the path to that folder as well as the DTD file name)
Make sure that your XML file validates to the DTD by clicking on the 'validate' button ( ) on the toolbar.
Preparing your XML transformation scenario:
(You should only need to do this once in your Oxygen setup)
Select 'Configure Transformation Scenario' button from the toolbar ( )
Create a New scenario and give it the name 'Standard EpiDoc Stylesheets'
XML URL: should read
${currentFileURL}
XSL URL: browse ( ) to the location of 'force-namespace-tei.xsl' (in epidoc-xsl/util folder)
Parameters: add a new parameter:
Name: screencsspath
Value: ../epidoc-xsl/css/epidocscreen.css
Press OK
Additional Stylesheets: add a new stylesheet; browse ( ) to the location of 'epidoc.xsl' (in epidoc-xsl/html folder). Press OK.
Output: set the value of "Save as" to:
../html/${cfn}.html
(this will automatically create an output file in the 'html' folder with the same name as your XML file but the suffix '.html')
Press OK two more times to close the Transformation Scenarios box.
Transformation to HTML
With your document open and at the foreground of Oxygen, press the 'Apply Transformation Scenario' button ( ).
(If necessary, select "Standard EpiDoc Stylesheets" from the scenarios list.)
If the transformation is successful, you will see the html version appear at the bottom of the screen. (The file will only transform if the XML validates to the DTD.)
To see the html file in your web browser, open the ‘html’ folder. Select your new html and open it with Firefox, Explorer or whichever browser you use.

edited ConfigurableParametersForStyleSheets

email@hidden () — Fri, 08 Jun 2007 18:20:31 +0000

screencsspath = provides a uri for path to a css file for screen user agents (values: any valid uri; default = epidocscreen.css)
printcsspath = provides a uri for path to a css file for print (values: any valid url; default = epidocprint.css)
htmlcontentdivid = provides an id for the main content <div> in the html output (values: any valid xml ID; default = htmlcontent; note: changing this will break behavior in the standard epidoc css)
htmlheaderdivid = provides an id for the main header <div> in the html output (values: any valid xml ID; default = htmlcontent; note: changing this will break behavior in the standard epidoc css)
htmlseparatordivid = provides an id for the main separator <div> in the html output (values: any valid xml ID; default = htmlcontent; note: changing this will break behavior in the standard epidoc css)
vestigemark = sets the character(s) used to indicate unreadable vestiges of characters in output (values: any Unicode character; default = +)
gapmaxrepeat = sets maximum number of character widths in a <gap/> that will be rendered as single characters; gaps larger than this number will be rendered according to a style that incorporates a numeric indication of the gap width (values: 2-n; default = 3)
htmltitleheaderid = provides an id for the main title header in the html output (values: any valid xml ID; default = htmlcontent; note: changing this will break behavior in the standard epidoc css)
htmltitlecontentid = provides an id for the main title content section in the html output (values: any valid xml ID; default = htmlcontent; note: changing this will break behavior in the standard epidoc css)
epidocrefurl = provides a url for the EpiDoc home page
epidocrefstring
~~corrstyle~~ = provides a title for the EpiDoc home page
corrstyle = controls the style used to render editorial corrections (e.g., <choice type="correction"><sic>R</sic><corr>p</corr></choice>; values = panciera, seg, edh; default = panciera)

edited ConfigurableParametersForStyleSheets

email@hidden () — Fri, 08 Jun 2007 18:13:51 +0000

dotitlepage = controls creation of a separate title page (for guidelines processing only; values = yes|no; default = no)
stripcomments = suppresses xml comments in the source, rather than passing them on (as comments) in the result html (values = true|false; default = false)
{persnamepref}#{key} (values: any; default = personalnames.html)
placenameuriprefix = like persnameuriprefix (values: any; default = placenames.html)
linenumberinterval = interval at which line numbers are printed in output (values: 0-n; default = 5; note: 0 suppresses output)
faviconpath = provides a uri for path to a favicon (values: any valid uri; default = img/favicon.ico)
standalonecss = provides a uri for path to a standalone css file (values: any valid uri; default = none)
screencsspath
~~printcsspath~~ = provides a uri for path to a css file for screen user agents (values: any valid uri; default = epidocscreen.css)
printcsspath = provides a uri for path to a css file for print (values: any valid url; default = epidocprint.css)
htmlcontentdivid
htmlheaderdivid

added ConfigurableParametersForStyleSheets

email@hidden () — Fri, 08 Jun 2007 18:06:38 +0000

There are some user-configurable parameters for the standard EpiDoc stylesheets. These parameters can be used to modify some behaviors of the stylesheets at transformation time. More parameters (and therefore more easy customization options will be added in time). All parameters are to be found in the epidoc.xsl file. They are declared, and default values provided, with syntax like: no Best practice for transform customization using the parameters is not to modify epidoc.xsl; rather, most XSL processors facilitate the passing of parameters to the transform at execution time. Consult the documentation that comes with your XSL tool to discover how to pass parameter values to the transformation. The following parameters were supported as of 8 June 2007: * dotitlepage = controls creation of a separate title page (for guidelines processing only; values = yes|no; default = no) * stripcomments = suppresses xml comments in the source, rather than passing them on (as comments) in the result html (values = true|false; default = false) * persnameuriprefix = provides a uri fragment assumed to point to a file or other resource containing user-readable information about personal names; elements with a \"key\" attribute are processed to produce a link with an href like {persnamepref}#{key} * placenameuriprefix * linenumberinterval * faviconpath * standalonecss * screencsspath * printcsspath * htmlcontentdivid * htmlheaderdivid * htmlseparatordivid * vestigemark * gapmaxrepeat * htmltitleheaderid * htmltitlecontentid * epidocrefurl * epidocrefstring * corrstyle

edited UsingTheStandardStyleSheets

email@hidden () — Fri, 08 Jun 2007 17:54:31 +0000

The EpiDoc stylesheets may be downloaded from the SourceForge repository (either checked out using CVS or, for users who do not need to edit them, download a stablerelease).
Instructions on running the XSL Transformations using various processors can be found in the SoftwareDocumentation section.
ConfigurableParametersForStyleSheets
(to be added)

edited CrosswalkingManifesto

email@hidden () — Thu, 07 Jun 2007 09:35:29 +0000

edited CrosswalkingManifesto

email@hidden () — Thu, 07 Jun 2007 09:34:54 +0000

Duke Database of Documentary Papyri (DDbDP)
Packard Humanities Institute Greek Epigraphy database
Latin), and related Classical textual objects, who may have different conventions and needs than classical epigraphers, including:
South East Asian inscriptions
Etruscan Texts Project

edited FrontPage

email@hidden () — Wed, 06 Jun 2007 12:52:56 +0000

EpiDocumentation Wiki
This site is meant for the collaborative authoring and reviewing of documentation on core EpiDoc concepts, tools, and recommendations. If you would like to edit this Wiki, please contact the Markuplist with your request and you will be issued with the password.
Useful indexes to documentation, regardless of its "kind":
HowTos (short, click-by-click tasks)
Tutorials (longer, thematic, hands-on explanations)
GettingStarted (very basic guidelines)
Kinds of documentation to be found herein:
EpiDoc Tools (applications created and/or maintained by the EpiDoc community)
The Community (EpiDoc community protocols and collaborations)
RoadMap (Planning the future of EpiDoc development)
Useful indexes to documentation, regardless of its "kind":
HowTos (short, click-by-click tasks)
Tutorials (longer, thematic, hands-on explanations)
GettingStarted (very basic guidelines)

edited HowTos

email@hidden () — Wed, 06 Jun 2007 12:52:31 +0000

How Tos (short, click-by-click tasks)
ChetCjs
~~UsingTheStandardStylesheets~~UsingTheStandardStyleSheets
SettingUpOxygen
XslTransformsWithOxygen

added HowTos

email@hidden () — Wed, 06 Jun 2007 12:52:01 +0000

! How Tos (short, click-by-click tasks) * ChetCjs * UsingTheStandardStylesheets * SettingUpOxygen * XslTransformsWithOxygen * SettingUpJedit * XslTransformsWithJedit * EpiDocIrcChannel * MarkupList

edited MarkupList

email@hidden () — Wed, 06 Jun 2007 11:23:35 +0000

For discussion of Greek and Latin text markup issues.
http://lsv.uky.edu/archives/markup.html
community. ~~Gaps~~
Gaps in the Guidelines or Documentation should be reported the to Markup list in the first instance.
To join the list, either visit the archive page (above), and enter your email address in the form provided, or send an email to LISTSERV@LSV.UKY.EDU containing no subject line and only the words "subscribe markup" in the body. (Turn off your signature if you have one.)
The list is moderated by Tom Elliott and Ross Scaife.

edited MarkupList

email@hidden () — Wed, 06 Jun 2007 11:23:18 +0000

added MarkupList

email@hidden () — Wed, 06 Jun 2007 11:23:07 +0000

! The Markup List For discussion of Greek and Latin text markup issues. * http://lsv.uky.edu/archives/markup.html The Markup list is the primary venue for community discussion of major EpiDoc issues. We try not to get too fussily technical (although sometimes we fail); beginners\' contributions are always welcome and there is no such thing as a stupid question. (If you want to be sure your question has not been covered before, you can search the archives, which go back to 2001.) Very technical help may be taken off-list for private assistance, unless it is clearly of wide interest to the community. Gaps in the Guidelines or Documentation should be reported the to Markup list in the first instance. To join the list, either visit the archive page (above), and enter your email address in the form provided, or send an email to LISTSERV@LSV.UKY.EDU containing no subject line and only the words \"subscribe markup\" in the body. (Turn off your signature if you have one.) The list is moderated by Tom Elliott and Ross Scaife.

edited UsingTheStandardStyleSheets

email@hidden () — Wed, 06 Jun 2007 11:11:42 +0000

edited ChetCjs

email@hidden () — Wed, 06 Jun 2007 10:55:04 +0000

Documentation
Paste the Leiden-formatted text into the text box. By default, a line break in the text is taken to be a real line break in the inscription; if you don't want that, check the box marked ignore line breaks, in which case only a '/' willbe taken as a line break.
EpiDoc ~~file.~~ ~~You~~ file, and may need tweaking, correction, or disambiguation.
You would then typically add your own editorial comments, description, and so forth.
Bugs
Still being updated to work with Greek (be sure you have the latest version)

edited SettingUpOxygen

email@hidden () — Wed, 06 Jun 2007 10:54:05 +0000

Getting Started with <oXygen/>
The Oxygen XML editor is optimised for text encoding, and comes with several TEI-based tools and schemas (although not the EpiDoc DTD). It also comes with multiple XSL engines. As a result it is more or less ready to run out of the box. (Although bear in mind that if you have the demo license your installation will only run for 30 days unless you upgrade in that time.)
Set-up options:
(to be added)

added SettingUpOxygen

email@hidden () — Wed, 06 Jun 2007 10:53:45 +0000

! Getting Started with The Oxygen XML editor is optimised for text encoding, and comes with several TEI-based tools and schemas (although not the ~EpiDoc DTD). It also comes with multiple XSL engines. As a result it is more or less ready to run out of the box. (Although bear in mind that if you have the demo license your installation will only run for 30 days unless you upgrade in that time.)

edited FrontPage

email@hidden () — Wed, 06 Jun 2007 10:28:01 +0000

GettingStarted (very basic guidelines)
Kinds of documentation to be found herein:
~~ToolDocumentation~~ ~~(tools~~EpiDoc Tools (applications created and/or maintained by the EpiDoc community)
~~ProjectDocumentation~~
Project Documentation (project setup and maintenance)
~~GuidelinesDocumentation~~
Common Software (help setting up/using common XML tools etc.)
Guidelines Documentation (help with the EpiDoc Guidelines)
~~CommunityDocumentation~~
The Community (EpiDoc community protocols and ~~collaborations)~~
~~SoftwareDocumentation~~ ~~(help~~ ~~setting~~ ~~up/using~~ ~~common~~ ~~XML~~ ~~tools~~ ~~etc.)~~ collaborations)
RoadMap (Planning the future of EpiDoc development)

added XslTransformsWithOxygen

email@hidden () — Fri, 01 Jun 2007 11:07:17 +0000

! XSL Transforms with

edited XslTransformsWithJedit

email@hidden () — Tue, 20 Mar 2007 21:55:52 +0000

Transforming the XML using jEdit
the ~~final~~ ~~section~~ subsections below.)
There are some bugs in jEdit performance: we have documented work-arounds to three of these serious problems below.
Open the XML file in jEdit. If the XSLT Processor is not already open, click on the 'XSLT Processor' tab (we recommend docking this tab at the bottom of the window but some may prefer to open a 'floating' window.)
Name the file
Go to where the file is saved to open it in your web browser
XSLT Plugin required
The above instructions assume that you have the JEdit XSLT plugin installed. In order to install it:
Select Plugins -> Plugin Manager
Select the "Install" tab
Wait for the Plugins list to download
Click the word "Name" above the column of plugin names to sort them alphabetically
Scroll down and select the checkbox for "XSLT" (note: the plugin manager will automatically select some other plugins, which are needed by the XSLT plugin)
Select the "Install" button
If you get "timeout" errors:
Select the "download options" button
Select "Update mirrors list" button
Choose one of the mirror sites
Select the "apply" button
Select the "ok" button
Try to download and install the plugin again using the steps above
Setting the CSS Parameter
At the moment the parameter function in jEdit does not seem to work correctly (as of version 4.2). The EpiDoc stylesheets require one parameter to be set, which needs to be edited by hand in your local copy of the stylesheets; this is the standalonecss parameter (which tells the output HTML where to find the CSS which displays it correctly in the browser).

edited UsingTheStandardStyleSheets

email@hidden () — Tue, 20 Mar 2007 15:48:07 +0000

added UsingTheStandardStyleSheets

email@hidden () — Tue, 20 Mar 2007 15:47:52 +0000

! Using the Standard EpiDoc Stylesheets The EpiDoc stylesheets may be downloaded from the SourceForge repository (either checked out using CVS or, for users who do not need to edit them, download a %5Bhttp://sourceforge.net/project/showfiles.php?group_id=60289&package_id=182239&release_id=413328 stable release%5D). Instructions on running the XSL Transformations using various processors can be found in the SoftwareDocumentation section.

edited FrontPage

email@hidden () — Tue, 20 Mar 2007 15:27:34 +0000

HowTos (short, click-by-click tasks)
Tutorials (longer, thematic, hands-on explanations)
GettingStarted (very basic guidelines)
Kinds of documentation to be found herein:
ToolDocumentation (tools created and/or maintained by the EpiDoc community)

edited SoftwareDocumentation

email@hidden () — Thu, 04 Jan 2007 23:30:33 +0000

* XslTransformsWithOxygen
* XslTransformsWithJedit
* XslTransformsWithCommandLine
** ** %5BXslTransformsWithXSLTProc%5D
** XslTransformsWithSaxon
!!! Collaboration tools

edited SoftwareDocumentation

email@hidden () — Thu, 04 Jan 2007 23:30:22 +0000

* XslTransformsWithOxygen
* XslTransformsWithJedit
* XslTransformsWithCommandLine
* XslTransformsWithXSLTProc
* XslTransformsWithSaxon
** XslTransformsWithXSLTProc
** XslTransformsWithSaxon
!!! Collaboration tools

edited SoftwareDocumentation

email@hidden () — Thu, 04 Jan 2007 23:30:09 +0000

* XslTransformsWithOxygen
* XslTransformsWithJedit
* XslTransformsWithCommandLine
* XslTransformsWithSaxon
XSLTProc
* XslTransformsWithSaxon
!!! Collaboration tools

edited SoftwareDocumentation

email@hidden () — Thu, 04 Jan 2007 23:19:35 +0000

* XslTransformsWithOxygen
* XslTransformsWithJedit
* XslTransformsWithCommandLine
* XslTransformsWithSaxon
!!! Collaboration tools

edited FrontPage

email@hidden () — Thu, 04 Jan 2007 22:00:28 +0000

This site is meant for the collaborative authoring and reviewing of documentation on core EpiDoc concepts, tools, and recommendations. If you would like to edit this Wiki, please contact the %5Bhttp://lsv.uky.edu/archives/markup.html Markup list%5D with your request and you will be issued with the password.
!! Useful indexes to documentation, regardless of its "kind":
* HowTos (short, click-by-click tasks)
* %5BTutorials%5D (longer, thematic, hands-on explanations)
!! Kinds of documentation to be found herein:
* ToolDocumentation (tools created and/or maintained by the ~EpiDoc community)

edited EdrXwalkTodo

email@hidden () — Thu, 14 Dec 2006 16:57:52 +0000

* Turn vocabulary tables into VDEX files, and incorporate regularisation into XWalk (TE)
* EDR2KV.xml is mishandling temp_sched/temp_sched rather than /orig (TE)
* in EDR2KV.xml namespace "tei:" needs to be taken off of date (TE)
* EDR2KV.xml needs to create an imagines/orig with value "None." isf there are no fotos (TE)
* EDR2KV.xml hard-coded 'forced' values need to be replaced with scripted conversion: e.g. date, bibliography, ... (TE)
* **Fully document this process (GB, HC, TE)**

edited EdrXwalkTodo

email@hidden () — Thu, 14 Dec 2006 16:57:29 +0000

!! To Dos
* EDRKV2epidoc.xml needs /reg values instead of /orig **except** for ''vir_distrib'' (GB **DONE**)
* ~EpiDoc.dtd: add @cert to , placeName, geogName, etc. (GB)
* EDRKV2epidoc.xml needs /reg values instead of /orig **except** for ''vir_distrib'' (gb **DONE**)
* ~EpiDoc.dtd: add @cert to , placeName, geogName, etc. (gb **DONE**)
* the CHET-C component of the XWalker does not exist **at all** (HC)

edited EdrXwalkTodo

email@hidden () — Thu, 14 Dec 2006 16:45:20 +0000

!! To Dos
* EDRKV2epidoc.xml needs /reg values instead of /orig **except** for ''vir_distrib'' (GB **DONE**)
* ~EpiDoc.dtd: add @cert to , placeName, geogName, etc. (GB)
* the CHET-C component of the XWalker does not exist **at all** (HC)

edited GuidelinesReorganizationDec2006

email@hidden () — Wed, 06 Dec 2006 21:37:51 +0000

* Look again at EDR categories and the corresponding epidoc encodings now produced by the crosswalker tool
** ensure that all of these are treated conceptually (i.e., without close ties to EDR specifically)
** incorporate the EDR/crosswalk specifics into our discussion of conformance
!!! Fodder for intro to "Transcription and etc."
No time to do anthing useful with this now:
The fundamental act of an epigraphic publication is the presentation of the text.
EpiDoc offers the opportunity to tag at varying levels/depths. The minimal presentation may simply tag the text and being the text. The second level is to tag individual words in order to create a word index. A further, interpretative level is tagging principally of proper names (dates, titles, placenames and the like) to produce subject indices and faciliate searching. See further:

edited GuidelinesReorganizationDec2006

email@hidden () — Wed, 06 Dec 2006 21:31:10 +0000

** "Describing the Text, the Support and the Context" (describing.xml)
** "Interpretation: Analysis and Translation" (interpretation.xml)
** "Recording and reporting" (recording.xml)
* Renamed
* Saved a copy of "dates.xml" to "encodingdates.xml" and changed the include reference to it (which is still in the "Other Markup" section)
* Saved a copy of "namesandpersons.xml" as "taggingnamesandpersons.xml" since this is technical, TEI encoding guidance
The above xml files (with their ids, etc.) now exist; however, various subordinate sections have been added to them as xi:includes, but the files to be included thereby do not yet exist (in other words, the guidelines are now broken).
Do this under the broad rubrics outlined above (transcribing, describing, transciption and recording) and create/move/reorganize guidelines source files to support the full hierarchy.
Specific tasks include:
* Create stubs for the missing subsections that currently will break the webapp because there are xincludes for them that will fail to resolve to files
* Check comments in the newly created stub files for additional things that should be added
* Gut and rewrite as necessary all the various sections modified or introduced by this process
* Look again at EDR categories and the corresponding epidoc encodings now produced by the crosswalker tool
** ensure that all of these are treated conceptually (i.e., without close ties to EDR specifically)
** incorporate the EDR/crosswalk specifics into our discussion of conformance

edited GuidelinesReorganizationDec2006

email@hidden () — Wed, 06 Dec 2006 21:27:59 +0000

edited EdrXwalkTodo

email@hidden () — Wed, 06 Dec 2006 21:27:52 +0000

* EDRKV2epidoc.xml needs /reg values instead of /orig **except** for ''vir_distrib'' (GB)
* ~EpiDoc.dtd: add @cert to , placeName, geogName, etc. (GB)
* Turn vocabulary tables into VDEX files, and incorporate regularisation into XWalk (TE)

* the CHET-C component of the XWalker does not exist **at all** (HC)
* Turn vocabulary tables into VDEX files, and incorporate regularisation into XWalk (TE)
* EDR2KV.xml is mishandling temp_sched/temp_sched rather than /orig (TE)
* in EDR2KV.xml namespace "tei:" needs to be taken off of date (TE)
* EDR2KV.xml needs to create an imagines/orig with value "None." is there are no fotos (TE)
* EDR2KV.xml hard-coded 'forced' values need to be replaced with scripted conversion: e.g. date, bibliography, ... (TE)
* Fully document this process (GB, HC, TE)

* **Fully document this process (GB, HC, TE)**

added ControlledVocabularies

email@hidden () — Wed, 06 Dec 2006 21:24:40 +0000

! Controlled Vocabularies Used to provide standard values for descriptive categories, etc. Need to add discussion about: * the EDR categories * the google spreadsheets * and the vdex files we\'re developing Need to: * invite participation from the whole markup list * figure out how to handle this process so it doesn\'t get wildly out of control

edited EdrXwalkTodo

email@hidden () — Wed, 06 Dec 2006 21:24:25 +0000

!! To Dos
* EDRKV2epidoc.xml needs /reg values instead of /orig **except** for ''vir_distrib'' (GB)
** ~EpiDoc.dtd: add @cert to , placeName, geogName, etc. (GB)
* Turn vocabulary tables into VDEX files, and incorporate regularisation into XWalk (TE)
* the CHET-C component of the XWalker does not exist **at all** (HC)
* EDR2KV.xml is mishandling temp_sched/temp_sched rather than /orig (TE)
* in EDR2KV.xml namespace "tei:" needs to be taken off of date (TE)

edited GuidelinesDocumentation

email@hidden () — Wed, 06 Dec 2006 21:22:29 +0000

! ~EpiDoc Guidelines Documentation
* %5BGuidelinesReorganizationDec2006%5D
* ControlledVocabularies

edited ToolDocumentation

email@hidden () — Wed, 06 Dec 2006 21:22:06 +0000

* CrossWalker
* EpidocWebapp
* UsingTheStandardStyleSheets
* ControlledVocabularies

edited GuidelinesReorganizationDec2006

email@hidden () — Wed, 06 Dec 2006 21:21:20 +0000

Started, but did not finish, reorganizing the hierarchical structure of the guidelines. The goal is to break out of the constraints of following our individual typed to present things conceptually for an epigraphist audience. The business of "where does this tag belong?" is then subordinate to the larger conceptual tasks.
This reorganization was stimulated by a vigorous examination (still ongoing) of the descriptive categories and associated terminology used by the EDR project (see further: ControlledVocabularies). Concurrent work on the Crosswalker tool (specifically, its ability to import/export EDR data) was dependent upon (and advanced) this work.
!! Started but not finished
Specifically, we've:

edited GuidelinesReorganizationDec2006

email@hidden () — Wed, 06 Dec 2006 21:19:26 +0000

Started, but did not finish, reorganizing the hierarchical structure of the guidelines. The goal is to break out of the constraints of following our individual typed to present things conceptually for an epigraphist audience. The business of "where does this tag belong?" is then subordinate to the larger conceptual tasks.
This reorganization was stimulated by a vigorous examination (still ongoing) of the descriptive categories and associated terminology used by the EDR project (see further: ControlledVocabularies).
!! Started but not finished
Specifically, we've:
* Renamed "Tagging the Text" (taggingtext.xml) as "Transcribing and Editing the Text"

edited FrontPage

email@hidden () — Wed, 06 Dec 2006 21:18:52 +0000

* SoftwareDocumentation (help setting up/using common XML tools etc.)
* %5B* RoadMap%5D (Planning the future of ~EpiDoc development)

edited FrontPage

email@hidden () — Wed, 06 Dec 2006 21:18:42 +0000

* SoftwareDocumentation (help setting up/using common XML tools etc.)
* %5BRoadMap* %5BRoadMap|Planning the ~EpiDoc Roadmap%5D
* %5BRoadMap%5D (Planning the future of ~EpiDoc development)

edited FrontPage

email@hidden () — Wed, 06 Dec 2006 21:18:24 +0000

* CommunityDocumentation (~EpiDoc community protocols and collaborations)
* SoftwareDocumentation (help setting up/using common XML tools etc.)
* %5BRoadMap|Planning the ~EpiDoc Roadmap%5D

edited FrontPage

email@hidden () — Wed, 06 Dec 2006 21:16:12 +0000

! ~EpiDocumentation Wiki
This site is meant for the collaborative authoring and reviewing of documentation on core %5Bhttp://epidoc.sf.net EpiDoc%5D concepts, tools, and recommendations. If you would like to edit this Wiki, please contact the %5Bhttp://lsv.uky.edu/archives/markup.html Markup list%5D with your request and you will be issued with the password.
!! Kinds of documentation to be found herein:

added EpiDoc

email@hidden () — Wed, 06 Dec 2006 21:15:47 +0000

! ~EpiDoc references * ~EpiDoc Web page http://epidoc.sourceforge.net * ~EpiDoc Guidelines http://www.stoa.org/projects/epidoc/stable/guidelines/ * ~EpiDoc ~SourceForge repository http://sourceforge.net/projects/epidoc

edited GuidelinesDocumentation

email@hidden () — Wed, 06 Dec 2006 21:14:47 +0000

! ! ~EpiDoc Guidelines Documentation
* %5BGuidelinesReorganizationDec2006%5D