Does GPLv2 Include an ‘Installation Information’ Obligation? A Textual & Historical Analysis

One of the features included in version 3 of the GNU General Public License (GPLv3) was a requirement, in certain circumstances, to provide ‘Installation Information.’ This was a new addition to the licence to address a ‘loophole’ that existed in version 2 of the licence (GPLv2); a loophole that was perceived as being exploited, at the time, by certain device vendors. Recently, it has been asserted that this requirement was inherent, or explicitly called for, in GPLv2. This paper examines the historical record around the time that the ‘Installation Information’ requirement was proposed, and eventually ratified, in GPLv3, to show that this requirement was understood to be both new, and not a part of GPLv2. A textual analysis of GPLv2 yields an identical result.

Does GPLv2 Include an ‘Installation Information’ Obligation? A Textual & Historical Analysis

One of the features included in version 3 of the GNU General Public License (GPLv3) was a requirement, in certain circumstances, to provide ‘Installation Information.’ This was a new addition to the licence to address a ‘loophole’ that existed in version 2 of the licence (GPLv2); a loophole that was perceived as being exploited, at the time, by certain device vendors. Recently, it has been asserted that this requirement was inherent, or explicitly called for, in GPLv2. This paper examines the historical record around the time that the ‘Installation Information’ requirement was proposed, and eventually ratified, in GPLv3, to show that this requirement was understood to be both new, and not a part of GPLv2. A textual analysis of GPLv2 yields an identical result.

The Correlation between the Commander’s CBRN Expertise and the Commander’s Crucial Information Requirement

The CBRN environment of joint operations determines that future joint operations are to be planned and commanded in a way that considers the risks posed by CBRN weapons against the forces participating in such operations. In addition to that, materials detrimental to the health of personnel may be released from destroyed industrial plants and nuclear facilities. Consequently, friendly forces shall prepare not just for the protection against conventional attacks, but also for CBRN incidents to. The commander’s critical information requirement has great importance during the operations planning period, and CBRN proficiency is critical in analyzing various sets of CBRN information.

Information Requirement in the Transition Towards a Circular Fashion Industry

Management of fashion (related) companies need to become convinced that circularity delivers positive financial results and incentives. This research aims to provide the first information requirement insights needed to enable the transition to a circular fashion industry. Due to easy access and abundant information ‘Jeans’ were selected as example item. Using the Design Science research approach the required information within in a closed loop supply chain (CLSC) in fashion was derived. Semi-structured interviews validated the CLSC information requirements derived from literature. Next, observations and additional literature findings supported the interview results. The outcomes show that information to support integration and collaboration of both: supply and recycle chain is necessary. Independently operating recycle organizations miss ‘central loop management’, ‘information integration’ and ‘a chain-common objective’ to successfully adopt circularity. The main bottlenecks found in relation to circularity are: ‘overlooking the customer as stakeholder’ and ‘a lack of chain integration’, this applies not only to jeans items. Therefore, the indicative study outcomes contribute to the body of knowledge of circular fashion value chain information requirements in general.

Requirement management in a life cycle perspective based on ISO 19650-1 and CoClass as the new classification system in Sweden

PurposeEach building project demands an integrated method for information and requirement management in its life cycle. The main purpose of this paper is to explore the major obstacles in integrated life cycle information management and recognize the potentials of CoClass as the new Swedish digital classification system to tackle them throughout asset life cycle.Design/methodology/approachThe industry viewpoint toward the current status of asset information management considering ISO 19650-1 principles and the existing obstacles and the industry practitioners' ideas regarding CoClass capabilities and applicability were captured and analyzed. A total of 13 semistructured interviews were conducted with the AECO industry professionals to have an understanding of information requirement management. Then the results were analyzed qualitatively, using the NVivo 12 software. Different attributes of a component (heating panel) in a meeting room according to CoClass and data deviations throughout the asset life cycle were elaborated.FindingsThis study reveals some obstacles in information management process in seven categories in relation to: (1) the need to employ information exchange platforms as common data environments (CDEs) by all actors from early stages; (2) the communication issues caused by lack of utilizing common languages; (3) the costly and time-consuming implementation process; (4) the misunderstandings in terms of data communication between service providers and owners; (5) the definition and fulfillment of information requirements as well as keeping track of data deviations throughout asset life cycle; (6) the information update difficulty; and (7) the need for training practitioners dealing with new systems such as CoClass.Originality/valueThe research explores the major obstacles in information requirement management concerning the practical implementation of the new Swedish classification system, CoClass, supporting the asset life cycle.

Balancing Expressiveness and Inexpressiveness in View Design

We study the design of data publishing mechanisms that allow a collection of autonomous distributed datasources to collaborate to support queries. A common mechanism for data publishing is via views: functions that expose derived data to users, usually specified as declarative queries. Our autonomy assumption is that the views must be on individual sources, but with the intention of supporting integrated queries. In deciding what data to expose to users, two considerations must be balanced. The views must be sufficiently expressive to support queries that users want to ask -- the utility of the publishing mechanism. But there may also be some expressiveness restriction. Here we consider two restrictions, a minimal information requirement, saying that the views should reveal as little as possible while supporting the utility query, and a non-disclosure requirement, formalizing the need to prevent external users from computing information that data owners do not want revealed. We investigate the problem of designing views that satisfy both an expressiveness and an inexpressiveness requirement, for views in a restricted declarative language (conjunctive queries), and for arbitrary views.

How are US institutions implementing the new key information requirement?

Recent revisions to the Federal Policy for the Protections of Human Subjects require that informed consent documents begin with a “concise and focused presentation” of the key information a participant requires. Key information “must be organized and presented in a way that facilitates comprehension.” The regulations do not specify what information be included, nor how it must be presented to facilitate comprehension. It is unknown how institutions and Institutional Review Boards (IRBs) are interpreting the current regulations. We conducted a review of randomly sampled available key information templates at 46 US medical institutions to determine how they are implementing the new regulations.