XProc 3.0: RDF steps201820192020the Contributors to the XProc 3.0 Standard Step Library
specificationsxproc/3.0-stepsXProc NextXMLNorman WalshAchim BerndzenGerrit ImsiekeErik SiegelThis specification describes the optional RDF related steps for XProc 3.0: An XML Pipeline Language.This specification was published by the
XProc
Next Community Group. It is not a W3C Standard nor is it on
the W3C Standards Track. Please note that under the
W3C
Community Contributor License Agreement (CLA) there is a limited
opt-out and other conditions apply. Learn more about W3C Community and Business
Groups.
If you wish to make comments regarding this document, please
send them to
xproc-dev@w3.org.
(subscribe,
archives).
IntroductionThis specification describes the optional text related XProc steps. A machine-readable description of these steps may be found in steps.xpl. Familarity with the general nature of steps is assumed; for background details,
see .p:something-rdfThe p:something-rdf step is just a placeholder.
The build for steps fails unless at least one step is defined.TBDDocument propertiesNo document properties are preserved.Step ErrorsThese steps can raise dynamic errors. A dynamic error is one which occurs while a pipeline
is being evaluated. Examples of dynamic errors include references to URIs that cannot be resolved,
steps which fail, and pipelines that exhaust the capacity of an implementation (such as memory or disk space). For
a more complete discussion of dynamic errors, see . If a step fails due to a dynamic error, failure propagates upwards until either a p:try is
encountered or the entire pipeline fails. In other words, outside of a p:try, step failure causes the
entire pipeline to fail.The following errors can be raised by this step:ConformanceConformant processors must implement all of the features
described in this specification except those that are explicitly identified
as optional.Some aspects of processor behavior are not completely specified; those
features are either implementation-dependent or
implementation-defined.An
implementation-dependent feature is one where the
implementation has discretion in how it is performed.
Implementations are not required to document or explain
how implementation-dependent features are performed.An
implementation-defined feature is one where the
implementation has discretion in how it is performed.
Conformant implementations must document
how implementation-defined features are performed.Implementation-defined featuresThe following features are implementation-defined:Implementation-dependent featuresThe following features are implementation-dependent:ReferencesXProc 3.0XProc 3.0:
An XML Pipeline Language.
Norman Walsh, Achim Berndzen, Gerrit Imsieke and Erik Siegel, editors.
XProc 3.0 StepsXProc 3.0 Steps:
An Introduction.
Norman Walsh, Achim Berndzen, Gerrit Imsieke and Erik Siegel, editors.
Glossarydynamic errorA dynamic error is one which occurs while a pipeline
is being evaluated.implementation-definedAn
implementation-defined feature is one where the
implementation has discretion in how it is performed.
Conformant implementations must document
how implementation-defined features are performed.implementation-dependentAn
implementation-dependent feature is one where the
implementation has discretion in how it is performed.
Implementations are not required to document or explain
how implementation-dependent features are performed.Ancillary filesThis specification includes by reference a number of
ancillary files.An XProc step library for the declared steps.