201820192020 20212022202320242025 the Contributors to the XProc 3.1 Standard Step Library specifications XProc/specification XProc Next XML Norman Walsh Achim Berndzen Gerrit Imsieke Erik Siegel This specification describes optional mail related steps for XProc 3.1: 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). This draft is the “editor’s working draft” and may continue to evolve.

This specification describes optional mail 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.

The p:send-mail step sends an email message. The first document on the source port is expected to conform to . It is a dynamic error if the first document on the source port does not conform to the required format. Any additional documents are treated as attachments. If the mail was send successfully a single c:result document whose content is “true” appears on the result port. It is a dynamic error if the email cannot be send. The em:content may contain either text or HTML. To send some other type as the first message body, you must leave the em:content element out of the first document and supply the body as a second document. The p:send-mail step has the following options: serialization The serialization option is used to control the serialization of documents for constructing the mail. If a document has a “serialization” document property, the effective value of the serialization options is the union of the two maps, where the entries in the “serialization” document property take precedence. auth If the mail service requires an authentication to send mails, these can be supplied using the auth option. The following standard keys are defined: username (xs:string) The username. password (xs:string) The password. Other key value pairs in “auth” are implementation-defined.It is a dynamic error if any key in the “auth” map is associated with a value that is not an instance of the required type. parameters The parameters option can be used to supply additional information for constructing and sending mails. A number of parameters are defined in this specification. It is implementation-defined which other key/value pairs in the parameters option are supported. send-authorization (xs:boolean) If the key is associated with false no authentication will be used when sending a mail. host (xs:string) The SMTP server. port (xs:unsignedShort) The port. Other key value pairs in “auth” are implementation-defined.It is a dynamic error if any key in the “parameters” map is associated with a value that is not an instance of the required type. If no values for “host” or “port” is specified, it it implementation-defined which server and port is used. No document properties are preserved.

These 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:

Conformant 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.

The following features are implementation-defined:

Glossary needs to be generated This specification includes by reference a number of ancillary files. An XProc step library for the declared steps.