Framework 0.4.2

[Azalee Freas]

On April 29, 2024, NIST released a draft publication based on the AI Risk Management Framework (AI RMF) to help manage the risk of Generative AI. The draft AI RMF Generative AI Profile can help organizations identify unique risks posed by generative AI and proposes actions for generative AI risk management that best aligns with their goals and priorities. Developed over the past year and drawing on input from the NIST generative AI public working group of more than 2,500 members, the guidance centers on a list of 12 risks and more than 400 actions that developers can take to manage them. More information is available here.

In collaboration with the private and public sectors, NIST has developed a framework to better manage risks to individuals, organizations, and society associated with artificial intelligence (AI). The NIST AI Risk Management Framework (AI RMF) is intended for voluntary use and to improve the ability to incorporate trustworthiness considerations into the design, development, use, and evaluation of AI products, services, and systems.

Released on January 26, 2023, the Framework was developed through a consensus-driven, open, transparent, and collaborative process that included a Request for Information, several draft versions for public comments, multiple workshops, and other opportunities to provide input. It is intended to build on, align with, and support AI risk management efforts by others.

A companion NIST AI RMF Playbook also has been published by NIST along with an AI RMF Roadmap, AI RMF Crosswalk, and various Perspectives. In addition, NIST is making available a video explainer about the AI RMF.

MIT recognizes that the value in published scholarship originates in the labor of authors, peer reviewers, and editors, and the institutions that support them. The benefits to society are greatest when this scholarship is freely and immediately available to the entire world to access, read, and use; without restriction and for any lawful purpose.

As MIT continues to lead in transforming scholarly communications from a system focused primarily on paywalled journal articles towards a system providing open access to the products of the full research life-cycle, many MIT scholars continue to value the services provided by journals and journal publishers. Those services include, but are not limited to, editorial oversight, curation, and coordination of the submission and peer review processes. Increasingly, scholars also value the availability of scholarly content as a corpus that is stored, described, and accessible for non-consumptive, computational access and analysis.

The MIT Libraries seek to provide services that enhance the use, reuse, analysis, discovery, curation, and preservation of those outputs. In a rapidly evolving scholarly communications landscape, such services may be offered by commercial, non-profit, or community-owned platforms and resources. We will strive for a portfolio of services that meets the needs of our scholars, reflects core MIT principles and values, and advances the public good and the progress of science.

The MIT Framework creates a mechanism for ensuring scholarly research outputs are openly and equitably available to the broadest and most inclusive audience possible, while also providing valued services to our community. The vision we seek to advance through the application of this framework is one in which enduring, abundant, equitable, and meaningful access to scholarship serves to empower and inspire humanity.

MIT intends to rely on this Framework as a guide for our relationships with publishers regardless of the actions of any of our peer institutions or other organizations. We are, however, delighted that the following institutions have decided that that these principles will advance open scholarship and the public good, and have therefore decided to endorse this Framework:

While California is engaging in litigation to restore its authority to protect the public health of its residents, it has finalized with six participating automakers individual bilateral agreements based upon the Framework unveiled last year.

Automakers who voluntarily agreed to the framework agreements are BMW of North America (including Rolls Royce for purposes of the agreement), Ford, Honda, Volkswagen Group of America (including VW and Audi), and Volvo.

The framework agreements are voluntary commitments that support continued annual reductions of vehicle greenhouse gas emissions through the 2026 model year, encourage innovation to accelerate the transition to electric vehicles, provide industry the certainty needed to make investments and create jobs, and save consumers money.

Each of the automobile manufacturers that have finalized Framework agreements have made additional and individual commitments to expedite the transition to zero-emission vehicles. These agreements, designed to further advance innovation and investment, are memorialized in a separate appendix for each company, and are designated as Confidential Business Information because they relate to specific model production plans and similar matters. Generally they promote enhanced distribution of zero-emission vehicles.

Under the framework agreements, gasoline and diesel cars and light trucks will get cleaner through 2026 at about the same rate as the former Obama-era program, preventing hundreds of millions of tons of greenhouse gas emissions over the lifetime of the agreements.

Cross-border capital flows provide significant benefits but may also generate or amplify shocks. Small open economies can be particularly vulnerable to swings in international capital flows. How should they respond? The traditional answer has been to use flexible exchange rates as a shock absorber. But flexible exchange rates may not offer full insulation from external shocks, for example, when financial markets do not work perfectly.

As a result, policy makers often reach for a mix of tools including intervention in the currency market, and macroprudential and capital flow management measures. These policy responses vary substantially across countries and over time. A significant shortcoming of this eclectic approach is the lack of clear frameworks.

To support and reinforce institutional capacity to intentionally serve, Excelencia developed a framework that integrates essential components of transformation into a comprehensive institutional strategy for SERVING students. This framework represents learning from over 20 years of working with higher education institutions.

Excelencia is committed to working in partnership with institutions to share and learn strategies that align data, practice, and leadership as a community of learners to accelerate Latino student success. Further, we recognize that developing the ability to serve Latino students enhances the capacity of institutions to serve all students.

The .NET Framework (pronounced as "dot net") is a proprietary software framework developed by Microsoft that runs primarily on Microsoft Windows. It was the predominant implementation of the Common Language Infrastructure (CLI) until being superseded by the cross-platform .NET project. It includes a large class library called Framework Class Library (FCL) and provides language interoperability (each language can use code written in other languages) across several programming languages. Programs written for .NET Framework execute in a software environment (in contrast to a hardware environment) named the Common Language Runtime (CLR). The CLR is an application virtual machine that provides services such as security, memory management, and exception handling. As such, computer code written using .NET Framework is called "managed code". FCL and CLR together constitute the .NET Framework.

FCL provides the user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. Programmers produce software by combining their source code with the .NET Framework and other libraries. The framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces an integrated development environment for .NET software called Visual Studio.

.NET Framework began as proprietary software, although the firm worked to standardize the software stack almost immediately, even before its first release. Despite the standardization efforts, developers, mainly those in the free and open-source software communities, expressed their unease with the selected terms and the prospects of any free and open-source implementation, especially regarding software patents. Since then, Microsoft has changed .NET development to more closely follow a contemporary model of a community-developed software project, including issuing an update to its patent promising to address the concerns.[2]

In April 2019, Microsoft released .NET Framework 4.8, the last major version of the framework as a proprietary offering, followed by .NET Framework 4.8.1 in August 2022. Only monthly security and reliability bug fixes to that version have been released since then. No further changes to that version are planned. The .NET Framework will continue to be included with future releases of Windows and continue to receive security updates, with no plans to remove it as of November 2023.[3]

Microsoft began developing .NET Framework in the late 1990s, originally under the name of Next Generation Windows Services (NGWS), as part of the .NET strategy. By early 2000, the first beta versions of .NET 1.0 were released.

In August 2000, Microsoft, and Intel worked to standardize Common Language Infrastructure (CLI) and C#. By December 2001, both were ratified ECMA standards.[4][5] International Organization for Standardization (ISO) followed in April 2003. The current version of ISO standards are ISO/IEC 23271:2012 and ISO/IEC 23270:2006.[6][7]

While Microsoft and their partners hold patents for CLI and C#, ECMA and ISO require that all patents essential to implementation be made available under "reasonable and non-discriminatory terms". The firms agreed to meet these terms, and to make the patents available royalty-free. However, this did not apply to the part of the .NET Framework not covered by ECMA-ISO standards, which included Windows Forms, ADO.NET, and ASP.NET. Patents that Microsoft holds in these areas may have deterred non-Microsoft implementations of the full framework.[8]

c80f0f1006