Image purpose is a property that states the role an image plays in a descriptive record, such as icon, logo, screenshot, sample rendering or structural diagram.
Registries use it so that interfaces, exports and catalogers can tell an illustrative image from evidence about the format itself.
A logo, a screenshot and a byte-layout diagram can all sit in the same format record, and each says something different. The logo tells a reader which organization’s format this is. The screenshot shows a program that opens it. The diagram explains how the file is built. Image purpose is the property that records which of these jobs an image does, so that the record stays useful when it is displayed, exported or merged with other sources.
Typical purpose values
Vocabularies differ in detail, but the values tend to fall into a handful of groups.
- Icon or logo: identifies a format, a product or the body that maintains a specification. Useful in interfaces, weak as evidence.
- Screenshot: shows software that creates or renders the format, often a specific version, which can matter when a format is defined mainly by its reference implementation.
- Sample rendering: shows what a correctly decoded file looks like. A rendering of a test image, for example, lets a later user check whether a viewer displays it the same way.
- Structure diagram: shows the internal layout, such as headers, chunks, boxes or blocks. These often carry more information than pages of prose.
- Thumbnail: a reduced version of another image, kept for display only.
The general linking property for any of these is foaf:depiction; the purpose value adds the role.
Evidence or decoration
The practical value of the property shows up in the difference between images that document a format and images that only decorate a record. A structure diagram derived from the specification is a form of documentation, and it should be treated like the references a record cites: with a source, a date and a note on which version of the format it describes. A logo is decoration, and nothing in the format’s behavior depends on it.
Sample renderings sit in between. They are useful to anyone testing whether a rendering environment works, for instance in emulation-based access, but only when the record states what software produced the rendering and from which sample file. A screenshot of a PDF in an unnamed viewer proves little; a rendering of a named test file in a named viewer version is a small piece of evidence.
Rights and accessibility
Images in descriptive records raise two practical questions that text fields do not.
Rights. Logos are trademarks of their owners, and screenshots reproduce someone else’s interface. A record should note the source and the terms of use for each image, for which a field like dc:rights is the usual fit. Diagrams drawn by the registry itself are the easiest images to share; reproduced figures from a specification usually come with the specification’s license.
Text alternatives. A diagram that explains a file structure must be readable by someone who cannot see it. Captions and alternative text should describe the content of the diagram (the order and names of the blocks, the sizes of fields), instead of a bare “diagram of GIF”. The purpose value helps here too, since it tells the interface which images need full descriptions and which, like a decorative logo, can carry a short label.
How image evidence fits alongside signatures and specifications is described in the file format identification guide, and the vocabulary index lists the other record properties.
Example in RDF
<format rdf:about="https://example.org/formats/gif-89a">
<name>Graphics Interchange Format 89a</name>
<image>
<imageURI>https://example.org/img/gif89a-structure.svg</imageURI>
<imagePurpose>Structure diagram</imagePurpose>
<caption>Block layout: header, logical screen descriptor, extensions, image data, trailer</caption>
</image>
<image>
<imageURI>https://example.org/img/gif89a-viewer.png</imageURI>
<imagePurpose>Screenshot</imagePurpose>
</image>
</format>
Questions about Image purpose
What does image purpose mean in a metadata record?
It names the job an attached image does in that record: identifying a product with its logo, showing software with a screenshot, illustrating a file's layout with a diagram, or showing what correct rendering of the format looks like.
Why attach a purpose to every image?
Because the same record may feed a web page, a data export and a software interface. Without a purpose value, a system cannot tell which image to use as a thumbnail and which one documents the format's structure.
Is a sample file the same as a sample image?
No. A sample file is an instance of the format, useful for testing identification tools. A sample image is a picture of how such a file renders. Records benefit from keeping the two apart, with the sample file linked as its own resource.
Who owns the images in a format record?
Often not the registry. Logos belong to the organizations that use them, and screenshots contain third-party software interfaces. Recording rights and source for each image avoids reusing material on terms that were never granted.
How does image purpose relate to foaf:depiction?
foaf:depiction says only that an image depicts something. An image purpose value adds why the image is there. A vocabulary can use foaf:depiction for the link and a purpose property, or a subproperty, for the role.