Define epub date

Reading Systems MAY support only this default value. If a Reading Systems supports the rendition:layout property, it MUST ignore the rendition:flow property when it has been set on a spine item that also specifies the rendition:layout value pre-paginated. In addition to using the rendition:flow property, Authors MAY override this behavior through an appropriate style sheet declaration, if the Reading System supports such overrides. The Author does not have a preference for overflow handling.

The Reading System MAY render overflow content using its default method or a user preference, whichever is applicable. Authors MAY specify the following properties locally on spine itemref elements to override the global value for the given spine item:. For the rendition:flow-scrolled-continuous property, the scroll direction is defined relative to the block flow direction of the root element of the XHTML Content Document referenced by the itemref element.

The scroll direction is vertical if the block flow direction is downward top-to-bottom. It is horizontal if the block flow direction of the root element is rightward left-to-right or leftward right-to-left. The rendition:align-x-center property specifies that the given spine item should be centered horizontally in the viewport or spread.

When the rendition:align-x-center property is set on a spine item, it indicates that the rendered content SHOULD be centered horizontally within the Viewport or spread, as applicable.

This property does not affect the rendering of the spine item, only the placement of the resulting content box. This version of this specification does not define a default rendering behavior when this property is not supported or specified. Reading Systems MAY render spine items by their own design. As support for paged media evolves in CSS, however, this property is expected to be deprecated.

Authors are encouraged to use CSS solutions when effective. The content flows, or reflows, to fit the screen and to fit the needs of the user. As noted in Rendering and CSS "content presentation adapts to the user, rather than the user having to adapt to a particular presentation of content.

Sometimes content and design are so intertwined they cannot be separated. Any change in appearance risks changing the meaning, or losing all meaning. This section defines a set of metadata properties to allow declarative expression of intended rendering behaviors of Fixed-Layout Documents in the context of EPUB 3. EPUB 3 affords multiple mechanisms for representing fixed-layout content. When fixed-layout content is necessary, the Author's choice of mechanism will depend on many factors including desired degree of precision, file size, accessibility, etc.

This section does not attempt to dictate the Author's choice of mechanism. The rendition:layout property specifies whether the given Rendition is reflowable or pre-paginated. When the rendition:layout property is specified on a meta element, it indicates that the paginated or reflowable layout style applies globally for the Rendition i.

The following values are defined for use with the rendition:layout property:. The given Rendition is not pre-paginated. Reading Systems MAY apply dynamic pagination when rendering.

The given Rendition is pre-paginated. Reading Systems typically restrict or deny the application of user or user agent style sheets to pre-paginated documents, since, as a result of intrinsic properties of such documents, dynamic style changes are highly likely to have unintended consequences.

Authors need to take into account the negative impact on usability and accessibility that these restrictions have when choosing to use pre-paginated instead of reflowable content. Refer to Guideline 1. The rendition:orientation property specifies which orientation the Author intends the given Rendition to be rendered in. When the rendition:orientation property is specified on a meta element, it indicates that the intended orientation applies globally for the given Rendition i.

The following values are defined for use with the rendition:orientation property:. The means by which the intent is conveyed is implementation-specific.

The rendition:spread property specifies the intended Reading System synthetic spread behavior for the given Rendition. When the rendition:spread property is specified on a meta element, it indicates that the intended Synthetic Spread behavior applies globally for the given Rendition i. The following values are defined for use with the rendition:spread property:. The use of spreads only in portrait orientation is deprecated.

Authors are advised to use the value " both " instead, as spreads that are readable in portrait orientation are also readable in landscape. No explicit Synthetic Spread behavior is defined. Refer to spine for information about declaration of global flow directionality using the page-progression-direction attribute and that of local page-progression-direction within content documents. When a Reading System renders a Synthetic Spread , the default behavior is to populate the spread by rendering the next EPUB Content Document in the next available unpopulated viewport, where the next available viewport is determined by the given page progression direction or by local declarations within Content Documents.

An Author MAY override this automatic population behavior and forcing a document to be placed in a particular viewport by specifying one of the following properties on its spine itemref element:.

The rendition:page-spread-center property indicates that the synthetic spread mode SHOULD be overridden and a single viewport rendered and positioned at the center of the screen. The rendition:page-spread-left , rendition:page-spread-right and rendition:page-spread-center properties apply to both pre-paginated and reflowable content, and they only apply when the Reading System is creating Synthetic Spreads. The presence of rendition:page-spread-center does not change the viewport dimensions.

In particular, it does not indicate that a viewport with the size of the whole spread has to be created. This is important so that the scale factor stays consistent between regular and center-spread pages. Although Authors often indicate to use a spread in certain device orientations, the content itself does not represent true spreads i. To indicate that two consecutive pages represent a true spread, Authors SHOULD use the rendition:page-spread-left and rendition:page-spread-right properties on the spine items for the two adjacent EPUB Content Documents, and omit the properties on spine items where one-up or two-up presentation is equally acceptable.

The rendition:page-spread-left and rendition:page-spread-right properties are aliases for the page-spread-left and spread-right properties. They allow the use of a single vocabulary for all fixed-layout properties. Authors can use either property set, but older Reading Systems might only recognize the unprefixed versions. The EPUB Spine Properties Vocabulary is no longer being extended for package rendering metadata, so an unprefixed page-spread-center is not available.

Use of the property is deprecated. Refer to its definition in [ Publications ] for more information. It allows Authors to include a human- and machine-readable global navigation layer, thereby ensuring increased usability and accessibility for the user. Because it is an XHTML Content Document, it can be part of the linear reading order, avoiding the need for duplicate tables of contents. Content which is only destined for machine processing, such as page lists , can be hidden from visual rendering with the hidden attribute.

If such formatting and functionality is needed, then the EPUB Navigation Document also needs to be included in the spine. The use of progressive enhancement [ ContentDocs32 ] techniques for scripting and styling of the navigation document will help ensure the content will retain its integrity when rendered in a non-browser context. When requested by a user, it MUST provide access to the links and link labels in the nav elements of the EPUB Navigation Document in a fashion that allows the user to activate the links.

When a link is activated, it MUST relocate the application's current reading position to the destination identified by that link. When a nav element carries the epub:type attribute [ ContentDocs32 ] in an EPUB Navigation Document , this specification restricts the content model of the element and its descendants as follows:. HTML Heading content [0 or 1]. HTML Phrasing content [1 or more]. The ol child of the nav element represents the primary level of content navigation.

Each list item of the ordered list represents a heading, structure or other item of interest. A child a element describes the target that the link points to, while a span element serves as a heading for breaking down lists into distinct groups for example, a large list of illustrations can be segmented into several lists, one for each chapter. The child a or span element MUST provide a non zero-length text label after concatenation of all child content and application of white space normalization rules.

Although non-textual descendant elements MAY be rendered directly to users, text content included in title or alt attributes MUST be used when determining compliance with this requirement. If an a or span element contains instances of HTML embedded content that do not provide intrinsic text alternatives, the element MUST also include a title attribute with an alternate text rendering of the link label. An a element MAY be followed by an ol ordered list representing a subsidiary content level below that heading e.

A span element MUST be followed by an ol ordered list; it cannot be used in "leaf" li elements. Regardless of whether an a or span element precedes it, every sublist MUST adhere to the content requirements defined in this section for constructing the primary navigation list. In the context of this specification, the default display style of list items within nav elements MUST be equivalent to the list-style: none property [ CSSSnapshot ].

Identifies the nav element that contains the table of contents. Identifies the nav element that contains a list of pages for a print or other statically-paginated source for the EPUB Publication. See Other nav Elements for more information. The toc nav element defines the primary navigational hierarchy of the given Rendition.

It conceptually corresponds to a table of contents in a printed work i. The references in the toc nav element MUST be ordered such that they reflect both:. The page-list nav element provides navigation to positions in the content that correspond to the locations of page boundaries present in a print source being represented by the EPUB Publication.

The landmarks nav element identifies fundamental structural components in the given Rendition in order to enable Reading Systems to provide the user efficient access to them. The structural semantics of each link target within the landmarks nav element is determined by the value of this attribute.

The landmarks nav MUST NOT include multiple entries with the same epub:type value that reference the same resource, or fragment thereof. EPUB Navigation Documents MAY include one or more nav elements in addition to the toc , page-list and landmarks nav elements defined in the preceding sections.

This specification imposes no restrictions on the semantics of any additional nav elements: they MAY be used to represent navigational semantics for any information domain, and they MAY contain link targets with homogeneous or heterogeneous semantics.

In some cases, Authors might wish to hide parts of the navigation data within the content flow i. A typical example is the list of page breaks , which usually is not rendered as part of the content flow but is instead exposed to the user separately in a dedicated navigation user interface. To control rendering across all Reading Systems, authors MUST use the [ HTML ] hidden attribute to indicate which if any portions of the navigation data are excluded from rendering in the content flow.

The hidden attribute has no effect on how navigation data is rendered outside of the content flow such as in dedicated navigation user interfaces provided by Reading Systems. These schemas may be updated and corrected outside of formal revisions of this specification. As a result, they are subject to change at any time. This registration supersedes [ RFC ]. It identifies the resources in the Rendition and provides metadata information.

Clearly, it is possible to author malicious files which, for example, contain malformed data. Most XML parsers protect themselves from such attacks by rigorously enforcing conformance. All processors that read Package Documents should rigorously check the size and validity of data retrieved.

This media type is in wide use for the distribution of ebooks in the EPUB format. The following list of applications is not exhaustive. W3C has change control over this specification. The properties in this vocabulary are usable in the meta element's property attribute.

The following tables define properties for use in the meta element's property attribute. The alternate-script property provides an alternate expression of the associated property value in a language and script identified by the xml:lang attribute.

This property is typically attached to creator and title properties for internationalization purposes. The authority property identifies the system or scheme the referenced element's value is drawn from. The belongs-to-collection property identifies the name of a collection to which the EPUB Publication belongs. It is also possible chain these properties using the refines attribute to indicate that one collection is itself a member of another collection.

To allow Reading System to organize collections and avoid naming collisions e. The dcterms:identifier property must carry this identifier. The collection MAY more precisely define its nature by attaching a collection-type property. When the collection-type value is drawn from a code list or other formal enumeration, the scheme attribute SHOULD be attached to identify its source. A sequence of related works that are formally identified as a group; typically open-ended with works issued individually over time.

A finite collection of works that together constitute a single intellectual unit; typically issued together and able to be sold as a unit. The display-seq property indicates the numeric position in which to display the current property relative to identical metadata properties. This property only applies where precedence rules have not already been defined e. The group-position property indicates the numeric position in which the EPUB Publication is ordered relative to other works belonging to the same group whether all EPUB Publications or not.

The group-position property can be attached to any metadata property that establishes the group, but is typically associated with the belongs-to-collection property.

The identifier-type property indicates the form or nature of an identifier. When the identifier-type value is drawn from a code list or other formal enumeration, the scheme attribute SHOULD be attached to identify its source. The meta-auth property identifies the party or authority responsible for an instance of package metadata.

The role property describes the nature of work performed by a creator or contributor e. When the role value is drawn from a code list or other formal enumeration, the scheme attribute SHOULD be attached to identify its source. The source-of property indicates a unique aspect of an adapted source resource that has been retained in the given Rendition of the EPUB Publication.

This specification defines the pagination value to indicate that the referenced dc:source element is the source of the pagebreak properties defined in the content. The title-type property indicates the form or nature of a title. Hey one of my files exists as a. Have tables with Greek and Hebrew letters in them. Also, would these fonts have to be embedded in the EPUB file? It can convert any existing document to EPUB.

You can also use it to create a new EPUB from scratch. If you take an EPUB file and change the. I have one copy of an out-of-print book I wrote years ago, containing both text and visuals.

I want to convert these pages to an eBook format ePub? Given the limited to non-existant scaling options in ebook readers, a file created that way would not be very practical.

It is better to use an OCR application to convert the scanned text to actual text and redo the layout of the book as a digital file. My graphics jpg are showing up way too large when I convert to epub, and in a different location on the page than they are in the original file. Any ideas on how to fix that? Also, my title page is repeated as the first page of the document with wacky spacing.

You can change graphics to PNG format, in case, if u wnat only jpg format, u can change the resolution using any Image editor. A subexpression may refine a media clip, for example, by expressing its duration, or refine a creator or contributor expression by defining the person's role.

Subexpressions are not limited to refining only primary expressions and resources; they may be used to refine the meaning of other subexpressions, thereby creating chains of information. All of the [ DCMES ] elements represent primary expressions, and permit refinement by meta element subexpressions. This specification reserves a set of vocabularies for use in the property attribute, but terms from any vocabulary may be used so long as a prefix is declared for the vocabulary. The scheme attribute can be used to identify the system or scheme that a meta element's value is drawn from.

The value of the scheme attribute is a property data type that resolves to the resource that defines the scheme. The following example shows how a subexpression can be attached to an creator to indicate it represents an author. The scheme indicates the value is drawn from the MARC relators terms. If a Reading System does not recognize the scheme attribute value, it should treat the value of the element as a string. Reading Systems should ignore all meta elements whose property attributes define expressions they do not recognize.

A Reading System must not fail when encountering unknown expressions. In order to ensure that a Package Identifier can be constructed, the metadata element must contain exactly one meta element defining a [ DCTERMS ] modified property for the Publication.

Additional modified properties may be included, but they must have a different subject i. Every meta element must express a value that is at least one character in length after whitespace normalization. Unless an individual property explicitly defines a different whitespace normalization algorithm, Reading Systems must trim all leading and trailing whitespace from the meta element values, as defined by the XML specification [ XML ] , before further processing them.

The following example represents a more complete set of metadata that typical Publications will contain. The meta element defined in [ OPF2 ] has been obsoleted and replaced by the new meta element, but may be included as an optional repeatable child of the metadata element for forwards compatibility purposes.

The link element is used to associate resources with a Publication, such as metadata records. As a child of metadata. A space-separated list of property values. A media type [ RFC ] that specifies the type and format of the resource referenced by this link.

The metadata element may contain zero or more link elements. The href attribute of the link element identifies the location of the resource — inclusion of which is optional in the container file — and the rel attribute defines the nature of the resource i. Reading Systems are not required to dereference these resources. Refer to Metadata link Properties for the list of resource types that are recognized by this specification.

Resources identified by the link element href attribute must not be represented as item s in the manifest. When the link element references a metadata record, precedence must be given to metadata defined inline in the Package Document metadata element in the case of conflicts.

The optional refines attribute can be attached when the referenced resource applies to another metadata item e. The resource applies to the Publication as a whole when the attribute is not present. If a Reading System does not recognize the relationship of the resource as defined in the rel attribute, it should ignore the link element.

The following example shows the link element used to associate three metadata resources with the Publication: an ONIX record, an XMP record, and a link to an informational web page. Note that as foaf is not a predefined prefix , the metadata extensibility mechanism is employed to associate the vocabulary. The manifest element provides an exhaustive list of the Publication Resource s that constitute the EPUB Publication , each represented by an item element.

Required second child of package , following metadata. One or more item elements [required]. This specification supports internationalized resource naming, so elements and attributes that reference Publication Resources accept IRIs as their value.

The item element represents a Publication Resource. As a child of manifest. A media type [ RFC ] that specifies the type and format of the Publication Resource described by this item. Refer to Manifest Fallbacks for more information. Refer to Manifest item Properties for a set of properties defined by this specification. Refer to Packaging [ MediaOverlays30 ] for more information. Each item element in the manifest identifies a Publication Resource by the IRI provided in its href attribute.

The IRI may be absolute or relative. The resulting absolute IRI must be unique within the manifest scope.

All Publication Resources must be referenced from the manifest , regardless of whether they are included in the EPUB Container or made available remotely. Refer to Publication Resource Locations for media type-specific requirements regarding resource locations. The Publication Resource identified by an item element must conform to the applicable specification s as inferred from the MIME media type provided in the media-type attribute.

All Foreign Resource s must provide a fallback as defined in Restrictions and Fallbacks. All Publication Resources must declare any applicable descriptive metadata properties as defined in Manifest item Properties via the item element properties attribute.

The manifest is not self-referencing: it must not include an item element that refers to the Package Document itself. The order of item elements in the manifest is not significant.

The presentation sequence of content documents is provided in the spine. The following example shows a manifest that only contains Core Media Type Resource s. The following example shows a manifest that references two Foreign Resource s, and therefore uses the fallback chain mechanism to supply content alternatives.

The fallback chain terminates with a Core Media Type. Refer also to the Manifest item properties examples for use of the properties attribute.

The spine element defines the default reading order of the EPUB Publication content by defining an ordered list of manifest item references. Required third child of package , following manifest. Refer to NCX Superseded for more information. Allowed values are ltr left-to-right , rtl right-to-left and default.

When the default value is specified, the Author is expressing no preference and the Reading System may chose the rendering direction. This value must be assumed when the attribute is not specified. Multiple itemref elements [required]. The spine represents an ordered subset of the Publication Resources listed in the manifest , with content items not being referenced being ancillary to those that do.

Although the page-progression-direction attribute sets the global flow direction for a Publication, individual Content Documents and parts of Content Documents may override this setting e. Reading Systems may also provide mechanisms to override the default direction e. The order of the itemref elements defines the default reading order of the Publication.

The value of the attribute must be yes or no. The default value is yes. Refer to Spine itemref Properties for a set of properties defined by this specification. Each itemref element must reference an item in the manifest via its idref attribute. The itemref element linear attribute indicates whether referenced item is considered primary yes or auxiliary no in the spine. This attribute may be used to enable Reading Systems to distinguish presentation of body content from supplementary content which might be, for example, presented in a popup window or omitted from an aural rendition.

Any applicable descriptive metadata properties, such as those defined in the Spine itemref Properties , should be declared via the properties attribute. Reading Systems must ignore all metadata properties expressed in the properties attribute that they do not recognize.

The following example shows a spine element corresponding to the manifest example above. Refer to The landmarks nav Element [ ContentDocs30 ] for more information.

The bindings element defines a set of custom handlers for media types not supported by this specification. Optional fourth or fifth child of package , following spine or guide. One or more mediaType elements [required].

The package element may contain at most one bindings element. The bindings element provides a means for Authors to include more sophisticated fallbacks than would otherwise be possible with the [ HTML5 ] object element's intrinsic fallback mechanisms.

When present, Reading Systems that support scripting must utilize the bindings element to handle object elements that reference unsupported media types. Each of the bindings element's child mediaType elements defines a unique handler for one of the foreign media types referenced in the Publication's XHTML Content Document s.

When an unsupported media type is encountered during processing of a document, the Reading System must look up the handler in the bindings element by checking the media-type attribute of each mediaType element for a match and before attempting any other type of fallback processing.

If a match is found, the XHTML Content Document referenced in the element's handler attribute must be instantiated instead of the referenced resource. If no match is found, the Reading System should continue with normal fallback processing i.

The Reading System must instantiate the designated handler as if it had been referenced from the object element's data attribute with the following parameters:.

Any additional param children of the object element must be similarly added as parameters using the param 's name attribute as the new parameter name and its value attribute as the new value. Depending on the capabilities of the User 's Reading System, they will see one of the following renditions of the slideshow:. If the Reading System supports the native slideshow format, it will render a rotating set of images as specified in slideshow.

If the Reading System cannot support the slideshow media type but supports scripting, it can check the bindings element in the Package Document for a scripted fallback. There it will find a reference to the item element containing the handler document impl. The Reading System can now load this document to render a JavaScripted equivalent of the slideshow source not shown.

If the Reading System does not support the slideshow media type and also does not support scripting, it will use the fallback images specified in the object element to show a static set of all the images.

As a child of bindings. A media type [ RFC ] that specifies the type and format of the resource to be handled. Each child mediaType of a bindings element must define a unique content type in its media-type attribute, and the media type specified must not be a Core Media Type.

The required handler attribute must reference the ID [ XML ] of an item in the manifest of the default implementation for this media type. The Package Document's author is responsible for including a primary identifier that is unique to one and only one particular EPUB Publication.

This Unique Identifier , whether chosen or assigned, must be stored in a dc:identifier element in the Package metadata and be referenced as the Unique Identifier in the package element unique-identifier attribute. Although not static, changes to the Unique Identifier for a Publication should be made as infrequently as possible.

New identifiers should not be issued when updating metadata, fixing errata or making other minor changes to the Publication. The Unique Identifier of an EPUB Publication typically should not change with each minor revision to the package or its contents, as Unique Identifiers are intended to have maximal persistence both for referencing and distribution purposes.

Each release of a Publication normally requires that the new version be uniquely identifiable, however, which results in the contradictory need for reliable Unique Identifiers that are changeable.

To redress this problem of identifying minor modifications and releases without changing the Unique Identifier, this specification defines the semantics for a Package Identifier, or means of distinguishing and sequentially ordering Publications with the same Unique Identifier. The Package Identifier is not an actual property in the package metadata section, but is a value that can be obtained from two required pieces of metadata: the Unique Identifier and the last modification date of the Publication.

When the taken together, the combined value represents a unique identity that can be used to distinguish any particular version of an EPUB Manifestation from another. Although not a part of the package metadata, for referencing and other purposes this specification requires that all string representations of the identifier be constructed using the at sign as the separator i.

Whitespace must not be included when concatenating the strings. The following example shows how a Unique Identifier and modification date are combined to form the Package Identifier.

Note that it is possible that the separator character may occur in the Unique Identifier, as these identifiers may be any string value. The Package Identifier consequently must be split on the last instance of the at sign when decomposing it into its component parts.

The Package Identifier does not supersede the Unique Identifier, but represents the means by which different versions of the same Publication can be distinguished and identified in distribution channels and by Reading Systems. The sequential, chronological order inherent in the required format of the timestamp also places Publications in order without requiring knowledge of the exact identifier that came before. The Package Identifier consequently allows a set of Publications to be inspected to determine if they represent the same version of the same Publication, different versions of a single Publication, or any combination of differing and similar Publications.

The property , properties , rel and scheme attributes use the property data type to represent terms from metadata vocabularies. A property value is an expression that consists of a prefix and a reference, where the prefix — whether literal or implied — is a shorthand mapping of an IRI that typically resolves to a term vocabulary. To assist Reading Systems in processing property values, the means of establishing the IRI a prefix maps to is required, and this specification defines three such mechanisms:.

The default vocabulary is a vocabulary that does not require a prefix to be declared in order to use its terms in package metadata, and whose terms must always be unprefixed. To facilitate the inclusion of package metadata, this specification defines the Package Metadata Vocabulary as the default vocabulary for Package Documents.

This specification exclusively defines the following set of prefixes for use in package metadata. The prefixes listed in the previous table must not be redeclared using the prefix attribute declaration mechanism.

Similarly, the IRIs associated with each prefix must not be assigned to another prefix. The prefix attribute defines additional prefix mappings not reserved by the specification. The value of the prefix attribute is a whitespace-separated list of one or more prefix-to-IRI mappings of the form:. The following example shows prefixes for the Friend of a Friend foaf and DBPedia dbp vocabularies being declared using the prefix attribute. The prefix attribute must not be used to redefine the default vocabulary or the predefined prefixes.

The property data type is a compact means of expressing an IRI [ RFC ] and consists of an optional prefix separated from a reference by a colon. The following example shows a property value composed of the prefix dcterms and the reference modified. After processing , this property would expand to the following IRI:.

When a prefix is omitted from the property value, the expressed reference represents a term from the default vocabulary.

An empty string does not represent a valid property value, even though it is valid to the definition above. If the property consists only of a reference, the IRI is obtained by concatenating the IRI stem associated with the default vocabulary to the reference. If the property consists of a prefix and reference, the IRI is obtained by concatenating the IRI stem associated with the prefix to the reference.

If no matching prefix has been defined, the property is invalid. Reading Systems are not required to resolve this IRI, however. The following sections both define a set of properties for use in package metadata and constitute a referenceable vocabulary.

This vocabulary is the default vocabulary reserved by this specification for the use of unprefixed terms in package metadata. Property usage examples in the following sections have been drawn from the metadata and meta examples whenever possible.

Refer to those examples for fuller context. The meta element properties enhance Publication metadata by providing additional level s of detail. These properties must reference the expression or resource they augment in the refines attribute on their parent meta element. The alternate-script property provides an alternate expression of the associated property value in a language and script identified by the xml:lang attribute.

This property is typically attached to creator and title properties for internationalization purposes. The display-seq property indicates the numeric position in which to display the current property relative to identical metadata properties e.

When the display-seq property is attached to some, but not all, of the members in a set, only the elements identified as having a sequence should be included in any rendering. The group-position property indicates the numeric position in which the Publication is ordered relative to other works belonging to the same group whether all EPUBs or not. The group-position property can be attached to any metadata property that establishes the group such as a series title.

The identifier-type property indicates the form or nature of an identifier. When the identifier-type value is drawn from a code list or other formal enumeration, the scheme attribute should be attached to identify its source.

The role property describes the nature of work performed by a creator or contributor e. When the role value is drawn from a code list or other formal enumeration, the scheme attribute should be attached to identify its source. The title-type property indicates the form or nature of a title. When the title-type value is drawn from a code list or other formal enumeration, the scheme attribute should be attached to identify its source.