Draft Requirements Strawman AUSTIN-5 This document is a set of requirements for consideration in production of a common standard. Backward compatibility. It has been agreed that there should be no breakage of functionality in the existing base documents. (need to add quotes in from the pasc adhoc) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Extensibility. Consideration needs to be made on how extensions can be layered onto the common standard. It has been agreed that there will be no amendments to this common standard , in future changes will be handled through the revision process. A set of recommendations will be produced to describe how extensions can be layered, for example, rather than incrementing _POSIX_VERSION, a layered extension should introduce its own feature macro to announce its presence. Scalability Todays systems need to scale to support larger numbers of users, disk space and system resources. The common standard should be reviewed for any built in limitations, and should look to provide scalable functionality. Considerations need to be made with Backward compatibility {at the moment this appears to be too broad a requirement} dev_t is an integral datatype, ISO C limits this to 32-bits n-bit neutral. The common standard should not make any implicit assumptions about the size of data types, for example previously some 32-bit implicit assumptions had crept into the standards. Architecture neutrality. Consistency