Högskolan i Skövde

Technological progress poses unique challenges for the public sector. New technology should be adopted, but it must always be done within the framework of good administration. It follows laws governing public administration must be continuously adapted. Sweden recently amended its secrecy legislation to facilitate the use of third-party cloud solutions by public authorities. When the amendment was enacted, most public sector organisations had already been using external cloud solutions for a long time. Today, there is as much pressure on authorities to implement AI technology as there ever was to move administration into the cloud. This paper uses traditional legal methodology to investigate if the Swedish secrecy legislation adequately enables the use of cloud-based GenAI solutions. Findings indicate that the recent amendment is likely insufficient and that there are significant practical hurdles for the application of the law, particularly with services from global cloud providers. The paper contributes to the understanding of Swedish law, and of the difficulties that can occur anywhere when policy makers and legislators do not move in tandem.

The importance of standards, and especially ICT standards, in the IoT domain is widely recognised. Implementations of standard specifications provided as Open Source Software (OSS) promote interoperability and longevity of systems and create conditions for avoiding lock-in, and industrial involvement is important since it can affect community dynamics and will to contribute. The overarching goal of this study is to characterize the industrial leadership and involvement in the LwM2M (Lightweight machine to machine) ecosystem. Specifically, the main focus of the study is on involvement with OSS projects implementing LwM2M elements by individuals who cooperate in projects that implement or use the LwM2M standard in their projects. This can be done by analyzing the commits to the git repository, the bugs issued and commented in the bug-tracking system and the pull requests performed in the project. Techniques will be applied to merge authors using different identities (i.e., different e-mail addresses). By means of identifying the affiliation of those individuals we plan to analyze the involvement of companies in those projects, and thus how they are present in an IoT standard, in this case LwM2M.

Software reference implementations of ICT standards have an important role for verifying that a standard is implementable, supporting interoperability testing among other implementations, and providing feedback to the standard development process. Providing reference implementations and widely used implementations of a standard as Open Source Software promotes wide deployment in software systems, interoperability, longevity of systems and associated digital assets, and avoidance of different lock-in effects. In this paper results are reported on the availability of, and perceptions and practices concerning, reference implementations and widely deployed implementations provided as Open Source Software for standards issued by different standards setting organisations. Specifically, findings draw from observations and analyses related to software implementations for identified standards and policy statements, issued by ETSI, IEC, IEEE, IETF, ISO, ITU-T, OASIS, and W3C.

Software reference implementations of ICT standards have an important role for verifying that a standard is implementable, supporting interoperability testing among other implementations, and providing feedback to the standard development process. Providing reference implementations and widely used implementations of a standard as Open Source Software also promotes wide deployment in software systems, avoidance of different lock-in effects, interoperability, and longevity of systems and associated digital assets. In this paper results are reported on the availability of reference implementations and widely deployed implementations provided as Open Source Software for standards issued by different standards setting organisations. Specifically, findings draw from observations and analyses related to software implementations for identified standards issued by ETSI, IEC, IEEE, IETF, ISO, ITU-T, OASIS, and W3C.

Reproducible builds (R-Bs) are software engineering practices that reliably create bit-for-bit identical binary executable files from specified source code. R-Bs are applied in someopen source software (OSS) projects and distributions to allow verification that the distrib-uted binary has been built from the released source code. The use of R-Bs has been advo-cated in software maintenance and R-Bs are applied in the development of some OSS secu-rity applications. Nonetheless, industry application of R-Bs appears limited, and we seekto understand whether awareness is low or if significant technical and business reasonsprevent wider adoption. Through interviews with software practitioners and business man-agers, this study explores the utility of applying R-Bs in businesses in the primary and sec-ondary software sectors and the business and technical reasons supporting their adoption.We find businesses use R-Bs in the safety-critical and security domains, and R-Bs are valu-able for traceability and support collaborative software development. We also found thatR-Bs are valued as engineering processes and are seen as a badge of software quality, butwithout a tangible value proposition. There are good engineering reasons to use R-Bs inindustrial software development, and the principle of establishing correspondence betweensource code and binary offers opportunities for the development of further applications.

Open hardware and open source software platforms bring benefits to both implementers and users in the form of system adaptability and maintainability, and through the avoidance of lock-in, for example. Development of the \riscv\ Instruction Set Architecture and processors during the last ten years has made the implementation of a desktop computer using open hardware, including open processors, and open source software an approaching possibility. We use the SiFive Unmatched development board and Ubuntu Linux, and the recorded experiences of system builders using the Unmatched board to explore the extent to which it is possible to create an open desktop computer. The work identifies current limitations to implementing an open computer system, which lie mainly at the interface between the operating system and hardware components. Potential solutions to the challenges uncovered are proposed, including greater consideration of openness during the early stages of product design. A further contribution is made by an account of the synergies arising from open collaboration in a private-collective innovation process.

Component-Based Software Development is a conventional way of working for software-intensive businesses and OpenSource Software (OSS) components are frequently considered by businesses for adoption and inclusion in softwareproducts. Previous research has found a variety of practices used to support the adoption of OSS components, in-cluding formally specified processes and less formal, developer-led approaches, and that the practices used continue todevelop. Evolutionary pressures identified include the proliferation of available OSS components and increases in thepace of software development as businesses move towards continuous integration and delivery. We investigate workpractices used in six software-intensive businesses in the primary and secondary software sectors to understand currentapproaches to OSS component adoption and the challenges businesses face establishing effective work practices to eval-uate OSS components. We find businesses have established processes for evaluating OSS components and communitiesthat support more complex and nuanced considerations of the cost and risks of component adoption alongside matterssuch as licence compliance and functional requirements. We also found that the increasing pace and volume of softwaredevelopment within some businesses provides pressure to continue to evolve software evaluation processes.

Open source software (OSS) and open standards have become increasingly important for addressing challenges related to lock-in, interoperability and long-term maintenance of systems and associated digital assets. OSS projects operate under different conditions and many projects and organisations consider successful governance and strategic involvement with projects to constitute major challenges. Today, many companies seek to establish work practices which facilitate strategic engagement with OSS projects. Based on findings from collaborative research which draws from rich insights and extensive experiences from practice, the paper presents seven actionable strategies for organisations that seek to leverage long-term involvement with OSS projects. 

Real-time communication (RTC) technologies for the web provide opportunities for individuals and organisations to work and collaborate remotely, and the need for such technologies has recently increased. Use of RTC technologies and tools for the web involves a number of challenges concerning data privacy and lock-in effects, such as dependency to specific suppliers and proprietary technologies. Use of open standards for RTC and open source software (OSS) implementing such standards can create conditions for avoiding issues related to data privacy and lock-in, and thereby provides opportunities for long-term sustainable solutions. The paper characterises how engagement with standardisation of WebRTC in the context of IETF and W3C is related to engagement with the WebRTC OSS project.