<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>Alek Tarkowski &#8211; Open Source Initiative</title>
	<atom:link href="https://opensource.org/blog/author/alek-tarkowski/feed" rel="self" type="application/rss+xml" />
	<link>https://opensource.org</link>
	<description>The steward of the Open Source Definition, setting the foundation for the Open Source Software ecosystem.</description>
	<lastBuildDate>Wed, 19 Oct 2022 20:38:16 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://i0.wp.com/opensource.org/wp-content/uploads/2023/01/cropped-cropped-OSI_Horizontal_Logo_0-e1674081292667.png?fit=32%2C32&#038;ssl=1</url>
	<title>Alek Tarkowski &#8211; Open Source Initiative</title>
	<link>https://opensource.org</link>
	<width>32</width>
	<height>32</height>
</image> 
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/><atom:link rel="hub" href="https://websubhub.com/hub"/><site xmlns="com-wordpress:feed-additions:1">210318891</site>	<item>
		<title>On the emerging landscape of open AI</title>
		<link>https://opensource.org/blog/on-the-emerging-landscape-of-open-ai</link>
					<comments>https://opensource.org/blog/on-the-emerging-landscape-of-open-ai#comments</comments>
		
		<dc:creator><![CDATA[Alek Tarkowski]]></dc:creator>
		<pubDate>Wed, 19 Oct 2022 20:38:16 +0000</pubDate>
				<category><![CDATA[Opinions]]></category>
		<category><![CDATA[Deep Dive: AI]]></category>
		<guid isPermaLink="false">https://blog.opensource.org/?p=2583</guid>

					<description><![CDATA[In recent months, principles that underpin Open Source programming and other efforts to build information commons are being applied to AI research and development. It’s a turning point.]]></description>
										<content:encoded><![CDATA[
<p><em>This article was contributed by Alek Tarkowski, director of strategy of Open Future Foundation, the think tank for an open movement.</em></p>


<p>The launch of open models like BLOOM and Stable Diffusion is a symbolic birth moment for the field of open AI. In recent months, principles that underpin Open Source programming and other efforts to build information commons are being applied to AI research and development. It’s a turning point, and it’s worthy of consideration by everyone who cares about the future of Open Source software.</p>
<p>Several weeks ago, I took a closer look at the emergent field, and wrote an <span style="text-decoration: underline;"><a href="https://openfuture.pubpub.org/pub/notes-on-open-ai/release/1">analysis</a></span> that focused on the role of licensing models (followed by a <span style="text-decoration: underline;"><a href="https://twitter.com/atarkowski/status/1573272600561713152">Twitter thread</a></span>). I wanted to understand how these developments relate to other, earlier fields of openness, like Open Source software, open science, or open data. And in turn, how the approach to openness chosen by AI researchers might have an impact on these other fields.</p>
<p>The “open AI” term is not ideal.After all, OpenAI is the name of a company. Consequently, we need to build this emerging field in the shadow of corporate branding. As my friend <span style="text-decoration: underline;"><a href="https://twitter.com/paul_keller">Paul Keller</a></span> and I brainstormed the question of whether there might be better terms out there, he said that the question is about open sharing in times of “machines that eat content.”</p>
<p>In recent months, AI tools like large language and text-to-image models were released in ways that connect norms of open sharing with a vision of responsible AI. The BigScience Research Workshop <span style="text-decoration: underline;"><a href="https://huggingface.co/bigscience/bloom">recently released</a></span> the BLOOM model under RAIL, a new &#8220;Responsible AI license.&#8221; This was followed in August by <span style="text-decoration: underline;"><a href="https://stability.ai/blog/stable-diffusion-announcement">Stable Diffusion</a></span>, a text-to-image model launched under CreativeML Open RAIL-M. That’s a derivative license (RAIL is an open-ended family of licenses). And, <span style="text-decoration: underline;"><a href="https://ai.facebook.com/blog/democratizing-access-to-large-scale-language-models-with-opt-175b/">Meta AI</a></span> released an OPT language model under a similar, bespoke license that permits research uses. Interestingly, it did not describe this as an &#8220;open&#8221; release.</p>
<p>These new licenses aim to ensure not just openness of resources, but also responsibility for the impact of AI models. They are tackling what we call the <span style="text-decoration: underline;"><a href="http://paradox.openfuture.eu">Paradox of Open</a></span>: openness is today both a challenger and enabler of concentrations of power.</p>
<p>“Open vs responsible” is now a big topic in AI circles. But it also raises questions for the broader space of open sharing and for companies and organizations built on open frameworks. And it signals an urgent need to revisit open licensing frameworks. Anna Mazgal calls this “<span style="text-decoration: underline;"><a href="https://wikimedia.brussels/debate-ai-and-the-commons-sharing-is-caring/">a singularity point for open licensing</a></span>” and also argues for a review of open licenses from a fundamental rights perspective.</p>
<p>Consider this: Open AI tools have the same generative potential as open servers (Apache Software Foundation), browsers (Mozilla) or encyclopedias (Wikipedia). But for the first time, the debate is not just about sharing. Management of risk and responsible use are raised from the start not as related to the issue of open, but as norms of equal importance. And in the case of the RAIL license, its creators pay more attention to figuring out how to enforce responsible behavior, than to openness (which they sort of take for granted). The license is meant to do what ethical guidelines fail to do. An <span style="text-decoration: underline;"><a href="https://dl.acm.org/doi/abs/10.1145/3531146.3533143">excellent paper</a></span> published at ACM FAccT 2022 by Danish Contractor, Daniel McDuff, Julia Haines, Jenny Lee, Christopher Hines, Brent Hecht, Nicholas Vincent, and Hanlin Li examines <span style="text-decoration: underline;"><a href="http://arxiv.org/abs/2011.03116">behavioral use licensing for responsible AI</a></span>. It should be required reading for anyone interested in the topic.</p>
<p>Is giving up on the most permissive licenses really necessary—and worth it? Can a balance really be found? John Weitzmann from Wikimedia argued recently that <span style="text-decoration: underline;"><a href="https://wikimedia.brussels/debate-ai-and-the-commons-solutions-to-be-found-only-beyond-licences/">use restrictions are not effective</a></span>. Other issues raised by new licenses include enforcement, governance, license proliferation, peer production, and theory of change behind creating open alternatives. I have defined these issues in more detail in my recent <span style="text-decoration: underline;"><a href="https://openfuture.pubpub.org/pub/notes-on-open-ai/release/1">notes on Open AI</a></span>.</p>
<p>Some will ask whether the RAIL license is really an open license. I don&#8217;t think that that&#8217;s the key question. The more important one is whether we need to revisit open licensing frameworks and definitions and embrace responsible licensing as a flavor of open.</p>
<p>I’ve recently published a <span style="text-decoration: underline;"><a href="https://openfuture.pubpub.org/pub/ai-commons/release/2">white paper</a></span>, co-authored with Zuzanna Warso, on the use of openly licensed photographs for face recognition training datasets. We followed previous work by Adam Harvey and his <span style="text-decoration: underline;"><a href="http://exposing.ai">exposing.ai project</a></span> (Adam also conducted <span style="text-decoration: underline;"><a href="https://ahprojects.com/creative-commons/">a detailed exploration</a></span> of aspects of the datasets related to open licensing). These controversial cases show how unethical uses of the information commons were a side effect of deploying key datasets for AI training. They also demonstrate the importance of assigning responsibility and ensuring responsible use—the same issues that the new RAIL licenses aim to solve.</p>
<p>In our paper, we argue that these datasets (and other elements of AI systems) should be governed as a commons. And as the AI commons <span style="text-decoration: underline;"><a href="https://openfuture.eu/publication/data-commons-primer/">gets designed</a></span>, licensing is one of the key questions that need to be answered. Hopefully, the answer will be peer produced together by open advocates and AI researchers. Please find me on Twitter (<span style="text-decoration: underline;"><a href="http://www.twitter.com/atarkowski">@atarkowski</a></span>) if you would like to be part of such a conversation.</p>
<p><em>Image generated by </em><a href="https://huggingface.co/spaces/stabilityai/stable-diffusion">Stable Diffusion</a><em>, using the prompt &#8220;blooming artificial intelligence&#8221;.</em></p>


<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://opensource.org/blog/on-the-emerging-landscape-of-open-ai/feed</wfw:commentRss>
			<slash:comments>26</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">19828</post-id>	</item>
	</channel>
</rss>
