The Z39.98 SVG CDR (Compound Document by Reference) feature enables the use of SVG, referenced as external documents via the
object
element, or specializations thereof.
The fallback mechanism defined by the
object element is used to provide alternate content type renditions where needed.
Note that this feature does not require alternate image format renditions to be provided, although this is highly recommended practice.
This feature is maintained by the ANSI/NISO Z39.98 advisory committee under the auspices of NISO.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this section are to be interpreted as described in RFC2119.
object Element requirements
The
object elements that carry the SVG document references must contain a textual fallback, as defined in the
object module.
The
object elements that carry the SVG document references should contain at least one fallback using the image formats defined in
core image types.
The referenced SVG documents must conform to one of the following versions of SVG:
Note that the schema module provided by this feature does not validate the referenced SVG documents; validating processing agents must perform SVG validation as an additional routine.
This resource directory represents version
1.0 of the SVG CDR feature:
This release may not be the most recently published (current) version of the SVG CDR feature. The current version should always be obtained from the static URI: http://www.daisy.org/z3998/2012/auth/features/svg-cdr/current/
This feature must be identified as
svg-cdr in Z39.98-AI document feature declarations.
The canonical identity URI is:
http://www.daisy.org/z3998/2012/auth/features/svg-cdr/1.0/
This version of the feature is compliant with the Z39.98-2012 Specification.
The normative
RelaxNG schema for version
1.0 of the SVG CDR feature is
z3998-feature-svg-cdr.rng.
Note - this feature schema does not represent an entire document model; it is intended for inclusion in host profiles.
This feature makes the following components available for inclusion in host profiles:
object element, it has no
public components.
This section defines processing agent behaviors that extend the default behaviors defined in Processing agent conformance definition.
If a processing agent supports this feature, it must process encountered SVG references as dictated by the SVG 1.1 and SVG 1.2 Tiny specifications respectively.
If a processing agent recognizes but does not support this feature, it must employ one of the following behaviors:
Upon encountering a document instance with this feature enabled, the processing agent issues a notification, and then aborts the processing.
While traversing the document tree, the processing agent
ignores any encountered
object element referencing an SVG document, and continues processing its children.
The processing agent
discards
object elements referencing SVG documents;
object elements with SVG references are recursively replaced by their children, until the replacement consists of a media type that is supported by the processing agent.
The
abort behavior is the default; the
ignore and
discard behaviors must only be employed when the processing agent is explicitly instructed to do so by the client.
Processing agents that employ the
ignore or
discard behaviors should issue a notification.
If a processing agent does not recognize this feature, it must, as dictated in Processing agent conformance definition, abort processing and issue an error message.
Refer to the Z39.98-AI community portal for information on available software tools.
The below list represents the modules at the time of version 1.0 of this feature.
The occurrence of the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in documentation fields embedded in these modules are to be interpreted as described in RFC2119.