Difference between revisions of "Guidelines for adding Bibliography entries"

From Cybersecurity Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
<last name>_F[M]:<year>
 
<last name>_F[M]:<year>
  
Where <last name> is the primary author's last name, F = first initial and M is an optional middle initial.  If there are  more than one reference in a year, subsequent ones are labeled with the date plus a sequence letter, e.g, Duncan_M:2009; Duncan_M:2009A, etc.
+
Where <last name> is the primary author's last name, F = first initial and M is an optional middle initial.  If there are  more than one reference in a year, subsequent ones are labeled with the date plus a sequence letter.  (e.g, Duncan_M:2009; Duncan_M:2009A, etc.)
  
 
If two authors use <last name 1>_<last name 2>:<year>  (e.g., Thomas_Martin:2006).
 
If two authors use <last name 1>_<last name 2>:<year>  (e.g., Thomas_Martin:2006).
Line 16: Line 16:
 
If more than two authors use <last name 1>_et_al:<year>  (e.g., Schmitt_et_al:2004).
 
If more than two authors use <last name 1>_et_al:<year>  (e.g., Schmitt_et_al:2004).
  
For institutional authors use initials (i.e. DOD:2009 = Department of Defense 2009 article)
+
For institutional authors use initials (e.g., DOD:2009 = Department of Defense 2009 article)
  
 
==Journal Names==
 
==Journal Names==

Revision as of 18:27, 28 May 2010

The available types of BibTeX entries and fields are documented at http://en.wikipedia.org/wiki/BibTeX.

Naming Convention for Entries

Do not use BibTeX's automatic "*" entry naming.

The naming convention we are using for entries is:

<last name>_F[M]:<year>

Where <last name> is the primary author's last name, F = first initial and M is an optional middle initial. If there are more than one reference in a year, subsequent ones are labeled with the date plus a sequence letter. (e.g, Duncan_M:2009; Duncan_M:2009A, etc.)

If two authors use <last name 1>_<last name 2>:<year> (e.g., Thomas_Martin:2006).

If more than two authors use <last name 1>_et_al:<year> (e.g., Schmitt_et_al:2004).

For institutional authors use initials (e.g., DOD:2009 = Department of Defense 2009 article)

Journal Names

Journal names should not be abbreviated in BibTeX. However, the full citation in individual references should conform to Bluebook standards, including abbreviations.

Links to Articles and References

Where possible include a url = entry pointing to a location where the reference may be found. If a second location is available use the alturl = key. Chose the location most likely to be persistent over time for the url = key. IF an SSRN entry is available use the SSRN = key.

Reference Types (with Examples)

The primary article types used in the Cybersecurity Wiki are:

article

An article from a journal or magazine. Required fields: author, title, journal, year Optional fields: volume, number, pages, month, note, key

 @Article{Hollis_DB:2007,
   author       = {Duncan B. Hollis},
   title        = {Why States Need an International Law For
                  Information Operations},
   journal      = {Lewis \& Clark L. Rev.},
   volume       = {11},
   year         = {2007},
   pages        = {1023},
   url          = {http://legacy.lclark.edu/org/lclr/objects/
                LCB\_11\_4\_Art7\_Hollis.pdf},
   ssrn         = {http://ssrn.com/paper=1083889},
   keywords     = {cyberwar cyberterror information operations IO
                  information warfare jus ad bellum jus in bello
                  international humanitarian law use of force
                  civilian distinction perfidy complexity
                  regulatory design international law estonia
                  denial of service attack hactivists computer
                  network attack},
   bibdate      = {2010-05-19},
 }

book

A book with an explicit publisher. Required fields: author/editor, title, publisher, year Optional fields: volume, series, address, edition, month, note, key

conference

An article in a conference proceedings. (The same as inproceedings.) Required fields: author, title, booktitle, year Optional fields: editor, pages, organization, publisher, address, month, note, key

 @Conference{Schmitt_et_al:2004,
   author       = {Michael N. Schmitt and Heather A. Harrison and
                  Thomas C. Wingfield},
   title        = {Computers and War},
   titleaddon   = {The Legal Battlespace},
   howpublished = {Online paper},
   publisher    = {Harvard University},
   organization = {Program on Humanitarian Policy and Conflict
                  Research},
   booktitle    = {Informal High-Level Expert Meeting on Current
                  Challenges to International Humanitarian Law},
   url          = {http://www.ihlresearch.org/ihl/pdfs/
                schmittetal.pdf},
   urldate      = {2010-05-19},
   month        = {6},
   year         = {2004},
   keywords     = {},
   bibdate      = {2010-05-19},
 }

proceedings

The proceedings of a conference. Required fields: title, year Optional fields: editor, publisher, organization, address, month, note, key

techreport

A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year Optional fields: type, number, address, month, note, key

unpublished

A document having an author and title, but not formally published. Required fields: author, title, note Optional fields: month, year, key

misc

For use when nothing else fits. Required fields: none Optional fields: author, title, howpublished, month, year, note, key

 @Misc{DOD_OGC:1999,
   author       = {Department of Defense Office of General Counsel},
   title        = {An Assessment of International Legal Issues in
                  Information Operations},
   howpublished = {Online paper},
   publisher    = {U.S. Government},
   url          = {http://www.au.af.mil/au/awc/awcgate/dod-io-legal/
                  dod-io-legal.pdf},
   urldate      = {2010-05-18},
   year         = {1999},
   note         = {Principal Author: Phillip A. Johnson},
   keywords     = {Law Espionage Treaties Government
                  International-Law Global Communities Agreements
                  United-Nations Legislation
                  International-Relations Law-Enforcement},
   bibdate      = {2010-05-18},
 }