Copyright © 2006 Open Geospatial Consortium. All Rights Reserved.
33 The
positioningHint
field is provided to give a hint of what line position in textual XML a comment should be regenerated. Comments will normally be indented on a fresh line, but
options are provided to suggest that they be generated at the start of a fresh line in case the comment has full-width visual formatting, or at the end of the previous contentmarkup
object, in the case that the comment describes that object.
8.8 XML control tokens
8.8.1 XML-declaration token
The XML-declaration token is defined as follows:
XmlDeclarationToken { ?xml ...? TokenType type = XmlDeclarationCode; token-type code
String version; XML version Bool standalone; document is standalone
Bool standaloneIsSet; standalone is used }
This is equivalent to the “
?xml …?
” XML-declaration construct where the substring “
xml
” is case-insensitive and it should normally be the first token present in the BXML token stream. The semantics for the
version
and
standalone
fields are the same as for the attributes of the same names for the XML-declaration. The
version
field may be logically marked as not being present for the XML semantics by assigning them a zero-length
string, and the logical presence of the
standalone
field is indicated by the
standaloneIsSet
field. No character-set “
encoding
” value is given here, but the value implied for that attribute of the XML declaration is the
charEncoding
value from the
Header
structure.
8.8.2 Bang token
The “bang” token is defined as:
BangToken { name ..., e.g., DOCTYPE TokenType type = BangCode; token-type code
Count nameRef; name of tag, string-table ref String content; verbatim character content
}
This is equivalent to the XML construct of the form “
name …
”. “Bang” is a synonym used sometimes for the exclamation mark . This construct is infrequently used in practice.
The name is given by a string-table reference and the
content
is represented simply as a verbatim unparsed string. The name and content have the same semantics and restrictions as
in textual XML. An example name is “
DOCTYPE
” and this type has a complex structure that is not worth tokenizing in the BXML file since non-validating parsersgenerators likely will
not understand it, and the parsers that do will most likely also support the textual XML
Copyright © 2006 Open Geospatial Consortium. All Rights Reserved.
34 format and will therefore be able to handle the unparsed string anyway. “
ENTITY
” declarations also use this token, among others.
8.8.3 Bang-bracket token
