Previous section.

Network Computer CAE Specification
Copyright © 1997 The Open Group

Introduction

Scope

This document provides the technical specification for the class of devices known as Network Computers. It identifies the minimum set of requirements which must be met by a product in order for that product to conform to the Network Computer (NC) Product Standard (see reference NC Product Standard).

Positioning

A rich heritage of open systems standards in a dynamic and heterogeneous computing environments led to the evolution of the Internet and network computing as it now exists.

As the focus on the Internet, Intranets, and this network computing environment, continues to increase, a number of emerging technologies and potential standards will emerge, both open and proprietary, competing for acceptance. Along with this will come a growing variety of network-attached devices, which will implement various combinations of these standards.

As consumers, developers, manufacturers, corporations, education, government, service providers, and others, approach this complex and sometimes confusing landscape, it will be beneficial if a common set of standards exists which facilitates:

This NC Specification is aimed at promoting this objective. It provides an entry-level definition for a foundation NC, to define common sets of popular and widely used features and functions across a broad range of scaleable network computing devices, including personal computers. It is flexible, architecturally neutral, and is intended to facilitate the growth of network computers while helping to protect investments made by customers and by content, system, service, and application providers. It encourages interoperability with servers, and facilitates development of a broad application base to run on compliant devices. It also provides guidelines to content and service providers for designing and building applications, and other Internet content which will interoperate with NC-standard-compliant devices.

This specification does not define a complete implementation for a network computer, nor does it preclude provision of additional features and functions outside the scope of the foundation NC.

Network computers are expected to be highly scaleable and to span a product range from the palmtop to the desktop. They attach to the network and interoperate with other network nodes and network content in an IP-based network. They are end-user devices.

Network computers conforming to this specification support a common Java-based execution environment, enabling network-resident applications, as well as stand-alone applications, to execute on them. They are typically dependent on the network, but may offer stand-alone functionality.

This NC Specification is an open systems specification, meaning that it defines an open standard which can be fully implemented from the information included in this document and referenced by this document. It has no dependency on any other information or proprietary technology.

This NC Specification is an "open systems" specification, meaning that it defines an open standard which can be fully implemented from the information included in this document and referenced by this document. It has no dependency on any other information or proprietary technology.

NC and PC

Network computers are not intended to replace personal computers. Today's personal computers are fully capable of satisfying the requirements of this specification. However, unlike personal computers, network computers are designed from the outset with the network, Internet, and Intranets in mind. Additionally, network computers which comply with this Profile are intended to have the following attributes:

Overriding Standards

All formal standards included within this Network Computer specification are specified by a direct reference to the formal standard document itself.

These are identified in the list of Referenced Documents in the front pages of this specification.

Compliance Considerations

The NC Brand

A Network Computer product that meets the functional requirements as defined in the relevant NC Product Standard can be submitted with an application to The Open Group for award of the corresponding NC Brand.

Any NC product which satisfies the mandatory parts of this NC specification may expect to satisfy the conformance requirements for the NC Brand. If any optional NC facilities defined in this specification are included in an NC product, then those facilities must be implemented as defined in this NC specification.

Conformant products may also provide additional standards-based or proprietary services, so long as the mandatory conformance requirements continue to be met, or an environment in which these requirements are met can be configured by a user.

In all cases, the definitive conformance requirements are specified in the applicable NC Product Standard.

The process to apply for award of an NC Brand is described in information linked from The Open Group's NC public Web page (http://www.opengroup.org/nc/).

NC Product Standards

The conformance requirements for an NC product are defined in an NC Product Standard.

It is clear that the market will demand a variety of network computer products to satisfy the differing requirements in a number of market areas.

It is desirable that all these Network Computers support a foundation level of functionality and standards, and that classes of devices, which may provide unique features and functions specific to their particular market, do so consistently, and where possible are based upon the same common foundation of open systems standards.

Accordingly, future versions of this NC Specification will build from the foundation NC, to define additional functionality.

As the set of NC functional components increases, new NC Product Standards will be generated to define conformance requirements for higher-functionality NC products. In addition, one NC Product Standard may call up other NC Product Standards, so enabling various combinations of functionality to be defined. Thus, a range of NC Product Standards will emerge, to meet market demand for the NC Brand for various configurations of NC products, for general use and for specific vertical markets. These NC Product Standards will coexist. The foundation NC Product Standard will be a fundamental component included in all higher-functionality NC Product Standards.

Terminology

The following terms are used in this specification:

can

This describes a permissible optional feature or behaviour available to the user or application; all systems support such features or behaviour as mandatory requirements.

implementation-dependent

The value or behaviour is not consistent across all implementations. The provider of an implementation normally documents the requirements for correct program construction and correct data in the use of that value or behaviour. When the value or behaviour in the implementation is designed to be variable or customisable on each instantiation of the system, the provider of the implementation normally documents the nature and permissible ranges of this variation. Applications that are intended to be portable must not rely on implementation-dependent values or behaviour.

may

With respect to implementations, the feature or behaviour is optional. Applications should not rely on the existence of the feature. To avoid ambiguity, the reverse sense of may is expressed as need not, instead of may not.

must

This describes a requirement on the application or user.

shall

This means that the behaviour described is a requirement on the implementation and applications can rely on its existence. See also "will".

should

With respect to implementations, the feature is recommended, but it is not mandatory. Applications should not rely on the existence of the feature.

With respect to users or applications, the word means recommended programming practice that is necessary for maximum portability.

undefined

A value or behaviour is undefined if this document imposes no portability requirements on applications for erroneous program constructs or erroneous data. Implementations may specify the result of using that value or causing that behaviour, but such specifications are not guaranteed to be consistent across all implementations. An application using such behaviour is not fully portable to all systems.

unspecified

A value or behaviour is unspecified if this document imposes no portability requirements on applications for correct program construct or correct data. Implementations may specify the result of using that value or causing that behaviour, but such specifications are not guaranteed to be consistent across all implementations. An application requiring a specific behaviour, rather than tolerating any behaviour when using that functionality, is not fully portable to all systems.

will

This means that the behaviour described is a requirement on the implementation and applications can rely on its existence.

Contents Next section Index