NB MANY OF THESE ARE ONLY COPIED FROM LLC's GUIDELINES, AND DO NOT YET APPLY!!!

Overview

This document describes the policies and guidelines for submitting articles and other materials to DHQ.

Rights, rules and relationships:

The author of any work published by DHQ grants to DHQ a perpetual, non-exclusive right to publish the work under a Creative Commons license with the following provisions:

• anyone may copy, display, and distribute the work for non-commercial purposes, as long as they credit the source appropriately; for commercial reuse, explicit permission is required
• the work may not be redistributed in modified form (except by the author)

A detailed version of the license and an explanation of its terms are available here? .

Types of submission

There are three distinctive types of contribution to DHQ. They will be coordinated through the Call for Submissions? page, which prospective authors should review carefully in order to understand which slot or slots within the DHQ framework a work of theirs will fit within. Authors may also want to review the FrameWorkNotes document, in order to acquire an understanding of the background and rationale for DHQ's dividing works into these categories.

The categories are:

• "traditional" journal content including papers documenting research results, reviews, essays and editorials
• non-traditional content, including digital art, that DHQ will undertake to mount and maintain on our servers and to archive for future access and possible reissue or re-publication
• non-traditional content that DHQ will publish, but will not undertake to maintain

These categories correspond roughly to Zones I-III as described in FrameWorkNotes.

Accordingly, outlined here are guidelines pointing authors to two alternative means of submission to DHQ: (1) a channel in DHQ's XML format, and (2) an "open channel" in any format. Our efforts to accommodate this range are intended to reflect our interest in pushing the boundaries of digital electronic media (and therefore, on occasion, finding ways to publish arbitary digital electronic formats or artifacts of digital processing), while continuing to perform a journal's traditional roles of finding and presenting a selection of the best and most interesting works available, and assuring their availability over a long term. All works published in DHQ will be provided with DHQ-compatible metadata for cataloging and long-term access. Where possible, works published in DHQ will also be converted entirely to DHQ markup; that, however, is not a sine qua non for publication in DHQ. Accordingly, any efforts that authors put in to help their piece along (perhaps by submitting in the DHQauthor XML format, or helping with conversion into it) will speed a paper's transition to publication. Yet authors are encouraged to submit in any appropriate medium, and DHQ's structure is designed to accommodate experimentation and variation in form as well as content.

Submissions in DHQ's own DHauthor format (or easily and rapidly converted into it) can be expected to appear in DHQ sooner than those submitted in arbitrary formats (especially proprietary ones that pose challenges for conversion). Generally, DHQuarterly articles will be made available on line immediately, as soon as they are accepted and any necessary editorial/conversion work on them is concluded. Note, however, that submission of articles in DHauthor format is not a guarantee that it will be selected for publication by DHQ.

Quarterly announcements will inform the research community and interested public of works being made available on DHQ.

Authors can expect that all works selected for publication to DHQ will have been peer reviewed.

See the DHquarterly WebHome to check on status towards a Call for Submissions? .

Schemas and stylesheets for the DHQauthor format will be available shortly at Download Central; for now see our development pages at Schema Requirements and Technical Specs.

General

[draft] Submission of a manuscript will be held to imply that it contains unpublished original material and that it is not being considered for publication elsewhere. [LLC rule: Contributions should not normally exceed 6,000 words in length.]

Proofs

As we are currently in development of the publishing infrastructure, turnaround time for proofs will vary. We reserve the right to dictate the formats exchanged in the proofing process (in case we need to undertake any upconversion on your behalf), while promising to do everything possible to accommodate authors' needs to work in familiar formats. Long-term, authors may benefit from a "galley proof" presentation of the DHauthor format.

Offprints

DHQ being a freely-accessible resource on the Internet, the question of offprints should not generally arise. Should authors' works be printed or redistributed in any restricted form or limited edition, all efforts will be made to provide authors with copies, offprints or their equivalent such as access rights.

Copyright

We are currently working out copyright issues, so ask an editor if this text has not been rewritten. Eventually we should have a Copyright Issues? page. We may ask to be mentioned should you choose to redistribute your work further.

Document Format

Authors submitting in XML: see the Download Central page to start looking for what you need.

Authors submitting in application formats, such as TeX, Word or WordPerfect formats (RTF would probably be preferred), PDF etc., might consider the LLC Guidelines for typescript format in addition to the below.

We also expect to provide usage models of articles in DHQ to show the relation between document tagging, rendition and functionality. More generally, and even if you don't submit in XML, you may be able to emulate the DHQ format by simply examining current issues of DHQ.

Naturally we expect to have full contact information from you should we decide to accept your paper, so as to negotiate document formats in sticky cases.

Submission

See the Call for Papers if you want to learn about how to submit.

[draft] Call for Papers will include instructions on

• providing metadata including a document abstract
• submission process
• format
• tools
• Documentation available on the DHauthor Schema?

Typescript

(NB: if the Call for Papers does not address how to submit a paper not in DHQ ML (that is, in the format of your choice), please ask. Many of these features will be supported transparently in DHQauthor, another reason to try it.)

[These rules are largely cribbed from LLC, and should be updated!]

We are not stipulating any rules regarding how to format paragraphs, headings, section numbering, or even bibliographic format, although our aim will be to reward contributors who give us XML by giving them their own access (through the tagging) to our controls of such features. (This is in addition to being able to prioritize such articles for publication.) Authors should expect, however, that idiosyncratic use of headers, renditional formatting, notes or bibliography will be normalized if an article is accepted for Zone I.

Spelling: Use the system which you are most accustomed to using, but be consistent. [LLC rule: British authors, please use Oxford (-ize) spellings. When in doubt, refer to the Concise Oxford Dictionary, or the Oxford Dictionary for Writer and Editors.]

Italics, bold, quotation or code insets: observe any consistent and clear usage, while keeping in mind that these are exactly the features that the DHQ format is intended to rationalize. If you find yourself experimenting with formal or renditional features of the text, consult us as to the feasibility of your aproach in DHQ ML -- remember, we intend specifically to accommodate experimental approaches in addition to more conventional and "naturalized" DHQ ML.

Punctuation [LLC rule]: Initials should be followed by a full point and a space, e.g. E. M. Forster, W. H. Auden. There is no full point after Dr, Mrs, Ms, or Mr.

We expect to provide semantic markup for code types (especially when discussing markup), technical terms, names and so forth; please explore the DHauthor Schema? and related tools (at Download Central to learn more.

Electronic mail addresses: Addresses should appear in lowercase only. Alert us if you have any external links to email or the web in your pages.

Miscellaneous points of style [from LLC]: & should be written out as 'and', and use a % sign for 5%, 25%, etc. No apostrophe in 1920s, 1950s, etc. Decimal point should be on the line: 5.2, 3.9, etc. et al. should be in italic. e.g. and i.e. are never capitalized even at the beginning of a sentence. There should be no comma after e.g. or i.e. Numbers below 100 and vaguely expressed numbers should be spelt out. Precise numbers, units of measurement, and numbers above 100 should be in figures. NB the use of the 'Oxford comma' in the previous sentence (comma before 'and' in lists). Please do likewise.

Cross-references in the text should be as follows (but note we will be autogenerating these): see Section 2.5 see Appendix 1 see Figure 1

We will support cross-referencing the following: sections (div), figures, examples (which may have labels and captions) including code examples, tables, bibliographic listings, inset texts (xtext) and appendices. Cross-references will be normalized, but may reference by title or label as well as by number. Expect numbering to be auto-generated from implicit links in document source code, so get your cross-references right

Do not abbreviate "sec." for Section, "fig." for Figure etc.

Figures (illustrations, artwork, tables): [draft] we will accept figures in any of a number of web-ready formats, including PNG, JPG, GIF, PDF and SVG.

Whenever possible we would like versions of figures and illustrations suitable for reproduction in print as well as on screen. If we have hi-res copies, so much the better.

Note that in particular special instances we may be able to accept illustrations in non-digital form, for digital conversion; but much of this will put a work into Zone II.

Tables: We would likely accept clear tables in a range of formats to be negotiated. Some papers may be published with data sets attached.

Note that according to the DHQauthor document model, certain elements such as tables, figures (which can include graphs and graphics), and examples, can appear either in and out of line. Please indicate whether such an element may float or not. Be as clear as possible indicating both the preferred location of one of these elements in the text, and whether they may "float". (Note that editorial discretion with respect to such matters may be applied in any case.)

Figures and examples may have captions, which should have the first word capitalized; references by head to a figure, table or example (e.g. "Table 1" in "*Table 1* Proper nouns and syntactic organization") will be generated for you, so feel free to use these constructs.

Do not type a label or caption on a graphic, but label it in a figure. To ensure correct matching up of tables/figures to captions, put table/figure number on the back of the artwork, and author's name.

[LLC material to be redrafted follows] The Order of Items After the Main Text will be:

Notes References Appendices Notes

If you are submitting in DHauthor format, notes and full bibliographic references may be encoded in line (where they are cited), with extraction and formatting of notes and references at the end of the document handled by a stylesheet.

In general, notes should not consist simply of a bibliographic reference, which can be made in running prose without having to be wrapped in a note.

If submitting not in DHauthor format, all notes should be gathered together at the end of the article. Notes should be numbered consecutively throughout the text, with numbers inserted above the line, e.g. ¹. They should be listed in numerical order at the end of the main text:

1. Smith, T . . . 2. These results . . .

References and Bibliography: Please use the version of the Harvard system described below. References should be cited in the text using the author's name and year of publication, e.g. (Bloggs, 1990; Bloggs et al., 1991). (Again, authors using DHauthor will find guidance on these issues in the DHauthor Schema? documentation.)

If not submitting in DHauthor, the list of references should be headed References and placed at the end of the article. The list should be in alphabetical order by reference label (the citation string). Where an author has more than one publication, they should be arranged in chronological order, and if there is more than one publication within a year, they should be alphabetically ordered by title and labelled a, b, etc. (e.g. 1989A, 1989b). Note that reference labels may contain spaces (e.g. [Sperberg-McQueen 1995]). Single-author works precede co-authored works. Please follow the examples given below for bibliographic layout.

NB These have been tweaked slightly, and no longer conform exactly to LLC usage - is the format below okay? (and which 'standard' is it compatible with?)

[Biber 1988] Biber, D. Variation Across Speech and Writing. Cambridge University Press, Cambridge. (1989).

[Calzolari 1989] Calzolari, N. A Typology of English Texts, Linguistics, 27: 3-43.

[Computer-Aided Lexicography 1989] “Computer-Aided Lexicography: Dictionaries and Word Databases”. In I. S. Batori, W. Lenders, and W. Putschke (eds), Computational Linguistics, Berlin (1989), pp. 510-19.

[Ellis 1987] Ellis, D. The Derivation of a Behavioural Model for Information Retrieval Design. Ph.D. thesis, University of Sheffield (1987).

[Halliday 1985] Halliday, M. A. K. An Introduction to Functional Grammar. Edward Arnold, London (1985).

[Oostdijk 1988] Oostdijk, N. “A Corpus Linguistic Approach to Linguistic Variation”, Literary and Linguistic Computing, 3 (1988): 12-25.

[Richardson 1988] Richardson, S. D. and Braden-Harder, L. “The Experience of Developing a Large-Scale Natural Language Text Processing System” CRITIQUE: Proceedings of the Second Conference on Applied Natural Language Processing, Austin, Texas, February 1988.

[Wallraff 1988] Wallraff, B. “The Literate Computer”, The Atlantic Monthly, 261.1 (1988): 64-71.

-- JuliaFlanders - 20 Sep 2005