Applications of information technology

The mission of the Audio Working Group is to add advanced sound and music synthesis capabilities to the Open Web Platform.
 
Building upon and expanding the basic functionalities brought by HTML5's and media elements and MediaStream object, the Audio Working Group defines client-side script APIs which support the features required by rich interactive applications including the ability to process and synthesize audio streams directly in script, as well as giving access to musical instruments through a bridge with existing system-level MIDI APIs.
 
The audio API provides methods to read audio samples, write audio data, create sounds, and perform client-side audio processing and synthesis with minimal latency. It also adds programmatic access to the PCM audio stream for low-level manipulation directly in script. This API can be used for interactive applications, games, 3D environments, musical applications, educational applications, and for the purposes of accessibility. It includes the ability to synchronize, visualize, or enhance sound information when used in conjunction with graphics APIs. Sound synthesis can be used to enhance user interfaces, or produce music. The addition of advanced audio capabilities to user agents presents new options to Web developers and designers, and has many accessibility opportunities and challenges that this working group will continue to keep in mind.
 
In addition to an audio processing API, this group has received feedback from the audio and music community and industry, who wish to Web-enable their MIDI-capable devices. MIDI is an electronic device interface, developed by the musical instrument industry, that includes communication protocols for two-way connection and control of a wide variety of devices, including digital musical instruments, digital audio workstations, lighting sytems, game controllers, and many other systems. The MIDI specification has wide adoption and interoperable deployment across devices and computer operating systems, and to extend this existing infrastructure, the Audio Working Group is also developing a specification to create a bridge between the browser and existing system-level MIDI APIs, to make musical instruments first-class citizens of the Web.
 
The scope of this working group includes:

• Developing a client-side script API for processing and synthesizing PCM audio streams, including direct scripted solutions.
• Access to audio devices, such as for microphones or other audio inputs, and multi-channel speakers or other audio outputs.
• APIs and advanced functionality regarding audio cache management and audio capability information.
• Defining a client-side script API for accessing and manipulating MIDI-capable devices available on the users' systems.

This working group will take into account common work-flows for sound creators, including considerations for common audio formats. This group will also liaise with other groups for direct connection to audio inputs, such as microphones and speakers.
 
The HTML5 specification introduces the

The mission of the Browser Testing and Tools Working Group is to produce technologies for use in testing, debugging, and troubleshooting of Web applications running in Web browsers.
 
The scope of the Browser Testing and Tools Working Group includes protocols and APIs for the purpose of automating testing of Web applications running in browsers—for example, to simulate user actions such as clicking links, entering text, and submitting forms.

The mission of the Automotive Working Group is to develop Open Web Platform specifications for application developers, including but not limited to HTML5/JavaScript, enabling Web connectivity through in-vehicle infotainment systems and vehicle data access protocols. The API is agnostic with regard to the connection used.
 
This group will develop service specifications for exposing vehicle data and other information around vehicle centric functions.
 
A common pattern will be described to unify the style the different service interfaces are using.
 
The specification(s) produced by this Working Group will include security and privacy considerations.
 
Members of the Working Group should review other working groups' deliverables that are identified as being relevant to the Working Group's mission.
 
Services may include but are not limited to

• Vehicle Data
  • vehicle brand, model, year, fuel type, transmission type, steering wheel position, tire pressure, oil level, wiper position, lights, doors, windows and seat settings as well as navigation, trip computer data, climate control data, speed, RPMs, acceleration, gears, …
• media
  • media control, track lists, …
• navigation
  • route manipulation, points of interests, …

Standardization of basic characteristics, test methods and other related items of products such as 2D and 3D Printers/Scanners, Copiers, Projectors, Fax and Systems composed of their combinations, excluding such interfaces as user system interfaces, communication interfaces and protocols.

SC 28 is one of the few product or hardware oriented subcommittees in the JTC 1 community. As such fundamental output of this group has been standards on product specification descriptors, methods for measurement of productivity of hardcopy devices, quality of hardcopy output and yield of consumables (ink and toner cartridges). SC 28 will continue the expansion of measurement methods for consumables and productivity. SC 28 will also extend the image quality assessment to support print permanence and durability. In 2015, due to the changing nature of market needs for office equipment and related technologies with increasing usage of 3D technology in the office environments, SC 28 enlarged its scope with including 3D Printers/Scanners. SC 28 will continue to monitor developments for 3D printers/scanners in the office/home space to identify areas for potential development to address customer needs. Not only 3D area, SC 28 starts to align its work program for IoT and accessibility with JTC 1 strategic directions where applicable.

Standardization in the field of information technologies for learning, education, and training to support individuals, groups, or organizations, and to enable interoperability and reusability of resources and tool.

Excluded from this scope are:

• standards or technical reports that define educational standards (competencies), cultural conventions, learning objectives, or specific learning content.
• work done by other ISO or IEC TCs, SCs, or WGs with respect to their component, specialty, or domain. Instead, when appropriate, normative or informative references to other standards shall be included. Examples include documents on special topics such as multimedia, web content, cultural adaptation, and security.

Standardization in the field of document structures, languages and related facilities for the description and processing of compound and hypermedia documents, including:

• languages for describing document logical structures and their support facilities
• languages for describing document-like objects in web environments facilities
• document processing architecture and formatting for logical documents facilities
• languages for describing interactive documents facilities
• multilingual font information interchange and related services facilities
• final-form document architecture and page information interchange facilities
• hypermedia document structuring language and application resources facilities
• API's for document processing

This specification contains the requirements for an implementation of the SM CLP to provide access to, and implement the behaviors of, the Base Server Profile.

The use of containers and microservices have been increasingly implemented in organizations. This increase in popularity can be attributed to the ease with which they move through a lifecycle allows for efficient restart, scale-up or scale-out of applications across clouds. However, these unique characteristics also mean there are distinct security ramifications which must be considered. The mission of the CSA Application Containers and Microservices working group is to conduct research on the security of application containers and microservices and publish guidance and best practices for the secure use of application containers and microservices. This working group is building upon the work done by the joint NIST/CSA Applications Container Security Guidance Developed by the NIST Cloud Security Working Group.

The Enterprise Resource Planning (ERP) WG seeks to develop best practices to enable organizations that run their business on large ERP implementations, such as SAP or Oracle applications, to securely migrate to and operate in cloud environments. Every ERP deployment is something that is unique to each organization. In most cases organizations spend months if not years customizing their SAP or Oracle implementations and also spend a significant amount of money with third party contractors to get the implementations done. This makes standard security measures more difficult to implement due to the differences of each deployment. With the complexity of these large implementations, combined with the criticality of data and processes housed in these applications, it is imperative that industry best practices be established to provide companies with security guidelines when migrating to the cloud in order to protect the organization’s critical infrastructure.

Standardization of graphic character sets and their characteristics, including string ordering, associated control functions, their coded representation for information interchange and code extension techniques. Excluded: audio and picture coding.

SC 2 experts have been working hard to develop Universal Coded Character Set, ISO/IEC 10646, and related standards which are the fundamental basis of Information systems and being referred from every standard involving character-based information exchange and/or processing.

The first version of ISO/IEC 10646 standardized 32,884 characters and published in 1993. Edition 5 of it, the latest version currently under development, will cover over 130,000 characters.

SC2 will keep the quality and speed of its work to develop standards for a character. And close cooperation between SC2 and other all committees to develop standards involving character codes is essential.

Recommendation ITU-T M.3070/Y.3521 presents the conceptual view and the common model of end-to-end (E2E) cloud computing management based on the service management interface (SMI) and cloud computing reference architecture, from the perspective of the telecommunications industry.