OPC definitions (thoroughly restructured)

[MURATA Makoto]

Dear colleagues,

I am still struggling to improve Clause 9.  To do so, I
think that we should revisit definitions.

I had a look at Directives, Part 2.  It says:

Terms and definitions should preferably be listed according to the
hierarchy of the concepts (i.e. systematic order). Alphabetical order is
the least preferred order.

EXAMPLE 2

3    Terms and definitions

[…]

3.2    Surface properties

3.2.1
abrasion
loss of material from a surface due to frictional forces

[…]

3.5    Optical properties

[…]

3.5.8
colour retention
degree of permanence of a colour

Note 1 to entry:    Colour retention can be influenced by weathering.
I tried to follow this guideline in the following new set of definitions.

Your comments are very welcome.

Regards,
Makoto


4. Terms and Definitions

****


4.1 Basics

4.1.1
byte
sequence of 8 bits treated as a unit

4.1.2
stream
linearly ordered sequence of bytes
4.1.3
device
hardware, such as a personal computer, printer, or scanner,
that performs a single function or set of functions
4.1.4
behavior
external appearance or action

4.1.5
behavior, implementation-defined
behavior, application-defined
unspecified behavior where each implementation shall document that
behavior, thereby promoting predictability and reproducibility within any
given implementation

4.1.6
behavior, unspecified
behavior where this document imposes no requirements


4.2 Abstract package model


4.2.1
part
stream with a name, a MIME media type, and associated common properties

4.2.2
package, abstract
container that holds a collection of parts

4.2.3
relationship
package relationship or part relationship

4.2.4
relationship, package
connection from a package to a specific part in the same
package, or to an external resource

4.2.5
relationship, part
connection from a part in a package to another part in the
same package, or to an external resource

4.2.6
source
part or package from which a connection is established by a relationship

4.2.7
target
part or external resource to which a connection is established by a
relationship

4.2.8
relationship type
absolute IRI for specifying the role of a relationship

4.2.9
Relationships part
part containing an XML representation of relationships

4.2.10
package model, abstract
abstract model that defines packages

4.2.11
growth hint
suggested number of bytes to reserve for a part to grow in place

4.2.12
pack scheme
URI scheme that allows IRIs to be used as a uniform mechanism
for addressing parts within a package

4.2.13
pack IRI
IRI that conforms to the pack scheme


4.3 physical package model

4.3.1
physical format
specific file format, or other persistence or transport mechanism

4.3.2
package, physical
the result of mapping an abstract package to a physical format

4.3.3
package model, physical
a pair of a physical format and a mapping between the abstract
package model and this physical format

4.3.4
piece
portion of a part.

4.3.5
logical item
either a non-interleaved part or a piece of an interleaved part

4.3.6
physical package item
To be supplied.

4.3.7
ZIP item
    an atomic set of data in a ZIP file that becomes a file when the
archive is uncompressed

4.3.8
ZIP file
    ZIP file as defined in the ZIP file format specification

4.3.9
simple ordering
       defined ordering for laying out the parts in a package in which
       all the bits comprising each part are stored contiguously
4.3.10
interleaved ordering
defined ordering for laying out the parts in a package in
which parts are broken into pieces and “mixed-in” with
pieces from other parts

4.4 digital signature and thumnail

4.4.1

signature policy
  format-defined policy that specifies what configuration of
  parts and relationships shall or might be included in a
  signature for that format and what additional behaviors that
  producers and consumers of that format shall follow when
  applying or verifying signatures following that format's
  signature policy

4.4,2
thumbnail
small image that is a graphical representation of a part or the package as
a whole

4.5 Implementations

4.5.1
package implementer

software that implements the physical input-output operations
to a physical package according to the requirements and
recommendations of this document

4.5.2
consumer
software or device that reads physical packages through a package
implementer

4.5.3
producer
software or device that writes physical packages through a package
implementer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20180602/4107c946/attachment.html>