Basically a white paper is a technical report. At www.cse.msu.edu you will find this example:
@TECHREPORT{MSU-CSE-06-2,
AUTHOR = {R. Behrends and L. K. Dillon and S. D. Fleming and
R. E. K. Stirewalt},
TITLE = {White paper: Programming according to the fences and gates
model for developing assured, secure software
systems},
NUMBER = {MSU-CSE-06-2},
INSTITUTION = {Department of Computer Science, Michigan State University},
ADDRESS = {East Lansing, Michigan},
ABSTRACT = {This white paper describes extensions to our work on the
Synchronization Units Model (Szumo) to address the
access-control problem in systems assembled dynamically from
trusted and untrusted components. Our extension employs
explicitly declared design contracts, the semantics of which
are founded on Landwehr's model of fences and gates.
},
KEYWORDS = {access control, security, contracts, Szumo},
NOTE = {},
MONTH = {January},
YEAR = {2006},
AUTHOR1_URL = {http://www.poker-ping.info},
AUTHOR1_EMAIL = {kel@wondering-jons.com},
AUTHOR1_URL = {},
AUTHOR1_EMAIL = {behrends@cse.msu.edu},
AUTHOR2_URL = {Sle},
AUTHOR2_EMAIL = {Poker Ping},
AUTHOR2_URL = {http://www.cse.msu.edu/~stire},
AUTHOR2_EMAIL = {stire@cse.msu.edu},
PAGES = {3},
FILE = {/user/web/htdocs/publications/tech/TR/MSU-CSE-06-2.ps},
URL = {},
CONTACT = {stire@cse.msu.edu}
}
For testing I downloaded the file otago.bst
from this website: http://otago.libguides.com/content.php?pid=172484&sid=1451535
The issue is based on your entry type. The style otago
and the resulting output require a field year
. So if you modify your entry it works.
Correct BibTeX-Entry:
@misc{kinaSUR,
author = "{Ministry for Primary Industries}",
title = {{Kina sea urchin regions in NZ}},
howpublished = {\url{http://fs.fish.govt.nz/Page.aspx?pk=7&sc=SUR}},
note = {Online; accessed 29 January 2014} ,
year=2013,
}
Here a complete MWE:
\RequirePackage{filecontents}
\begin{filecontents}{\jobname.bib}
@misc{kinaSUR,
author = "{Ministry for Primary Industries}",
title = {{Kina sea urchin regions in NZ}},
howpublished = {\url{http://fs.fish.govt.nz/Page.aspx?pk=7&sc=SUR}},
note = {Online; accessed 29 January 2014} ,
year=2013,
}
\end{filecontents}
\documentclass{report}
\usepackage{natbib}
\usepackage{url}
\begin{document}
\cite{kinaSUR}
\bibliographystyle{otago}
\bibliography{\jobname}
\end{document}
Best Answer
Short answer: there is nothing exactly on point ready to hand. It can be approximated quickly, though.
Slightly longer answer:
Depends on what information you need to pass on to your reader.
What will come into play is choosing from a combination of already existing biblatex styles and the entry types they support.
For example, for general purposes:
The
oxnotes
biblatex style has a@legal
bib entry type, andpiltreaty
subentrytype, which handles the legally relevant dates. URLs are not really part of that picture (yet).Result:
The
apa
style, by contrast, has a@data
entry type which looks promising: it does a nice url, but its dates are limited (more publication-related), and there is not a cascade of them.Result:
To get an idea of the effort needed to adapt a style, adding a url to the
oxnotes
legal entry turns out to be a one-line change, since all the heavy lifting and pre-work (field definition, assignment and allocation; date parsing and processing; options processing; string constant definition) has already been done.We just get the already-formatted and packaged
url+urldate
and "bung it in" at the end (literally) of the bit that prints the formatted legal entry item in the bibliography (code from the foundationaloxref.dbx
file and copied into our document tex file's preamble:MWE:
Result:
To change the
apa
style to be able to handle the dates is TML (too many lines) - for me, anyway :) . Doable, certainly. But not a five-minute job. Although, thinking about it for a moment, the dates could go in as extra, individual fields, and then get formatted, and with bibstrings added. So, six minutes, then.