Project Requests issueshttp://opensource.ieee.org/oscom/official-project-requests/-/issues2024-03-20T14:12:02Zhttp://opensource.ieee.org/oscom/official-project-requests/-/issues/36Authorization to create a new Official IEEE Open Source Project for Person On...2024-03-20T14:12:02ZJames SchoeningAuthorization to create a new Official IEEE Open Source Project for Person Ontology## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Person Ontology
2. Description of the Project: Person Ontology specifies terms and definitions, and relationships amongst them, for the domai...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Person Ontology
2. Description of the Project: Person Ontology specifies terms and definitions, and relationships amongst them, for the domain of the natural person. This ontology is expressed in a formal language that computers
can process and is a conforming extension of P3195.1 (Standard for Common Core Ontology).
3. IEEE Open Source Project lead (or main point of contact):
Name: James Schoening
Email: james.schoening@ieee.org
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [BSD 3-Clause License](https://opensource.ieee.org/community/cla/bsd3)(James Schoening has already signed this CLA for all projects)
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. No
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1. Yes - This project will be run by the Person Ontology Subgroup of the IEEE Ontology Standards Working Group (https://sagroups.ieee.org/oswg/). See PAR P3195.1.2 Person Ontology at https://development.standards.ieee.org/myproject-web/app#viewpar/14375/10540
7. Governance
IEEE Ontology Standards Working Group has approved Policies and Procedures at https://ieee-sa.imeetcentral.com/oswg/folder/WzIwLDE1NzU0NTYxXQ/.2024-03-14http://opensource.ieee.org/oscom/official-project-requests/-/issues/34Convergent Operating Systems2023-10-06T18:50:03ZTodd WeaverConvergent Operating Systems## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Convergent Operating Systems
2. Description of the Project: Operating System that can display to many form factors, monitor, laptop, phone scr...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Convergent Operating Systems
2. Description of the Project: Operating System that can display to many form factors, monitor, laptop, phone screen, etc. from a single code base. This convergence allows for detecting screen size and adapting for the user and input device. We will use the IEEE platform to develop open source software the supports the advancement of this type of OS.
3. IEEE Open Source Project lead (or main point of contact):
Name: Todd Weaver
Email: todd@puri.sm
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [Apache 2.0 License]
* Request use of other license*
We currently use GPL 2 and 3.
5. Will this project use pre-existing Open Source software or hardware? If so, please describe.
Yes, we have open source code and libraries from https://source.puri.sm and various downstream/upstream projects such as GNOME.
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
3. No
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.Josh Gayj.gay@ieee.orgJosh Gayj.gay@ieee.org2023-10-04http://opensource.ieee.org/oscom/official-project-requests/-/issues/339274.2.1 Open Source Project Request (Working Group already exists)2023-10-06T18:47:45ZAndy Johnson9274.2.1 Open Source Project Request (Working Group already exists)## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
Standard for JavaScript Object Notation for Linked Data (JSON-LD) for Application Profiles of Learner Experience Data
2. Description of the P...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
Standard for JavaScript Object Notation for Linked Data (JSON-LD) for Application Profiles of Learner Experience Data
2. Description of the Project:
This project will seek to implement the existing 9274.2.1 PAR but also expand upon it by providing two additional guides. These guides might be considered standards or could just be resources produced by the group. The idea is they are all in the same Open Source repository and the same project. The purpose of this Standard is to provide an interoperable means to implement, automate and validate the semantic structures of learner experience data imbued with meaning for modern, data-intensive learning technologies.
3. IEEE Open Source Project lead (or main point of contact):ab:
Name: Andy Johnson
Email: andy.johnson.ctr@adlnet.gov
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [Apache 2.0 License](https://opensource.ieee.org/community/cla/apache)
*NOTE: Requesting use of another license may include a lengthy review process and acceptance is not guaranteed.
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. \
No
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1/A- Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs. 9274.1.1 (IEEE Standard) and 9274.2.1 (Established PAR and Working Group, to be replaced by this standard). The scope of this project was limited to ” This Standard describes a JSON-LD format that defines concepts, templates and patterns of learner experience data.” The contribution to the standard is far more than that and needs to be separated into a 1) standard that is in the original scope, 2) best practices for xAPI Profiles, and 3) conformance testing of both data and systems that use profiles of 9274.1.1
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
NO – We plan on using standard IEEE LTSC Governance2023-10-04http://opensource.ieee.org/oscom/official-project-requests/-/issues/32IOR SDK2023-10-17T12:08:48ZDaozhuang LinIOR SDK## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
IOR SDK
2. Description of the Project:
IOR SDK is an SDK for developers to access IOR services. It provides the encapsulation of multiple fun...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
IOR SDK
2. Description of the Project:
IOR SDK is an SDK for developers to access IOR services. It provides the encapsulation of multiple functions, including decentralized certificates, roles, permissions, templates, etc. The IOR SDK also supports asynchronous transaction signatures, which makes private key management at the developer's discretion.
3. IEEE Open Source Project lead (or main point of contact):
Name: Diana Shi
Email: yunlingdshi@gmail.com
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [BSD 3-Clause License](https://opensource.ieee.org/community/cla/bsd3)
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. \
Yes.
Python3:
hexbytes 0.3.0
httpx 0.18.2
py_rest_api_client 0.2.1
setuptools 65.5.0
web3 6.0.0
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1. Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs.
2. Maybe - We are interested in learning more. Please see [IEEE SA - How Are Standards Projects Started?](https://standards.ieee.org/develop/initiating-project/projstart.html) for more information.
3. No
Yes. P3816 WG.
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
YES: URL ________________________
NO2023-10-04http://opensource.ieee.org/oscom/official-project-requests/-/issues/31Create new repo for source code related to STTP / IEEE P26642023-08-01T13:05:28ZJames CarrollCreate new repo for source code related to STTP / IEEE P2664## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: STTP
2. Description of the Project: The Streaming Telemetry Transport Protocol (STTP) is optimized for the demands of transporting high volu...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: STTP
2. Description of the Project: The Streaming Telemetry Transport Protocol (STTP) is optimized for the demands of transporting high volume continuous streaming data and related metadata. The protocol allows for the transmission of any information that can be represented longitudinally, e.g., time-series data.
This repo will host source code referenced by the IEEE 2664 standard, e.g., the C++ implementation of the Time Series Special Compression (TSSC) algorithm and grammar used for generating filter expression parsers.
3. IEEE Open Source Project lead (or main point of contact):
Name: James Ritchie Carroll
Email: ritchiecarroll@gmail.com (rcarroll@gridprotectionalliance.org)
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [BSD 3-Clause License](https://opensource.ieee.org/community/cla/bsd3)
*NOTE: Requesting use of another license may include a lengthy review process and acceptance is not guaranteed.
5. Will this project use pre-existing Open Source software or hardware? No
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
Yes: https://standards.ieee.org/ieee/2664/7397
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
NO: No document exists yet2023-07-27http://opensource.ieee.org/oscom/official-project-requests/-/issues/30Open source the P31672023-06-27T20:18:47ZSasikumar GanesanOpen source the P3167## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Secure Biometrics Device Interface Specification
2. Description of the Project: This standard specifies a language-agnostic protocol and corr...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Secure Biometrics Device Interface Specification
2. Description of the Project: This standard specifies a language-agnostic protocol and corresponding interfaces for biometric devices to support features such as the discovery of devices, capabilities exposure of the device and capture of biometrics using the device for all instant capture modalities. This protocol also specifically addresses the trustworthiness of both the device and the captured data in addition to data security.
3. IEEE Open Source Project lead (or main point of contact):
Name: Sasikumar Ganesan
Email: sasi@mosip.io
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [Apache 2.0 License](https://opensource.ieee.org/community/cla/apache)
*NOTE: Requesting use of another license may include a lengthy review process and acceptance is not guaranteed.
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. \
This specification's first draft was derived from the pre-existing MOSIP specification. https://docs.mosip.io/1.1.5/biometrics/mosip-device-service-specification.
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1. Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs.
https://standards.ieee.org/ieee/3167/10925/
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
NO2023-06-22http://opensource.ieee.org/oscom/official-project-requests/-/issues/28IEEE P3330 Shape Expression Schemas Working Group2023-05-30T18:54:45ZKat ThorntonIEEE P3330 Shape Expression Schemas Working Group## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Shape Expression Schemas Working Group
2. Description of the Project: This standard defines the syntax of Shape Expression schemas represente...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Shape Expression Schemas Working Group
2. Description of the Project: This standard defines the syntax of Shape Expression schemas represented in JavaScript Object Notation (JSON), Resource Description Framework (RDF), and plain text. Shape Expressions (ShEx) is a structural schema language for RDF graphs that expresses structural requirements for terms and relationships in a graph. This standard includes formal semantics for validation of RDF knowledge graphs using ShEx. This validation process includes the definition of ShapeMaps to associate nodes in RDF graphs with labeled ShEx. A test suite covers all aspects of syntax and validation.
3. IEEE Open Source Project lead (or main point of contact):
Name: Katherine Thornton
Email: katherine.thornton@yale.edu
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [Apache 2.0 License](https://opensource.ieee.org/community/cla/apache)
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. \
Yes. This project will use implementations of the Shape Expressions language.
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1. Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs.
PAR 3330
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
NO2023-05-25http://opensource.ieee.org/oscom/official-project-requests/-/issues/27Open Source the Soon-to-be-kicked off 9274.3.12023-10-04T14:38:59ZAndy JohnsonOpen Source the Soon-to-be-kicked off 9274.3.1## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Standard for Packaging, Launch, and Run-time of Experience Application Programming Interface (xAPI) in Session-based Learning
2. Description ...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project: Standard for Packaging, Launch, and Run-time of Experience Application Programming Interface (xAPI) in Session-based Learning
2. Description of the Project: A standard is needed to define a data model format and communication protocol for learning experience data allowing vendors to build interoperable solutions and to take advantage of many products that support the xAPI. Learning Management Systems (LMSs) as they currently exist in the marketplace do not have semantic data interoperability through xAPI alone, nor are there standards for content delivery or structure. The result is that LMSs push content development requirements in a non-standard way towards content developers, such that developers create content that does not work in an LMS. Thus, there is a need of a standard is to provide an interoperable means to store and retrieve learning experience data as required by modern, data-intensive learning technologies and in the current paradigm of an authenticated learner registering for learning content within a learning management system and experiencing that content with their progress being tracked.
3. IEEE Open Source Project lead (or main point of contact):
Name: Andy Johnson
Email: andy.johnson.ctr@adlnet.gov
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [Apache 2.0 License](https://opensource.ieee.org/community/cla/apache)
*NOTE: Requesting use of another license may include a lengthy review process and acceptance is not guaranteed.
5. Will this project use pre-existing Open Source software or hardware? If so, please describe. \ No, but it is contingent on another IEEE standard (9274.1.1)
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
1. Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs. PAR - [9274.3.1](https://development.standards.ieee.org/myproject-web/app#viewpar/14022/10264)
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures. (Yes - Andy Johnson)
We have an existing governance document that we are submitting for review at this time (pick one):
NO2023-05-25http://opensource.ieee.org/oscom/official-project-requests/-/issues/26Digital Transformation of Pandemic Surveillance2023-04-03T13:46:53ZGrace LiDigital Transformation of Pandemic Surveillance## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
Digital Transformation of Pandemic Surveillance
2. Description of the Project:
This Project is part of the IEEE SA Industry Connections Activ...## Authorization to create a new Official IEEE Open Source Project
1. Title of the Project:
Digital Transformation of Pandemic Surveillance
2. Description of the Project:
This Project is part of the IEEE SA Industry Connections Activity IC20-005 Global Initiative on Digital Transformation of Pandemic Surveillance. The goal is to improve the efficiency and transparency of pandemic surveillance by building a platform that integrates the data interfaces of multiple industries (not only healthcare, but also other industries such as travel & transportation, telecommunications, retail, etc.) to better detect and respond to a pandemic.
3. IEEE Open Source Project lead (or main point of contact):
Name: Grace Li
Email: grace.xd.li@ieee.org
4. Selection of a single Open Source approved license and associated CLAs (See the [Maintainers Manual](https://opensource.ieee.org/community/manual#82-licensing-and-control-of-contribution )):
* [BSD 3-Clause License](https://opensource.ieee.org/community/cla/bsd3)
5. Will this project use pre-existing Open Source software or hardware? If so, please describe.
No.
6. Supporting an IEEE Standards Project (Please Select A, B, or C)
Yes - This project will be run by an IEEE Standards Committee and/or a Working Group. Please list all applicable PARs.
P2677.1, P2677.10, P2677.11, P2677.12, P2677.20, P2677.21, P2677.22, P2677.30, P2677.31, P2677.32
7. Governance
We agree that we will have a governance document for review by the community manager within 30 days and that we will make any modifications necessary to conform to all applicable policies and procedures.
We have an existing governance document that we are submitting for review at this time (pick one):
NO