Keks Dose makes the good point in the comments that not only do the legal systems differ from country to country so do their citation practices.

The styles listed below come mainly from an English/American common law perspective.

Styles with support for legal citations

A handful of biblatex styles have some kind of support for legal citations with @jurisdiction and @legislation (I only listed styles that I consider to be of recent vintage, i.e. updated after the release of biblatex v3.3 in 2016)

• 
  biblatex-abnt aliases both to @article.


• 
  biblatex-bath has support for UK legislation and parliamentary reports (@legislation) as well as EU legislation and reports (as @legislation) and case reports (@jurisdiction). See §§4.8-4.10 of the documentation.


• 
  biblatex-chicago offers the types @jurisdiction, @legal and @legislation following CMS/Bluebook recommendations.


• 
  

  biblatex-oxref (by the author of biblatex-bath) also offers support for legal sources mimicking OSCOLA with a few minor differences. See §10 Legal references of the style documentations (here oxyear) For the author-year style oxyear the author notes

  
  
  

  
  

  Since legal references are usually cited using footnotes, how oxyear should behave is not well defined. As a result, I have not configured it to do anything fancy: the full reference will be formatted just the same as with oxnotes, and citations will typically be title–year using parentheses in the usual way.

  
  

  
  



• biblatex-philosophy has experimental support for @jurisdiction.



• 
  oscola has support for much of the English-speaking world.

biblatex-bath, biblatex-oxref's oxyear style and biblatex-chicago's authordate will be of particular interest since those styles usually follow an autho-year scheme and are otherwise not focused on legal citations.

As far as I can see biblatex-bath and biblatex-oxref can get away with not modifying the citation commands significantly (a few delimiters are modified but the cite bibmacro itself not), biblatex-chicago has has dedicated macros set up for legal citations. All styles have dedicated drivers and supporting infrastructure for the accepted entry types.

There were also dedicated styles for German legal citations, Swiss legal style and French legal citations, but these styles have not been updated recently and will probably not work as intended any more. A more recent French style is https://github.com/ienissei/frenchlaw

Write your own legal references

Depending on the output you expect and the input you find reasonable the work you may have to do can vary.

Bibliography

I think it is fair to assume that you will have to write a dedicated bibliography driver for @legislation and @jurisdiction. Mapping to a standard driver like @article, @misc or @book is probably not enough for you.
The general approach to writing a bibliography driver as shown in Creating Entry in Bibtex for Executive Orders and How can I create entirely new data types with BibLaTeX/Biber? is still valid. I would definitely prefer bibstrings over hard-coded text in macros and would usually try to avoid printtext and try to use DeclareFieldFormat as much as possible (but I guess to some extent that is just a matter of taste). As we are all painfully aware there are no comprehensive "introduction to writing a biblatex style" or "my first bibdriver" available (yet?), so I would usually recommend to learn by looking at examples. Naturally you would start with the standard drivers, but I believe most of the styles listed above can also be used to learn best practices - if you keep in mind that some of them need to implement a complicated set of rules and so some tricks are required once in a while.

You may also have to add certain fields to the default data model if you feel that the available fields don't cover everything you need. (biblatex-oxref adds a few non-standard fields for case reporting for example.) See Add field "tome" to biblatex entries.

With a bit of care those two things can happen almost independent of the style that is later used.

Citation

For citations the situation is not as clear.

As biblatex-oxref and biblatex-bath demonstrate it might not actually be necessary to modify the cite macros, it can be enough to use existing features like labeltitle, labeldate and a few modifications of their behaviour to obtain acceptable citation output. But depending on the rest of your style and your input it may be necessary to change the cite macro to incorporate legal citations. This gets harder to pull off in a way that is independent of the used citation style. If you use a complicated style such as authoryear-icomp some care needs to be taken to make sure legal citations interact with the various features of the style in a reasonable way.

A dedicated lawcite command might be an option that avoids messing with heavily style-dependent citation commands, but it does not feel as nice to me.

I cannot really say much about best practices on the matter, and neither on
legal sources in particular. So I guess technically I shouldn’t be
answering. But I do think I have some input that might be of interest. However, I intend to tackle the question from a somewhat specific perspective: Sharing my thoughts on how to handle non-regular entry types with biblatex, of which legal sources can be considered a particular case.

My own relation to the problem comes from the need to cite/reference primary
sources for Economic History research, which means mostly archive sources but may actually be quite diverse stuff. This includes legal sources, but I never really worried much about specific requirements of this type of source. I mention this because some of my choices here do stem from the requirements implied by this, but I do think most of the suggestions bellow are quite flexible (Indeed, "flexibility" is one of my key requirements, for I usually cannot predict in advance the required style for submission of any given work when I start it).

There is always a range of alternatives to deal with less than standard types of sources. moewe covers this very well in his
answer, so there is no need for me to reiterate. But a comment on a natural choice may be worth it. Indeed, one of the obvious ways would be to choose a style that handles the particular type of source that we need. My view is that, unless there is a general reason to go for a specialized or heavily customized style, I feel it to be too much to choose it just to support a particular entry type we need. I prefer to stick to my style of choice (usually one of the standard ones), which provides me well with the desired results for regular entry types and layer on top of it the necessary structure to deal with the non regular ones. Normally regular entry types will comprise a large share of the sources anyway, so why change everything, for all entry types, just to be able to handle one or another kind of special source?

Given this, in the most general case, handling non-standard entry type entails three basic issues:

• Providing the data structure (entry types, entry fields)




• Specifying how the entry types should appear in the bibliography (bibdrivers, filtering)




• Specifying how the citation for these entry types should behave.

As for the first two, moewe also covers them in the second part of his answer,
pointing to two good sources on the matter here on the site (Creating Entry in Bibtex for Executive Orders and How can I create entirely new data types with BibLaTeX/Biber?).
That’s about it. And it is a testimony to biblatex’s capabilities, which was
designed to be both customizable and extensible.

But some comments. It is hard to escape from defining a bibdriver for your
special entry type(s). Well, at least if you want things nicely done
(theoretically you could always try to hammer / (ab)use one or another existing entry type). Anyway, biblatex offers us a nice user interface with which this can be done without much fuss, so it is highly recommendable to do so.

As to extending or not the datamodel, the choices are not as clear and will
depend on your requirements (and taste). In particular, biblatex has some entry types and entry fields readily available for such purposes (entrytypes custom[a-f], entry fields name[a-c], list[a-f], user[a-f] etc.). So, if you only need some few of those, a proper extension of the datamodel may not be needed. Furthermore, if you’d like to use meaningful names for your types and fields, you can map the names of your choice to the existing ones with a sourcemap.

Another consideration regarding the extension of the data structure to support a special type of source is the portability of your (.bib) data. And, related to this, how much support you will be able to get from existing software for management of your bibliography data (JabRef, Zotero, Mendeley and equivalents and related software) if you like or need those. My view on this matter is that, for less standard types of sources, portability (and software support) is not granted anyway, so I might as well leave portability behind (for these types of entries only!), and go for a meaningful data structure. Time and again I found myself "tayloring" the bibentry data to achieve desired end results for a particular style, resulting in, let’s say, "less than semantic and less than portable" bib data. In my experience, this is particularly true with heavily customized styles or specialized styles, which will be the ones that support your special source type to start with. Every time you resort to this, your data is not really portable anymore. So I choose to separate regular entry types, and keep them portable, letting standard styles handle them, and for the non standard sources/entry types, assuming they will not be portable anyway, I tend to a meaningful / semantic data structure. I keep "portable" and "non portable" data in separate .bib files. However, notice that once you can carry the parallel structure for your special entry types to the style of your choice, that is not particularly restrictive (This is not unrestricted though. To start with, you won’t carry it outside biblatex, which means you won’t carry it outside LaTeX and thus will only be able to achieve pdf, or similar, output).

How to handle citations then? Citation call-outs are creatures more delicate
than bibdrivers. To start with because bibdrivers let you have a specific
structure for each entry type, while citations (normally) require a single
overall standard structure, whatever the entrytype may be. This point is
interesting because the first temptation here would be: I can simply redefine
the relevant citation commands or citation macros to get them to handle my
special source types. Technically that is true, but it’s not the crux of the
problem. First we have to figure how our citation call outs should be displayed, and if there is any meaningful way to fit our special sources within the current style citation structure. E.g. would it make any sense to try to fit a decree or a law in an author-year structure? Out of this dilemma, I eventually converged to what I call a "mixed citation style". My usual kind of special sources practically requires a long citation in footnotes, both because the amount of information is usually long enough not to fit the flow of text and because primary/archive sources do not usually reach individually the bibliography (their "container" does). This blends organically with the verbose style (or variants) but also works pretty well with, e.g. authoryear style for the regular entry types, provided I choose properly the citation command for each occasion. I’m not claiming this is the only approach to the problem, quite the contrary would be true, but only that this is the most expedient way to do so I was able to find for my current needs in dealing with non standard sources.

From a technical point of view, given this perspective, how to deal with
citations? Given my flexibility requirements, I’ve opted for patching (well, sort of) the cite bibmacro, which offers a reasonable hook for the purpose. This allows us to get the job done for whatever style we happen to choose ex post. (Ok, "whatever" is not completely true, more on this later). My current setup for this is in the form:

letbibmacro{cite:orig}{cite}



renewbibmacro*{cite}{%

  ifcategory{primary}{%

    usebibmacro{primary}}{%

    usebibmacro{cite:orig}}}

Of course, you could substitute primary there for legal (or whatever you may choose), just taking care that your set of legal sources entry types are duly added to the corresponding category. (For other techniques for the same
purpose, see Biblatex - xpatch bibmacro with unbalanced braces).

This essentially, redefines the cite bibmacro in a way that lets biblatex do what it usually does for regular entry types, but allows you to control separately what happens for your special entry types. That given, you now can exert full control of the citation call-outs, for your special entry types only, through the primary (legal) bibmacro, leaving citations for regular entry types untouched. That’s no small feat, but comes at a cost.

Some comments on this approach. The patch allows one to have style flexibility
for the regular entry types, which may or may not be a requirement for
you. However, even if it’s not, I suggest it still may be interesting because,
if the structure of the call out is not really adjustable within the current
citation style logic, you’ll probably see the need to resort to a similar
conditional (wherever you choose to place it). And, if so, there will not be much difference in
requirements/limitations at the end of the day. So the patch may well be convenient.
Any way, as mentioned, redefining the relevant bibmacros and/or the relevant
citation commands are also options to consider. Defining dedicated citation
commands too. Patching the citation commands is not, though (See discussion in
the comments at Biblatex's bibmacros, bibliography drivers, formats - patch or redefine?). This is relevant because the cite bibmacro is not a perfect universal hook, particularly not for comp variants of the standard citation styles (not to mention contributed ones).

This approach gives us a reasonable flexibility in the choice of the underlying citation style (for regular entrytypes), but it is not quite "style agnostic", and this for two reasons.

First, given we hijacked the core citation bibmacro in this fashion, it means we are responsible for reimplementing any special features of the citation style on our own for the special entry types (e.g. ibid handling, short vs long formats and so on). And it is hard to do this in a way which is independent of the style...

Second, not all styles get to build the full citation based solely in the cite bibmacro, not even the standard ones, the comp variants being the most conspicuous examples. (Though I still think this should be quite viable,
provided you don’t mix regular and non regular entry types in any single
citation command. This is untested though). Though, in principle, this approach may work with the standard styles and likely with (many?) contributed styles, whether it does or not hangs on this same issue. It must also be sensible (e.g. I don't think this would blend well with numeric or alphabetic, even if it technically works). Anyway, I have been using this with authoryear, authortitle and verbose, alongside their ibid variants quite successfully, without needing to get paranoid when citing any given source (due care is needed of course) and without worrying with any other adjustments beyond the choice of citation style.

A final touch. If you are like me, you may stumble upon some case where one of
your non regular source type(s) happens to be published within a regular one, and you’d like to treat it as a special type, because that’s meaningful/important, but still acknowledge the published version. You can do that in a way that is responsive to the citation style being used for the regular entry types by using the cite bibmacro for the regular type within the citation of the non regular one within an entrydata fed with a proper crossref. (moewe, now you know why I was so interested in nested entrydatas a while ago).

Conceptually, those are my main points. To be somewhat less abstract, I include some key pieces in concrete form. The primary bibmacro, which handles my citations for my primary sources uses mixed interfaces of biblatex (that is, uses a bibdriver to render the citation), and is something similar to:

newbibmacro*{primary}{%

  ifciteseen

  {ifboolexpr{

      test {ifciteibid}

      and

      not test {iffirstonpage}}

    {usebibmacro{cite:ibid}}

    {ifdriver{thefield{entrytype}:short}

      {usedriver{}{thefield{entrytype}:short}}

      {usedriver{}{thefield{entrytype}}}}}

  {usedriver{}{thefield{entrytype}}}}

Of course, you don’t have to use mixed interfaces, and could well go with
regular bibmacros. I happen to think this is specially convenient to be able to get citation call outs for each of my special entry types by simply defining the relevant bibdrivers. Note that the above structure handles both short/long citation forms and ibid, doing so automatically with the corresponding citation styles without any further intervention, given biblatex turns on or off the relevant trackers according to the chosen style.

My legislation drivers are the following:

DeclareBibliographyDriver{legislation}{%

  usebibmacro{bibindex}%

  usebibmacro{begentry}%

  usebibmacro{legislation:typenumber}%

  setunit{addcommaspace}%

  printdate%

  setunit{addcommaspace}%

  printfield{leggov}%

  setunit{addcommaspace}%

  iffieldundef{shorttitle}

    {printfield[title]{title}}

    {printfield[title]{shorttitle}}%

  setunit{addcommaspace}%

  iffieldundef{pubin}

    {}

    {%

      bibstring{in}%

      setunit{addspace}%

      usebibmacro{primpublishedin}%

    }%

  newunit

  ifcitation

    {}

    {printfield{addendum}}%

  usebibmacro{finentry}}



DeclareBibliographyDriver{legislation:short}{%

  usebibmacro{bibindex}%

  usebibmacro{begentry}%

  usebibmacro{legislation:typenumber}%

  setunit{addcommaspace}%

  printshortdate%

  setunit{addcommaspace}%

  iffieldundef{shortleggov}

    {printfield{leggov}}

    {printfield{shortleggov}isdot}%

  setunit{addcommaspace}%

  iffieldundef{pubin}

    {}

    {%

      bibstring{in}%

      setunit{addspace}%

      usebibmacro{primpublishedin}%

    }%

  usebibmacro{finentry}}

Which require:

newbibmacro*{legislation:typenumber}{%

  ifboolexpr{

    test {iffieldundef{pubin}}

    and

    test {ifcitation}

    and not

    test {iffieldundef{crossref}}

  }{%

    printtext[bibhyperref:crossref]{%

      printfield{legtype}%

      setunit{addspace}%

      bibstring{number}%

      setunit{addnbspace}%

      printfield{legnumber}}%

  }{%

    printfield{legtype}%

    setunit{addspace}%

    bibstring{number}%

    setunit{addnbspace}%

    printfield{legnumber}}}



newbibmacro*{primpublishedin}{%

  entrydata*{strfield{pubin}}{%

    ifentrytype{primperiodical}{%

      ifbibliography

        {clearfield{urlintro}%

          clearfield{url}%

          clearfield{addendum}%

          usedriver{}{thefield{entrytype}}}

        {begingroup%

          delimcontext{none}%

          usebibmacro{cite}%

          endgroup}%

      setunit{addcommaspace}%

      iffieldundef{savedvolume}

        {}

        {iffieldnum{savedvolume}

          {bibstring{jourvol}addnbspace}

          {}%

        printfield{savedvolume}}%

      setunit{addcommaspace}%

      iffieldundef{savednumber}

        {}

        {iffieldnum{savednumber}

          {bibstring{number}addnbspace}

          {}%

          printfield{savednumber}}%

      setunit{addcommaspace}%

      printsavedpubdate%

    }{%

      ifbibliography

        {usedriver{}{thefield{entrytype}}}

        {begingroup%

          delimcontext{none}%

          usebibmacro{cite}%

          endgroup}%

    }%

  }%

  ifboolexpr{

      test {iffieldpages{postnote}}

      and

      not test {iffieldundef{pages}}}

    {globaltoggletrue{prim:thiscite}}

    {}%

  setunit{bibpagespunct}%

  printfield{pages}%

}

With this (and assuming the relevant fields are defined in your datamodel), you just have to add all entries of type legislation to the category primary (or legal) to get your citation working for the legislation entrytype (the standard AtEveryCitekey hook should suffice for this).

To get things done in practice, I just fill out a proper template:

% legislation

% "legtype", "legnumber" and "date" are mandatory

% If "pubin" is not set, does not automatically crossref to any entry, if that's desired use the "crossref" field directly

@legislation{ID,

  OPTdocid = {},

  legtype = {},

  legnumber = {},

  OPTleggov = {},

  OPTshortleggov = {},

  date = {},

  OPTtitle = {},

  OPTshorttitle = {},

  OPTpubin = {},

  OPTvolume = {},

  OPTnumber = {},

  OPTpubdate = {},

  OPTpages = {},

  OPTcrossref = {},

  OPTaddendum = {},

}

This, of course, does not attend OSCLA or any other reputable citation style for legal sources, it is also not self sufficient code, but hopefully can do as an example for how to use this citation approach more concretely.

Well, I think those are my thoughts on the matter, as promised. I hope they get to be useful.

Use the oxnotes biblatex style. It does quite a good and robust job and has a sufficiently nuanced presentation. The laser-scapel precision of a full OSCOLA compliance is not really required outside a legal forum.

You were almost there in the MWE. Some additional adjustments:

In the bib file, for cases, put the case reference in the number field. This will handle both hardcopy and electronic law reports. For printed cases, page ranges are not required.

For legislation, do not use an author field. Having the year in the footnote is sufficient.

In the text, use autocite. Part of the clear-writing ethos for lawyers is to de-clutter the page. Reference details go in the footnotes. (Notice in the MWE how textcite wants to treat the legislation name - it should be plain.)

Note that you can put formatting commands (latex code) in the bib field items, emph, etc., if you want.

As to the question of 'should', it is a matter of degree.

If you're feeling tempted to go as far as splitting the bibliography into a legal part and a non-legal part, to help the reader, easiest way is to use keywords. (There are other ways as well: biblatex is a toolkit, in effect.)

MWE:

RequirePackage{filecontents}

begin{filecontents}{jobname.bib}

@jurisdiction{case,

  title             = {{Somebody} v {Somebody Else} and Others (No 4)},

  number              = {[2016] AC 100},

  date={2016},

  keywords={legal,case},

%  pages             = {100--178},

%  date              = {2015-03-10,2015-03-12,2015-04-25,2015-04-27,2015-05-01}

  }

@legislation{teu,

keywords = {legal,legislation},

entrysubtype = {eu-treaty},

title = {Consolidated Version of the

Treaty on European Union},

date = {2010},

journaltitle = {OJ},

series = {C},

volume = {83},

pages = {13},

shorthand = {TEU},

pagination = {article},

}

@jurisdiction{c632,title = {Tenacity Investments v Ku-Ring-Gai Council and Ors (No 2)},keywords = {au},number = {[2008] NSWLEC 171},institution = {Land and Environment Court of New South Wales},date = {2008-08-22},  keywords={legal,case},}



@jurisdiction{c606,title = {Lee-Hirons v Secretary of State for Justice},keywords = {au},number = {[2016] UKSC 46},institution = {United Kingdom Supreme Court},date = {2016-07-27},keywords={legal,case},}



@legislation{deddf,

    title               =   {{Deddf  Ardderchog (Cymru)}},

    year                =   {2014},

    institution              =   {{Cynulliad Cenedlaethol Cymru}},

    languageid          =   {cy},

      keywords={legal,legislation},

    }



@legislation{cansw,

    title               =   {Crimes Act (NSW) },

    year                =   {1900},

    languageid          =   {en_AU},

      keywords={legal,legislation},

    }



@article{article,

  title     = {Fantastic Findings and Where to Find Them},

  author    = {Vark, Aar D.},

  journal   = {Diligent Discoveries},

  volume    = 45,

  number    = 3,

  pages     = {23--32},

  year      = 2010}



@book{book,

  title     = {Brilliant Baths},

  author    = {Allard, M.},

  publisher = {Empire Books},

  address   = {Alpha Centauri},

  year      = 1998}



@book{austrams,

author = {Austin, Robert P. and Ramsay, Ian M},

title = {Ford, Austin and Ramsay's Principles of Corporations Law},

edition = {16},

publisher = {LexisNexis Butterworths},

date = {2015},

pagination = {paragraph},

ISBN = {9780409338386},

}

end{filecontents}



documentclass[welsh,british,a4paper]{article}

%usepackage[utf8]{inputenc}

%usepackage{geometry}

%usepackage{cfr-lm}

usepackage{babel}

usepackage{csquotes}

usepackage[style=oxnotes]{biblatex}

addbibresource{jobname.bib}



begin{document}



Most of my bibliography entries are `normal' sources, such as articles autocite[e.g.][]{article} and books autocite[e.g.][]{book}.

Textcite{article} and textcite{book} are cited using the author-year system.



However, I also need to cite legal sources, even though I'm not working in law or writing in this discipline.

Nonetheless, these need to be cited appropriately.

Unfortunately, Biblatex doesn't handle these out-of-the-box and the contributed styles which do are all designed for work in law, as opposed to, say, history, philosophy or quantum mechanics.

Hence, the standard styles do not handle these cases well:

begin{quote}

  textcite{deddf} is a law autocite{deddf}.

  Textcite[at 150]{case} is a case autocite{case}.

  A legal textbookautocite{austrams}. And another caseautocite{c632}. And a medium-neutral citation of a case autocite[at para 23]{c606}. Some EU legislation to play with autocite{teu}. And a statuteautocite{cansw}. A law from another jurisdiction: textcite{cansw}

end{quote}



printbibheading

printbibliography  [

    heading=subbibliography,%

    keyword=case,

    title={Cases}

    ]

printbibliography  [

    heading=subbibliography,%

    keyword=legislation,

    title={Statutes}

    ]

printbibliography  [

    heading=subbibliography,%

    notkeyword=case,

    notkeyword=legislation,

    title={General}

    ]



hrule





end{document}

giving:

and the footnotes:

and the bibliography:

P.S.
It took me a few minutes to work out why I couldn't find "Deddf Ardderchog" on BAILII! :)