Apéndice G Deprecations

Índice

Apéndice G.1 Items Scheduled to be Removed

TEI: Items Scheduled to be Removed⚓︎Apéndice G.1 Items Scheduled to be Removed

This appendix provides a partial list of items (elements, attributes, attribute values, datatypes etc.) which are deprecated in this revision of the TEI Guidelines (revision 4e6e41b0b of TEI P5 Version 4.8.0).

The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. This feature will be withdrawn after 2024-11-11.
The use of ISO Schematron <sch:assert> and <sch:report> elements without a parent <sch:rule> with a context attribute is deprecated — it will be an error after 2025-03-15. This feature will be withdrawn after 2025-03-15.
Because an entry can now occur inside an entry, the re element is no longer needed. These Guidelines recommend using an entry with a type attribute value of relatedEntry instead. This feature will be withdrawn after 2026-03-10.
Because an entry can now occur inside an entry, the superEntry element is no longer needed. For instances where the superEntry element was used to group multiple entry elements, these Guidelines recommend using instead an outer entry element, perhaps with a type attribute. This feature will be withdrawn after 2027-03-07.

[English] [Deutsch] [Español] [Italiano] [Français] [日本語] [한국어] [中文]

TEI Guidelines P5 Version 4.8.0. Last updated on 2nd September 2024, revision 4e6e41b0b. This page generated on 2024-09-04T14:54:59Z.

TEI: Directrices para la codificación y el intercambio de textos electrónicos

Apéndice G Deprecations

TEI: Items Scheduled to be Removed⚓︎Apéndice G.1 Items Scheduled to be Removed