pub enum Relationship {
Source,
Data,
Alternative,
Supplement,
EncryptedPayload,
FormData,
Schema,
Unspecified,
}Expand description
What an associated file is to the thing it is associated with
(/AFRelationship, ISO 32000-2 table 404).
The relationship is not decoration: a PDF/A-3 validator reads it, and an
electronic-invoice profile requires the invoice XML to be
Alternative — the machine-readable form of what the
page shows — rather than Supplement or
Unspecified.
Variants§
Source
/Source: the file the visible content was generated from.
Data
/Data: data the content presents — a spreadsheet behind a chart.
Alternative
/Alternative: an alternative representation of the same content.
This is what an electronic invoice’s XML is.
Supplement
/Supplement: additional material the content does not itself show.
EncryptedPayload
/EncryptedPayload: the file is an encrypted payload, and the
document around it is the wrapper.
FormData
/FormData: the data of a form the document presents.
Schema
/Schema: a schema the associated data conforms to.
Unspecified
/Unspecified: the relationship is not stated. The default, and what
a validator that requires one will reject.
Implementations§
Source§impl Relationship
impl Relationship
Sourcepub fn from_bytes(bytes: &[u8]) -> Option<Relationship>
pub fn from_bytes(bytes: &[u8]) -> Option<Relationship>
The relationship an /AFRelationship name means, or nothing for one
outside the table.
Trait Implementations§
Source§impl Clone for Relationship
impl Clone for Relationship
Source§fn clone(&self) -> Relationship
fn clone(&self) -> Relationship
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more