|
704 | 704 | <list style="hanging"> |
705 | 705 | <t hangText="date-time:"> |
706 | 706 | A string instance is valid against this attribute if it is |
707 | | - a valid representation according to the "date-time" production. |
| 707 | + a valid representation according to the "date-time' ABNF rule |
| 708 | + (referenced above) |
708 | 709 | </t> |
709 | 710 | <t hangText="date:"> |
710 | 711 | A string instance is valid against this attribute if it is |
711 | | - a valid representation according to the "full-date" production. |
| 712 | + a valid representation according to the "full-date" ABNF rule |
| 713 | + (referenced above) |
712 | 714 | </t> |
713 | 715 | <t hangText="time:"> |
714 | 716 | A string instance is valid against this attribute if it is |
715 | | - a valid representation according to the "full-time" production. |
| 717 | + a valid representation according to the "full-time" ABNF rule |
| 718 | + (referenced above) |
716 | 719 | </t> |
717 | 720 | <t hangText="duration:"> |
718 | 721 | A string instance is valid against this attribute if it is |
719 | | - a valid representation according to the "duration" production. |
| 722 | + a valid representation according to the "duration" ABNF rule |
| 723 | + (referenced above) |
720 | 724 | </t> |
721 | 725 | </list> |
722 | 726 | </t> |
723 | 727 | <t> |
724 | 728 | Implementations MAY support additional attributes using the other |
725 | | - production names defined anywhere in that RFC. If "full-date" or "full-time" |
| 729 | + format names defined anywhere in that RFC. If "full-date" or "full-time" |
726 | 730 | are implemented, the corresponding short form ("date" or "time" |
727 | 731 | respectively) MUST be implemented, and MUST behave identically. |
728 | 732 | Implementations SHOULD NOT define extension attributes |
729 | | - with any name matching an RFC 3339 production unless it validates |
730 | | - according to the rules of that production. |
| 733 | + with any name matching an RFC 3339 format unless it validates |
| 734 | + according to the rules of that format. |
731 | 735 | <cref> |
732 | 736 | There is not currently consensus on the need for supporting |
733 | 737 | all RFC 3339 formats, so this approach of reserving the |
|
0 commit comments