This may be an ARK, URN, filename, or other identifier. See URI Encoding and Decoding for more information. The prefix may contain multiple path segments, delimited by slashes, but all other special characters must be encoded. This prefix is optional, but may be useful when the host server supports multiple services. The path on the host server to the service. The parameter may also include a port number. The host server on which the service resides. Indicates the use of the HTTP or HTTPS protocol in calling the service. There are four parameters shared by the requests, and other IIIF specifications: Name It also permits a minimal implementation using pre-computed files in a matching directory structure. This makes responses easier to cache, either at the server or by standard web-caching infrastructure. Request information about the image service, including characteristics, functionality available, and related services.īoth convey the request’s information in the path segments of the URI, rather than as query parameters.Request an image, derived from the underlying image content.The IIIF Image API can be called in two ways: The key words must, must not, required, shall, shall not, should, should not, recommended, and optional in this document are to be interpreted as described in RFC 2119. The term full image is used to refer to the entire area of the underlying image content, with the pixel dimensions given in the image information document, and which is imagined as the starting point for image requests. It might be derived from one or more source images but could also be dynamically generated. No assumptions are made about its format or structure. The term underlying image content is used to refer to the source image data. Dynamic image server implementations may provide additional functionality beyond the base level of compliance. Implementations may use a pre-generated set of files served as static web resources and still enable rich user experiences. This allows flexibility for implementation in domains with particular constraints or specific community practices, while supporting interoperability in the general case. It covers how to respond to requests that follow a particular URI syntax, but does not cover methods of implementation such as rotation algorithms, transcoding, color management, compression, or how to respond to URIs that do not conform to the specified syntax. This specification concerns image requests by a client, but not management of the images by the server. Client applications using image content for analysis or comparison.
0 Comments
Leave a Reply. |