DHQ Wiki | Policy Documents | Journal Development

Technical Specs

Issues and Suggestions for XML Core Model

Usage

• related to <bibl>
  • What is the purpose of <label> in this context? It's required, but I don't see why I'd want to use it. KimTryka?
    • The label is what will appear in display as the "referencing string", as in "[Piez 2005]" (brackets or parens provided by the stylesheet) if referencing a paper by me, and along with that paper's listing in the bibliography. IME it is good to have this string kept distinct from the @id, which is often dragged into service for this. WendellPiez
    • I wonder whether encoding this as a label= attribute on <bibl> would be a reasonable thing to do? I realize this is a trivial change--so why would it matter? but it feels less odd than putting this into content. This suggestion is premised on the notion that the problem is one of author understanding, rather than actual function. JuliaFlanders
    • The primary reason this is modeled as an element (with a constrained position) is out of an analogy to the way is used elsewhere, for example in list items. So I see a possible point of confusion either way. is actually optional when the bibl has @type="reviewTarget". That does not, however, address your usability issue. If an attribute, is it required? WendellPiez
  • We need <editor> as choice under <bibl> KimTryka?
    • Okay. WendellPiez
  • Do we need a tag for pages (for giving the total pagination or for citing a piece in a larger work)? Or is it assumed that this type of information will float in mixed content? Maybe this needs to be something like an <extent> tag - could hold the number of dvds, amount of time of a performance, etc. KimTryka?
    • I like the idea of . WendellPiez
    • I still like the mixed content model for its flexibility, but would like a structured display when the data is sufficiently structured to support it. (It's trying to structure it when it ain't, is what is hard.) WendellPiez
  • should there be a place for ISBN and price for published monographs? KimTryka?
    • Hm, what would this be under TEI? We could add them. Let's use an <idno> as in the header (which can serve for any ISBN, DOI or other), plus <price>. Is okay? WendellPiez
    • Can we provide a rationale for the <price> element? Is price ever included in standard citations? JuliaFlanders
    • A quick look around (New York Review of Books, NYT Book Review, Science, New Scientist, First Monday, American Archivist, Journal of the Society of Archivists) says, 'yes' to price! Though it won't always be needed. (actually, I got the idea when looking at reviews in various publications KimTryka?
    • Ah! sorry--I was being an "articles" bigot. Of course you need price in a review. Apologies for being dense!! JuliaFlanders
    • They do get included in standard citations of works under review. (A link to a book dealer might do as well however! WendellPiez

• related to <div>
  • I think that <div>s need attributes beyond 'id' -- I'd definitely like at least 'type'. KimTryka?
    • Okay. (But you're not suggesting any special magic for these types yet are you? WendellPiez
  • What is <xtext> (under <div>)? I don't see a similar tag in TEI so I can't come up with an analogy. KimTryka?
    • xtext is like a div only even looser, when you want entire external texts embedded. We don't expect for it to be used much. (Mostly <quote> should do the job.) Mostly it included since it's easy to model and occasionally useful -- and since it's so free form we can constrain div in a TEIish way (which is preferable when we can get it). WendellPiez
    • I would perhaps gloss this by suggesting that xtext is like div only looser--see the TEI-L strand on floating divs for the background on this. In other words, the idea of xtext is not based on the idea ofsubdivision (<div>), but on the idea of wholeness (<text>). Except that it omits some of the things that make the <text> element a high-level element. JuliaFlanders
  • I think I'm using in an unexpected way, not to create a list of citations, but within