05.07.2014 Views

here - OSTA - Optical Storage Technology Association

here - OSTA - Optical Storage Technology Association

here - OSTA - Optical Storage Technology Association

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1. Introduction<br />

The <strong>OSTA</strong> Universal Disk Format (UDF ® ) specification defines a subset of the standard<br />

ECMA 167 3 rd edition. The primary goal of the <strong>OSTA</strong> UDF is to maximize data<br />

interchange and minimize the cost and complexity of implementing ECMA 167.<br />

To accomplish this task this document defines a Domain. A domain defines rules and<br />

restrictions on the use of ECMA 167. The domain defined in this specification is known<br />

as the “<strong>OSTA</strong> UDF Compliant” domain.<br />

This document attempts to answer the following questions for the structures of ECMA<br />

167 on a per operating system basis:<br />

Given some ECMA 167 structure X, for each field in structure X answer the<br />

following questions for a given operating system:<br />

1) When reading this field: If the operating system supports the data in<br />

this field then what should it map to in the operating system?<br />

2) When reading this field: If the operating system supports the data in<br />

this field with certain limitations then how should the field be interpreted<br />

under this operating system?<br />

3) When reading this field: If the operating system does NOT support the<br />

data in this field then how should the field be interpreted under this<br />

operating system?<br />

4) When writing this field: If the operating system supports the data for<br />

this field then what should it map from in the operating system?<br />

5) When writing this field: If the operating system does NOT support the<br />

data for this field then to what value should the field be set?<br />

For some structures of ECMA 167 the answers to the above questions were selfexplanatory<br />

and t<strong>here</strong>fore those structures are not included in this document.<br />

In some cases additional information is provided for each structure to help clarify the<br />

standard.<br />

This document should help make the task of implementing the ECMA 167 standard<br />

easier.<br />

To be informed of changes to this document please fill out and return the <strong>OSTA</strong> UDF<br />

Developers Registration Form located in appendix 6.16.<br />

UDF 2.01<br />

1<br />

March50 April

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!