[ISO8601] allows many options and variations in the representation of dates and times. The current specification uses one of the formats described in the profile [DATETIME] for its definition of legal date/time strings ( %Datetime in the DTD).
[ISO8601]在日期和时间的展现上允许很多选项及变形。本规范只采用了其中的一种格式,在[DATETIME] 中描述了该格式的细节,在DTD的参数实体%Datetime 中出现的日期/时间字符串必须符合该种格式才是合法的。
The format is:YYYY-MM-DDThh:mm:ssTZDwhere:
YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) TZD = time zone designator
The time zone designator is one of:
日期/时间字符串的格式如下:
YYYY-MM-DDThh:mm:ssTZD
其中:
YYYY = 四位数字的年份 MM = 两位数字的月份(01代表一月份,依此类推) DD = 两位数字的日期(从01 到 31) hh = 两位数字的小时(从00 到 23) (不允许上下午标识:am/pm) mm = 两位数字的分钟(从00 到 59) ss = 两位数字的秒钟(从00 到 59) TZD = 时区指示符
时区指示符可以是下表中的任何一种:
Exactly the components shown here must be present, with exactly this punctuation. Note that the "T" appears literally in the string (it must be uppercase), to indicate the beginning of the time element, as specified in [ISO8601]
必须按照上面的描述提供所有组成部分,它们之间的标点分隔也要精确匹配。请注意:根据[ISO8601]的描述,大写字符"T"(必须大写)表示时间元素的开始。
If a generating application does not know the time to the second, it may use the value "00" for the seconds (and minutes and hours if necessary).
如果生成程序不知道具体的秒钟时间,它可以对秒钟字段使用"00"作为其值。类似的,如果需要也可以将该规则应用到分钟,小时字段。
Note. [DATETIME] does not address the issue of leap seconds.
注释。 [DATETIME] 不包括闰秒机制。
Authors may use the following recognized link types, listed here with their conventional interpretations. In the DTD, %LinkTypes refers to a space-separated list of link types. White space characters are not permitted within link types.
HTML作者可以使用下述已经被识别出链接类型,这些链接类型在下表中都有规范的解释。在DTD中, %LinkTypes 指的是用空格分隔的链接类型列表。在链接类型里不允许出现空格字符。
These link types are case-insensitive, i.e., "Alternate" has the same meaning as "alternate".
这些链接类型是大小写不敏感的,例如: "Alternate"和"alternate"都代表同样的含义。
User agents, search engines, etc. may interpret these link types in a variety of ways. For example, user agents may provide access to linked documents through a navigation bar.
用户代理、搜索引擎等等可能会对这些链接类型进行不同方式的解读。例如:用户代理可能会通过导览条提供对链接文档的访问机制。
Authors may wish to define additional link types not described in this specification. If they do so, they should use a profile to cite the conventions used to define the link types. Please see the profile attribute of the HEAD element for more details.
HTML作者可能希望定义其他本规范内没有描述的链接类型。如果他们确实想这么做,那么他们应该使用profile注解用于定义链接类型的术语。请参考HEAD元素的profile属性来获得更多细节。
For further discussions about link types, please consult the section on links in HTML documents.
关于链接类型的更深入讨论,请参阅《HTML文档内的链接》部分。
The following is a list of recognized media descriptors ( %MediaDesc in the DTD).
下面是已经可以被识别的介质描述列表,媒体描述符在DTD中用参数实体%MediaDesc来表示。
Future versions of HTML may introduce new values and may allow parameterized values. To facilitate the introduction of these extensions, conforming user agents must be able to parse the media attribute value as follows:
在HTML的未来版本中可能会引入更多的介质名称并且可能允许参数化取值。为了简化这些可能的扩展,符合规范的用户代理必须能按照如下的机制来解析media属性的值:
media="screen, 3d-glasses, print and resolution > 90dpi"
is mapped to:
"screen" "3d-glasses" "print and resolution > 90dpi"
"screen" "3d-glasses" "print"
media="screen, 3d-glasses, print and resolution > 90dpi"
会被映射为:
"screen" "3d-glasses" "print and resolution > 90dpi"三个实体。
"screen" "3d-glasses" "print"
Note. Style sheets may include media-dependent variations within them (e.g., the CSS @media construct). In such cases it may be appropriate to use "media=all".
注释。样式表可能包含上述介质的更多变种(例如,CSS @media指令)。在这种情况下,将media设置成all可能更合适。
Script data ( %Script; in the DTD) can be the content of the SCRIPT element and the value of intrinsic event attributes. User agents must not evaluate script data as HTML markup but instead must pass it on as data to a script engine.
Script脚本数据(在DTD中%Script;参数实体)可以是SCRIPT元素的内容或者死内建时间属性的属性值。用户代理绝对不能将脚本数据当做HTML标记处理,而是要将它当成数据传递给相应的脚本引擎。
The case-sensitivity of script data depends on the scripting language.
Script脚本数据是否大小写敏感依赖于相应的脚本语言。
Please note that script data that is element content may not contain character references, but script data that is the value of an attribute may contain them. The appendix provides further information about specifying non-HTML data.
请注意,当Script脚本数据是元素内容的时候,不能含有字符引用。但当Script脚本数据是属性值时就可以携带字符引用。附录里提供了关于指定非HTML数据的更进一步信息。
Style sheet data (%StyleSheet; in the DTD) can be the content of the STYLE element and the value of the style attribute. User agents must not evaluate style data as HTML markup.
样式表数据(在DTD中为%StyleSheet;参数实体)可以是STYLE元素的内容,另外也可以是style属性的值。用户代理绝对不能将样式表数据当成HTML标记来处理。
The case-sensitivity of style data depends on the style sheet language.
样式数据是否是大小写敏感依赖于相应的样式表语言。
Please note that style sheet data that is element content may not contain character references, but style sheet data that is the value of an attribute may contain them. The appendix provides further information about specifying non-HTML data.
请注意,样式表数据作为元素内容时不可以携带字符引用,但作为属性值时可以携带字符引用。附录里提供了有关指定非HTML数据的更进一步信息。
Except for the reserved names listed below, frame target names (%FrameTarget; in the DTD) must begin with an alphabetic character (a-zA-Z). User agents should ignore all other target names.
除了下表列出的保留的名字外,框架目标名字(在DTD中的%FrameTarget参数实体)必须以字母开始(a-zA-Z)。用户代理应该忽略其他任何形式的目标名字。
The following target names are reserved and have special meanings.
下面的目标名字是被保留并有特使含义的。