<?xml version="1.0" encoding="UTF-8"?>
<!-- DOCTYPE header SYSTEM "file:/C:/Projects/DHQuarterly/Schemas/beta/header-draft.dtd" -->
<?oxygen RNGSchema="header-draft.rng" type="regular"?>
<DHQheader xmlns="http://digitalhumanities.org/DHQ/namespace">
  <title>Markup and its Discontents</title>
  <subtitle>Or, one character after another</subtitle>
  <author>
    <name>Julia <family>Flanders</family></name>
    <!--
      This should be enough for us, and is lightweight

      Note MODS uses a namePart+ structure, where
      namePart types include: family, given, date, termOfAddress
      but what about name suffixes (Jr, III)? and whatever other
      imaginative uses people make of their names?
      
      So, mapping name to MODS:

      <xsl:template match="authorInfo/author/name/text()">
        <namePart>
          <xsl:value-of select="normalize-space()"/>
        </namePart>
      </xsl:template>
      
      <xsl:template match="authorInfo/author/name/family">
        <namePart type="family">
          <xsl:value-of select="normalize-space()"/>
        </namePart>
      </xsl:template>
      
      results in
        <name>
          <namePart>Julia</namePart>
          <namePart type="family">Flanders</namePart>
        </name>
      
      mapping name to DC:

      <xsl:template match="authorInfo/author/name">
        <dc:creator>
          <xsl:value-of select="normalize-space()"/>
        </dc:creator>
      </xsl:template>
      
      results in <dc:creator>Julia Flanders</dc:creator>
    -->
    <affiliation>Women Writer's Project</affiliation>
    <affiliation>Brown University</affiliation>
    <address>
      <addrLine>Providence, RI</addrLine>
      <addrLine>USA</addrLine>
    </address>
  </author>
  <author>
    <name>Wendell <family>Piez</family></name>
    <affiliation>Mulberry Technologies, Inc.</affiliation>
    <email>wapiez@mulberrytech.com</email>
  </author>
  <langUsage>
    <!-- Q: what spec for language codes? -->
    <language id="en" role="primary"/>
    <language id="la" role="secondary"/>
  </langUsage>
  <keywords resp="author" scheme="scheme">
    <!-- other keyword resp and scheme values are allowed?
      resp is required, scheme are optional -->
    <term>markup</term>
    <term>TEI</term>
    <term>ontology</term>
  </keywords>
  <history>
    <!-- all these can map to TEI revisionDesc -->
    <submission>
      <date value="2005-10-01">October 1 2005</date>
      <idno type="intakeID">keys this submission to tracking db</idno>
    </submission>
    <revisionDesc>
      <change>
        <date value="2005-10-04">October 5 2005</date>
        <respStmt>
          <name>Wendell Piez</name>
        </respStmt>
        <item>bunch more stuff, including more rearrangement and renaming</item>
      </change>
      <change>
        <date value="2005-10-02">October 2 2005</date>
        <respStmt>
          <name>Wendell Piez</name>
        </respStmt>
        <item>added wrappers, cleaned up, changed a couple of names, added
          comments ... should we support markup of tag structures here?</item>
      </change>
    </revisionDesc>
    <assignment>
      <!-- multiple assignments can be used for peer review, editorial attention
        or revision, translation or whatever the ME wants to track (though mostly 
        the DB should be used for this) -->
      <!-- content model for assignment and submission is date?, idno*, item*) -->
      <idno type="blindID">blind ID assigned for peer review</idno>
      <!-- a permanent DHQid can be assigned when a work is published -->

    <!-- assignment has a multitude of uses, including tracking 
      DHQ process metadata:
        section to which an article is submitted or assigned
          (articles, editorials, reviews)
        submission attachments (ancillary file)
        if this is just a metadata stub, not DHQauthor data
          submission itself (ancillary file)
          format of submission
      
      Note the tradeoff here: anything can be tracked by the db, but to the
      extent it's here it will be transparently available in our CMS
      (look at a stub and you'll see everything you need to know about it)
    -->
    </assignment>

  </history>
  <!-- publicationStmt etc will go here later (in DHQpublish schema)
      TEI model for publicationStmt:
        (publisher | distributor | authority | pubPlace | address | idno 
         | availability | date ) -->
  <availability>
    <!-- also available alternative versions, such as translations, might be
      made known here -->
    <!-- HTML for Creative Commons License -->
    <!-- 
      <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/2.5/">
        <img alt="Creative Commons License" border="0" 
           src="http://creativecommons.org/images/public/somerights20.gif" />
      </a>
      <br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/2.5/">Creative Commons Attribution-NonCommercial-NoDerivs 2.5 License</a>.
    -->
    <!-- /Creative Commons License -->
    <!-- Creative Commonds code -->
    <cc:License xmlns:cc="http://web.resource.org/cc/"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      rdf:about="http://creativecommons.org/licenses/by-nc-nd/2.5/"/>
  </availability>
  <respondsTo>
    <!-- optional - btw where would such a thing go in a TEIheader? -->
    <idno type="DOI">DOI, DHQid, ISBN or other identifier of article to which
      this one relates or responds</idno>
    <bibl>A bibl, perhaps scraped from any bibl[@type="reviewTarget"] appearing
      in the doc</bibl>
  </respondsTo>
  <!-- to be added for DHQpublish:
    dublinCore? (a Dublin Core profile
      extracted from the rest of the header)
    also, some Dublin Core and MODS can be reported directly by XSLT, such
    as number of figures, appendixes, even a rough word count or more exact 
    character count? plus also ToCs, keywords extracted from any cases of
    bibl[@type=reviewTarget] or other special indicators in the text -->
  <abstract>
    <!-- in MODS, an abstract is unstructured; but we want to allow
      multiple paragraphs, verse etc in abstracts don't we? -->
    <p>A synopsis of the article's argument or findings</p>
  </abstract>
  <teaser>A short (one or two-sentence) blurb for catalogs and article listings,
    to entice the reader.</teaser>
</DHQheader>