21 October 2017

FOI and Surveillance

'The Ecology of Transparency Reloaded' by Seth F. Kreimer in David Pozen and Michael Schudson (eds), Troubling Transparency: The Freedom of Information Act and Beyond (olumbia University Press, 2018) comments
As Justice Stewart famously observed, "[t]he Constitution itself is neither a Freedom of Information Act nor an Official Secrets Act." What the Constitution's text omits, the last two generations have embedded in "small c" constitutional law and practice in the form of the Freedom of Information Act and a series of overlapping governance reforms including Inspectors General, disclosure of political contributions, the State Department’s "Dissent Channel," the National Archives Information Security Oversight Office, and the publication rights guaranteed by New York Times v. United States. These institutions constitute an ecology of transparency.
The late Justice Scalia argued that the Freedom of Information Act was unnecessary. FOIA has also suffered the converse criticism: that it is necessary but ineffective. A third constellation of critics discerns a mismatch between the legal regime of transparency and the goals of good governance. David Pozen has argued that the costs imposed are pathologically asymmetric. FOIA, he alleges, is "neoliberal" and "reactionary"; it "empowers opponents of regulation, distributes government goods in a regressive fashion, and contributes to a culture of contempt surrounding the domestic policy bureaucracy," while doing little to further scrutiny or control of corporate exploitation.
Drawing on case studies from the Bush-era "Global War on Terror" (or "Terrorism"), this chapter argues that critics miss important normative and practical issues. Critiques focused on denied requests and unsuccessfully litigated cases in isolation miss the ways in which information obtained though unlitigated or partially successful requests is facilitated by, and in turn has catalyzed other elements of a broader ecology of transparency. Analysts of FOIA should be alert to the elements of that ecology. Critics should acknowledge its virtues of resiliency and efficacy. Reformers should neither slight nor squander them.
The Constitutional Limits of Private Surveillance' by Kiel Robert Brennan-Marquez in Kansas Law Review (Forthcoming) comments
The age of data-driven law enforcement is upon us. As a consequence, state officials now rely heavily on private surveillance technology to forecast threats, drive investigations, and mobilize enforcement. On the whole, this development is welcome; the use of privately-collected data promises to refine policing and counterterrorism efforts. But it also has major implications for constitutional privacy. For the Fourth Amendment to safeguard privacy into the future, its approach to state action must change. Instead of turning, as it has historically, on the extent of government influence over private surveillance activity, the Fourth Amendment’s coverage should depend on whether private surveillance activity effects an extension, in practice, of law enforcement’s infrastructural capacity.
In addition to its normative benefits, the “infrastructural” approach also resolves certain mysteries within existing law and brings the Fourth Amendment into greater alignment with broader patterns of state action jurisprudence. Most importantly, focusing on infrastructure underscores the connection — unappreciated to date — between (1) law enforcement’s compulsory seizure of privately-held data, enabled by the so-called “third-party doctrine,” and (2) informal data-sharing between law enforcement and the private sector. The third-party doctrine is teed up for reform this term in Carpenter v. United States. But no such progress is on the horizon for informal data-sharing. Doctrinally, the issues have been compartmentalized, even though, at an infrastructural level, they represent two sides of the same coin. Both are mechanisms by which law enforcement officials capitalize on private surveillance technology in lieu of performing surveillance directly — and both thus facilitate bulk, warrant-less data collection by the state. As such, a full solution to the shortcomings of the third-party doctrine demands parallel attention to the shortcomings of the Fourth Amendment’s antiquated state action rules, and vice versa. Solving one problem in isolation from the other risks a partial victory — or even a Pyrrhic one, to the extent that reform of the third-party doctrine could encourage even more informal data-sharing between the government and the private sector. Against this backdrop, the infrastructural approach offers an integrated path forward, and one that will only become more urgent, over time, as data-driven law enforcement practices intensify.

20 October 2017

Victorian Digital Czar

The Victorian Government, following the various whole of government digital strategy initiatives announced over the past decade (and accompanied by fundamental weakening of the state privacy commissioner, has announced that it is "improving data-sharing across government to deliver better services for Victorians".
The Government collects vast quantities of data – about education and health, our communities, business, employment, infrastructure and the environment. However for too long government data has been held in agency silos and not available across government to tackle many of the pressing community concerns.
The Victorian Data Sharing Bill 2017 – which was second read in Parliament today – will break down these silos and ensure agencies can share data and information across the whole of Government.
Enabling data to be shared and used across government will provide insights about what works and why, and ensure informed policy decisions that deliver for hard working families – from tackling family violence to improve health outcomes.
This Bill provides a clear legal framework that allows for government data to be shared for policy making, service planning and design, enabling government agencies to work together to tackle key priorities.
The Bill also includes strong safeguards and oversight to protect personal data and information, including independent oversight by Victoria’s privacy regulators, mandatory reporting of any potential breaches, and new offences for unauthorised access, use or disclosure.
This Bill follows other work that the Labor Government is doing to modernise Victoria’s data and information sharing regime that includes:
  • Legislation to protect women affected by family violence by better sharing information and prioritising victim survivors over their perpetrators 
  • The development of a Central Information Point to facilitate information sharing across agencies involved in protecting women from family violence 
  • The creation of Office of Victorian Information Commissioner, bringing together freedom of information with data protection and privacy, to provide independent oversight across those closely-related fields.
The Labor Government has also appointed Victoria’s first Chief Data Officer within the Victorian Centre for Data Insights to transform how the Victorian Government uses data to strengthen policy making. This Bill supports the new Officer by establishing into law the statutory position, and its powers and functions.
The Centre website states -
The Victorian Centre for Data Insights (the Centre) provides a whole-of government focus to help transform the way government uses data.
The Centre will tell a bigger story than analysing data from just one source. It will bring data together from across government to generate new insights to design better and more data driven policy and services.
The Centre will:
  • partner with departments and agencies on data analytics projects that inform policy making and service design 
  • build data analytics skills and capability of the Victorian Public Service (VPS) 
  • contribute to improving how data is collected and managed across the VPS 
  • work with other governments across Australia on better data use, on behalf of the Victorian Government.
The Centre operates as a business unit within the Department of Premier and Cabinet. The Centre is part of the Special Minister of State’s focus on public sector reform, working to strengthen evidence- based policy and practice.
The Centre is led by Victoria’s first Chief Data Officer (CDO). The CDO will lead the Centre, and advocate for the better use of data across government. The CDO is supported by a team of data analysts, information management and policy specialists.
The Explanatory Memo for the Bill states
The main purpose of the Victorian Data Sharing Bill 2017 is to establish the office of the Chief Data Officer, to promote the sharing and use of public sector data as a public resource that supports government policy making, service planning and design, and to amend the Privacy and Data Protection Act 2014.
Clause Notes
Part 1--Preliminary
Clause 1 provides that the main purposes of the Bill are--
  • to establish the office of Chief Data Officer; and 
  • to promote the sharing and use of public sector data as a public resource that supports government policy making, service planning and design; 
  • to remove barriers that impede the sharing of identifiable data with the Chief Data Officer or with data analytics bodies, and to facilitate the sharing of data across the public sector; and 
  • to provide protections in connection with data sharing under this Bill, by-- 
  • specifying the purposes of data sharing, and the circumstances in which sharing of identifiable data is permitted; and   
  • ensuring that data that is handled under this Bill is protected from unauthorised access, use or disclosure; and 
  • to make consequential and other amendments to other Acts.
Clause 2 sets out the commencement of the Bill. It will come into operation on the day after the day on which it receives the Royal Assent.
Clause 3 provides definitions for the key terms used in the Bill.
Subclause (2) provides that, for the purposes of the Bill, a body holds data if the data is contained in a document in the possession or under the control of the body.
Clause 4 provides that the Bill binds the Crown. Clause 5 provides that data must only be handled under the Bill for the purpose of informing government policy making, service planning and design.
Part 2--Chief Data Officer
Clause 6 provides that the Secretary to the Department responsible for administering this Bill may employ a person under Part 3 of the Public Administration Act 2004 to be the Chief Data Officer.
Clause 7 sets out the functions of the Chief Data Officer which include to conduct data integration and data analytics work to inform government policy making, service planning and design, to build capability in data analytics across the public sector, to coordinate data sharing and integration on behalf of the state of Victoria, to make integrated data sets and the results of data analytics work available to data sharing bodies and designated bodies and to collaborate with these bodies, and any other functions incidental to these functions or conferred under this Bill or any other Act.
Part 3--Data requests
Clause 8 sets out the mechanism by which the Chief Data Officer can make a formal request to a data sharing body or a designated body for data held by the body. The Chief Data Officer can only make a request for the purpose of informing government  policy making, service planning and design and must not request restricted data. The Chief Data Officer must make the request in the form of a written notice which specifies the data being requested, the reasons for the request and how the data will be handled.
Clause 9 provides that a data sharing body that receives a request under clause 8 must respond to the request within 10 business days (or a longer period as agreed by the Chief Data Officer). The data sharing body's response must either be to provide the data, or to provide reasons (in accordance with clause 14) for why the data sharing body will not be providing some or all of the data. If the data sharing body does not intend to provide some or all of the data, the response must be given to the Secretary to the Department as well as the Chief Data Officer.
Clause 10 provides that if a designated body receives a request under clause 8, the designated body may respond by providing some or all of the data but is not obligated to do so.
Clause 11 sets out the mechanism by which the Chief Data Officer can make a formal request to a data sharing body or a designated body for information about their data holdings. The information that may be requested includes, but is not limited to--
  • the kind of data sets held by the data sharing body or designated body; and 
  • the number of data sets held by the data sharing body or designated body; and 
  • the kind of information contained in the data sets held by the data sharing body or designated body; and 
  • the accuracy, currency and completeness of the data sets held by the data sharing body or designated body.
The Chief Data Officer can only make a request for the purpose of informing government policy making, service planning and design. The Chief Data Officer must make the request in the form of a written notice which specifies the information being requested, the reasons for the request and how the information will be handled.
Clause 12 provides that a data sharing body that receives a request under clause 11 must respond to the request within 10 business days (or a longer period as agreed by the Chief Data Officer). The data sharing body's response must either be to provide the information, or to provide reasons (in accordance with clause 14) for why the data sharing body will not be providing some or all of the information. If the data sharing body does not intend to provide some or all of the information, the response must be given to the Secretary to the Department as well as the Chief Data Officer.
Clause 13 provides that if a designated body receives a request under clause 11, the designated body may respond by providing some or all of the information but is not obligated to do so.
Clause 14 sets out a non-exhaustive list of reasons for which a data sharing body or designated body may choose to refuse to provide data or information requested by the Chief Data Officer under clause 8 or 11. The responsible officer of the data sharing body or designated body may refuse if the responsible officer considers that data or information should not be provided for any reason, including but not limited to the following reasons--
  • • that the provision of the data or information would constitute a breach of one or more of the following-- 
  • client legal privilege or legal professional privilege; 
  • contract; 
  • an equitable obligation of confidence; 
  • an order of a court or tribunal; 
  • subject to Part 4, a law of the Commonwealth, a State or a Territory; or 
  • that the provision of the data or information would be likely to prejudice one or more of the following-- 
  • the investigation of a breach, or possible breach, of a law of the Commonwealth, a State or a Territory, or the administration or enforcement of such a law; 
  • a coronial inquest or inquiry; 
  • a proceeding before a court or tribunal; or 
  • that the responsible officer believes on reasonable grounds that the provision of the data or information would be likely to endanger the health, safety or welfare of one or more individuals.
Part 4--Use and disclosure of data
Division 1--Authorised use and disclosure of identifiable data
This division sets out the circumstances in which the use or disclosure of identifiable data is authorised by the Bill and the restrictions which apply to use and disclosure of identifiable data.
Clause 15 subclause (1) authorises the responsible officer of a data sharing body or a designated body to disclose identifiable data to the Chief Data Officer in response to a request under clause 8. The disclosure is only authorised for the purpose of informing government policy making, service planning and design.
Subclause (2) authorises the responsible officer of a data sharing body or designated body to disclose identifiable data to a data analytics body. The disclosure is only authorised for the data analytics body to conduct data integration on the identifiable data for the purpose of informing government policy making, service planning and design.
Clause 16 authorises the Chief Data Officer to disclose identifiable data that the Chief Data Officer has received from a data sharing body or designated body under the Bill to a data analytics body. The disclosure is only authorised for the data analytics body to conduct data integration on the identifiable data for the purpose of informing government policy making, service planning and design.
Clause 17 authorises the Chief Data Officer to use (as well as collect, hold and manage) identifiable data received from data sharing bodies and designated bodies under this Bill. The Chief Data Officer is only authorised to use the identifiable data for data integration for the purpose of informing government policy making, service planning and design.
Clause 18 provides that if the Chief Data Officer or a data analytics body intend to use the data that they have received under this Bill for the purpose of data analytics work, they must first take reasonable steps to ensure that the data no longer relates to an individual that can be reasonably identified. In doing so, the Chief Data Officer or data analytics body must have regard to--
  • the de-identification techniques applied to treat the data; 
  • the technical and administrative safeguards and protections implemented in the data analytics environment to protect the privacy of individuals; and 
  • any other considerations specified in the guidelines issued by the Chief Data Officer.
Clause 19 provides that before disclosing the results of data analytics work, the Chief Data Officer or a data analytics body must ensure that the results to be disclosed include only de-identified data.
Division 2--Authorised use and disclosure of data to which a secrecy provision applies
Clause 20 provides that the responsible officer of a data sharing body or designated body may disclose data to the Chief Data Officer under this Bill, even where a secrecy provision under another Act applies to that information, so long as the disclosure is in accordance with, and for the purposes of, this Bill.
Clause 21 requires that if a responsible officer of a data sharing body or designated body is aware that a secrecy provision applies to data which they are disclosing to the Chief Data Officer, the body must inform the Chief Data Officer of the existence of the secrecy provision.
Clause 22 provides that if a secrecy provision applies to the data received by the Chief Data Officer under this Bill, then the Chief Data Officer is authorised to use the data for the purposes of this Bill.
Clause 23 provides that if the Chief Data Officer intends to disclose information received under this Bill to which a secrecy provision applies, the Chief Data Officer must first obtain the approval of the Minister responsible for administering the secrecy provision  (and in the case of a secrecy provision in the Taxation Administration Act 1997, the Commissioner of State Revenue).
Subclause (2) enables the Chief Data Officer to disclose data to the Minister or to the Commissioner of State Revenue (as applicable) for the purpose of obtaining the approval.
Division 3--Relationship with other Acts
Clause 24 subclause (1) provides that this Part does not affect the handling of data that would otherwise be permitted by or under the Privacy and Data Protection Act 2014, the Health Records Act 2001 or any other Act.
Subclause (2) provides that except as expressly provided by this Part, this Bill does not affect obligations under the Privacy and Data Protection Act 2014 or the Health Records Act 2001 in relation to the handling of identifiable data.
Subclause (3) provides that if the Chief Data Officer or a data analytics body becomes aware that this Bill, the Privacy and Data Protection Act 2014, or the Health Records Act 2001 has been or is likely to have been breached in relation to data handled under the Bill while in the Chief Data Officer's or the data analytics body's control, they must as soon as possible inform the data provider and the Information Commissioner or Health Complaints Commissioner (as relevant).
Clause 25 provides that the Freedom of Information Act 1982 does not apply to data in the possession of the Chief Data Officer or a data analytics body that was received or integrated under this Bill.
Part 5--Offences
Clause 26 creates a summary offence for a person (without a reasonable excuse) to access, use or disclose data obtained by the person under this Bill, other than in accordance with this Bill or in the performance of the person's functions under this Bill. The penalty for the offence is 240 penalty units or 2 years' imprisonment or both.
Clause 27 creates an indictable offence for a person to access, use or disclose any data or information obtained by the person under this Bill if the person knows or is reckless as to whether the data or information may be used to--  
  • endanger the life or physical safety of any person; or 
  • commit, or assist in the commission of, an indictable offence; or 
  • impede or interfere with the administration of justice.
The penalty for the offence is 600 penalty units or imprisonment for 5 years or both.
Part 6--Reporting and review
Clause 28 requires that the Chief Data Officer provide a report to the Health Complaints Commissioner at least every 12 months on the operation of the Centre in relation to the Centre's use of health information including the sharing of health information, projects which have involved the use of health information and the Centre's compliance with the Health Records Act 2001.
Clause 29 requires that the Chief Data Officer provide a report to the Information Commissioner at least every 12 months on the operation of the Centre in relation to the Centre's use of personal information (other than health information) including the sharing of personal information, projects which have involved the use of personal information and the Centre's compliance with the Privacy and Data Protection Act 2004.
Clause 30 provides that the Minister must cause a review to be made of the first 5 years of operation of this Bill and within 12 months of the review being completed, cause the report of the review to be laid before each House of Parliament.
Part 7--Other matters
Clause 31 subclause (1) allows the Chief Data Officer to delegate any of their powers, functions or duties (other than their power of delegation) under the Bill to a person employed or engaged by the Department responsible for administering this Bill.
Subclause (2) allows the Secretary to a Department to delegate in their capacity as a data analytics body, any of their powers, functions or duties (other than their power of delegation) under the Bill to a person employed or engaged by the Department.
Subclause (3) allows the responsible officer of a data sharing body, data analytics body or designated body to delegate any of their powers, functions or duties (other than their power of delegation) under the Bill to a person employed or engaged by the relevant body.
Clause 32 provides that the Governor in Council may make regulations to give effect to the Bill, including regulations to--
  • prescribe a body as a data sharing body or a data analytics body; and 
  • prescribe a class of data to be restricted data; and 
  • prescribe a provision to be a secrecy provision to which Division 2 of Part 4 does not apply.
Clause 33 provides that the Chief Data Officer may issue and publish policies and guidelines in relation to the administration of this Bill and that a data analytics body, data sharing body or a designated body must have regard to the policies or guidelines issued by the Chief Data Officer. The policies and guidelines may relate to--
  • privacy and confidentiality preserving procedures for treating data; 
  • data security safeguards in relation to data handling and storage under this Bill; 
  • secure technology platforms for data handling and storage under this Bill; 
  • risk mitigation frameworks for data handling and storage, such as proportionate risk assessment tools and techniques; 
  • protocols for data integration and data analytics projects, such as project design, governance and data handling arrangements; 
  • any other matters the Chief Data Officer considers relevant.
Part 8--Other matters
Clause 34 subclause (1) amends Schedule 1 of the Privacy and Data Protection Act 2014 to correct the definition of unique identifier by replacing the second "but" in the following definition with an "and" so that it now reads as follows--
"unique identifier means an identifier (usually a number) assigned by an organisation to an individual uniquely to identify that individual for the purposes of the operations of the organisation but does not include an identifier that consists only of the individual's name and does not include an identifier within the meaning of the Health Records Act 2001;".
Subclause (2) amends Schedule 1 of the Privacy and Data Protection Act 2014, to insert "or authorised" in clause 10.1(b) so that it permits the collection of sensitive information by an organisation where it is required or authorised by law.
Clause 35 amends section 20 of the Family Violence Protection Amendment (Information Sharing) Act 2017 to repeal certain amendments to the Privacy and Data Protection Act 2014 that are no longer required as a result of the amendment made by clause 34(2) of the Bill.
Clause 36 provides that the repeal of this Part is repealed on the first anniversary of the day on which this Bill comes into operation.

18 October 2017

Protests and Offensive Speech

In Brown & Anor v The State of Tasmania [2017] HCA 43 the High Court has held invalid certain provisions of the Workplaces (Protection from Protesters) Act 2014 (Tas) in relation to the implied freedom of political communication.

Provisions of the Act prohibit "protesters" – persons engaging in conduct in furtherance of, or for the purposes of promoting awareness of or support for, "an opinion, or belief, in respect of a political, environmental, social, cultural or economic issue" – from engaging in certain conduct on "business premises" or "business access areas". "Business premises" relevantly comprises "forestry land", which includes land on which "forest operations" are being carried out. "Business access area" is defined as so much of an area of land, outside business premises, as is reasonably necessary to enable access to an entrance to, or to an exit from, business premises. Police officers may direct any person to leave or stay away from "business premises" or "business access areas" in certain circumstances under pain of arrest or criminal penalty.

The plaintiffs, notably former Greens Senator Bob Brown were present in the Lapoinya Forest in North West Tasmania when forest operations were being conducted there. They were arrested and charged with offences under the Act in relation to their conduct in opposing the logging of part of that forest. (The charges against each plaintiff were not later pursued.)

It was not disputed that, but for directions made under the Act, and to the extent permitted by other laws, the plaintiffs would have gone back to the Forest for the purpose of raising public awareness of logging in that forest.

In the High Court, the plaintiffs challenged the validity of provisions of the Act on the basis that the Constitution protects freedom of political communication and that those provisions impermissibly burden that freedom.

 A majority of the High Court has today held that the impugned provisions of the Act in respect of forestry land and business access areas relating to forestry land effectively burdened the implied freedom of political communication.

A majority of the Court held that the Act pursued the legitimate purpose of protecting businesses and their operations by ensuring that protesters do not prevent, hinder or obstruct the carrying out of business activities. The Court however held that the burden imposed by the impugned provisions on the implied freedom of political communication was impermissible. The provisions were not reasonably appropriate and adapted, or proportionate, to the pursuit of that purpose in a manner compatible with the maintenance of the system of representative and responsible government that the Constitution requires.

A majority of the Court therefore declared that the impugned provisions were invalid in their operation in respect of forestry land and related business access areas.

In Danny Lim v Regina [2017] NSWDC 231 Judge AC Scotting has quashed the conviction of controversial figure Danny Lim for the  summary offence, under the Summary Offences Act 1988 (NSW), of using offensive language (in the form of a placard critiquing Tony Abbott)  in or near public place or school.

 Lim's case on the appeal was that the conduct in question was not offensive, that the conduct merely involved the use of offensive language - you can read the judgment to see the offensive words - and could thereby not amount to offensive conduct, that the political nature of the appellant’s communication amounted to a reasonable excuse for the conduct and finally that section 4 of the Act was invalid because it burdened the implied freedom of political communication.

The Court stated
Conduct capable of amounting to an offence should be limited to conduct at the high end of the range that could be considered “offensive”. The purpose of section 4 is to protect members of the public from undue disturbance of the use and enjoyment of public places: Coleman v Power [2004] HCA 39; (2004) 220 CLR 1 at [32] per Gleeson CJ. Section 4 extends to conduct in or near a school. This indicates that part of the purpose of the section is to restrict behaviour that might cause a parent or guardian concern for what their child may be exposed to. As such in assessing whether conduct is offensive, the reaction to it being witnessed by children must be considered. 
Where constructional choices are open, a meaning that limits the effect on political communication is to be preferred: Monis at [331]. The legislation should be read as going no further than is necessary to achieve its protective purpose, consistent with its terms, without unduly burdening political communications: Monis at [334]. 
In Coleman, Gleeson CJ at [14]-[15] said that a Queensland statute prohibiting the use of “threatening, abusive or insulting words” in a public place required more than the language being “merely derogatory” of the person to whom it was addressed. The language needed to be of such a nature that the use of it in a public place was contrary to the contemporary standards of public good order and goes beyond an exercise of freedom to express an opinion on controversial issues. 
The reasonable excuse defence involves an evaluative judgement. It is open to conclude that the political nature of a communication could be considered to be a reasonable excuse, in an appropriate case. 
The term “reasonable excuse” has been used in many statutes. What is a reasonable excuse depends upon the circumstances of the case and the purpose of the provision to which the defence of reasonable excuse is an exception: Taikato v The Queen[1996] HCA 28; (1996) 186 CLR 454 at 464 per Brennan CJ, Toohey, McHugh and Gummow JJ. A reasonable excuse is no more or less than an excuse that would be accepted by a reasonable person: Taikato at 470. 
The onus of proving a reasonable excuse is on the appellant on the balance of probabilities.
In analysing the Magistrate’s reasons the Court notes the  ex tempore judgment and states
Ultimately, the Magistrate found it to be a very “straightforward case”. She found that the reasonable person would have been offended by the sandwich board because the Impugned word was used by reference to the Prime Minister. 
The Magistrate’s reasons did not state the reasons why a reasonable person would have been offended. I interpolate that the Magistrate found that it was the use of the impugned word alone that was offensive. 
In both of these respects I am satisfied that the Magistrate fell into error. First, the Magistrate failed to give reasons for her finding as to why the conduct was capable of arousing a significant emotional reaction and was thereby offensive, and second the only available inference is that Magistrate decided that the use of the impugned word was of itself offensive.
Accordingly
Having found error, it is now necessary to consider the decision to be made on the basis of the facts and the law as they now stand. 
Was the conduct offensive? 
The only aspect of the appellant’s conduct that could be considered to be offensive was the use of the impugned word on the front of the sandwich board. The use of the upside down pointed capital “A” on the back of the sandwich board did not create the same logical inference that the use of the impugned word was intended and I am not satisfied beyond reasonable doubt that the reasonable person would read the back of the sandwich board as a reference to the impugned word. 
It should be noted that on both the front and back of the sandwich board that the appellant used the apostrophe in the same position as if he was using the word “can’t”. There was nothing that could have been considered to be offensive by the appellant wearing a sandwich board containing a political comment, in the absence of the impugned word, for example if the appellant had used the word “can’t” instead. 
At its highest, the prosecution case is that the use of the impugned word was used as derogatory description of the Prime Minister, and it is the use of the impugned word that is offensive. As a matter of law, the impugned word is not necessarily offensive, even when used in a public place: Dalton at 555. 
The impugned word is often used as a derogatory term to describe a person of any gender. In this use, it is best described as an expletive, rather than as an intensive or it being used for its literal significance. 
Politicians and their views are often subject to criticism in public. This is an essential and accepted part of any democracy. That criticism can often extend to personal denigration or perhaps even ridicule, but still maintain its essential character as political comment. There is no reason to conclude that the Prime Minister, as the leader of the Federal Government should be treated any differently to any other person who holds or seeks political office. 
The front of the sandwich board, at the height of the prosecution case, conveyed no more than a reference to the Prime Minister in derogatory terms. It was clear that the description of the Prime Minister was given by reference to disapproval with the policies of the government and or the Prime Minister’s decisions relating to those policies. 
The impugned word is now more prevalent in everyday language than it has previously been. It is commonplace in movies and television entertainment, although it is not without restriction in that context. The impugned word is of ancient English origin and featured in Shakespeare’s Hamlet. The prevalence of the impugned word in Australian language is evidence that it is considered less offensive in Australia than other English speaking countries, such as the United States. However, that also appears to be changing as is evidenced from the increase in American entertainment content featuring the impugned word. 
References to the impugned word are often included in print media, usually a reference to a direct quote with the “u” or the “un” removed. This treatment of the word does little to alleviate the meaning to be conveyed and is directed more at decorum than avoiding offence that may be caused by the publication of the impugned word. 
It was also open to read the front of the sandwich board as a play on words, comparing the similarity in the pronunciation of the word “can’t” and the impugned word. This is particularly demonstrated by the inclusion of the apostrophe in the relevant position. The front of the sandwich board is capable of being construed as being clever or light hearted and thereby removing or reducing the force of the impugned word. It is also capable of being read as the word “can’t”. 
I am not satisfied beyond reasonable doubt that a reasonable person considering all of the circumstances of the case would have had a significant emotional reaction such as anger, disgust, resentment or outrage to the appellant’s conduct. Whilst the conduct was inappropriate and in poor taste, I am not satisfied beyond reasonable doubt that it was offensive, or so offensive as to be considered in the high end of the range of what would be considered to be offensive.
Was the offensive conduct any more than the use of offensive language? 
The appellant’s second contention was that the appellant’s conduct involved no more than a use of offensive language and was thereby excluded from the offence of offensive conduct, by section 4(2) Summary Offences Act 1988
The term “use” is defined in the Macquarie Dictionary to “employ for some purpose, to avail oneself of, to expend or consume, or to utter words or speak a language”. The word in section 4(2) is “using” but I do not think that is a significant difference. 
Whilst the definition of “use” refers to spoken language, the appellant says that there is no good reason to restrict the meaning of the word to that narrow use in the context of the legislation. In other words, the display of the impugned word on the front of the sandwich board was no more than a use of offensive language. The prosecution case is that what the appellant did was to prepare and wear a sandwich board in a public place that contained offensive language and that the whole of his conduct should be considered to be offensive. 
To determine the interpretation of section 4(2) it is necessary to consider it in the context of the statute, bearing in mind the legislative purpose: SAS Trustee Corporation v Woollard [2014] NSWCA 75 at [58] per Bathurst CJ. 
The offensive language offence in section 4A Summary Offences Act 1988, provides that, “[A] person must not use offensive language in or near, or within hearing from, a public place or school”. 
The narrow definition of “use” in this context promotes the purpose of the legislation, to restrict the uttering or speaking of offensive language in public places. The requirement that the offensive language must be used within the hearing of a public place or school supports this interpretation. 
The wider definition of “use” of offensive language, such as where it is written, is covered by the offence of offensive conduct. That interpretation is consistent with the limiting employment of the word “merely” in section 4(2). 
For these reasons, the word “using” in section 4(2) means speaking or uttering offensive language and the appellant has not made out this contention. 
Did the appellant have a reasonable excuse for his conduct? 
The Magistrate accepted the only evidence before her that the appellant made and wore the sandwich board for the purpose of making a political comment. 
If I am wrong in the conclusion that the appellant’s conduct was offensive, then it is open to balance the right of freedom of political communication with the offensiveness of the appellant’s conduct, to determine if the appellant had a reasonable excuse for his actions. 
In the present case, the appellant did not unequivocally use the impugned word. The front of the sandwich board presented a depiction of the word “can’t” that could be read as “cunt”, but it was not the only logical conclusion to draw. The language used was clearly a play on words. If the appellant’s conduct was offensive, contrary to my view, in my view it was only marginally so. 
The Magistrate accepted the appellant’s evidence that he did not intend to be offensive by using the words that he did. In my view this is also a relevant consideration. 
I am satisfied on the balance of probabilities that in the circumstances of this case that the appellant has demonstrated a reasonable excuse for his actions that in the course of expressing a political comment he published a play on words that was capable of being construed as offensive.