Lines Matching refs:tag

209 the standard seven tag roster identification information ("STR", see below), 3)
283 In some cases, very long tag values will require 80 or more columns, but these
284 are relatively rare.  An example of this is the "FEN" tag pair; it may have a
285 long tag value, but this particular tag pair is only used to represent a game
330 two adjacent backslashes.  Strings are commonly used as tag pair values (see
350 to delimit tag pairs (see below).  Both are self terminating.
380 A PGN game is composed of two sections.  The first is the tag pair section and
381 the second is the movetext section.  The tag pair section provides information
391 The tag pair section is composed of a series of zero or more tag pairs.
393 A tag pair is composed of four consecutive tokens: a left bracket token, a
395 the tag name and the string token is the tag value associated with the tag
396 name.  (There is a standard set of tag names and semantics described below.)
397 The same tag name should not appear more than once in a tag pair section.
399 A further restriction on tag names is that they are composed exclusively of
401 mapping of tag names into key and attribute names for use with general purpose
405 any adjacent pair of tokens in a tag pair.
408 bracket and the tag name, there are no white space characters between the tag
410 tag name and the tag value.
412 Tag names, like all symbols, are case sensitive.  All tag names used for
415 PGN import format may have multiple tag pairs on the same line and may even
416 have a tag pair spanning more than a single line.  Export format requires each
417 tag pair to appear left justified on a line by itself; a single empty line
418 follows the last tag pair.
420 Some tag values may be composed of a sequence of items.  For example, a
426 The tag pair format is designed for expansion; initially only strings are
427 allowed as tag pair values.  Tag value formats associated with the STR (Seven
429 However, there are long term plans to allow general list structures as tag
430 values for non-STR tag pairs.  Use of these expanded tag values will likely be
432 structure of a tag pair remains the same: left bracket, tag name, tag value,
441 additional tag names and semantics is permitted and encouraged when needed, the
445 For import format, the order of tag pairs is not important.  For export format,
446 the STR tag pairs appear before any other tag pairs.  (The STR tag pairs must
448 any additional tag pairs appear in ASCII order by tag name.
450 The seven tag names of the STR are (in order):
466 A set of supplemental tag names is given later in this document.
468 For PGN export format, a single blank line appears after the last of the tag
469 pairs to conclude the tag pair section.  This helps simple scanning programs to
470 quickly determine the end of the tag pair section and the beginning of the
474 8.1.1.1: The Event tag
476 The Event tag value should be reasonably descriptive.  Abbreviations are to be
479 single question mark should appear as the tag value.
492 8.1.1.2: The Site tag
494 The Site tag value should include city and region names along with a standard
498 appear as the tag value.  A comma may be used to separate a city from a region.
512 8.1.1.3: The Date tag
514 The Date tag value gives the starting date for the game.  (Note: this is not
516 with respect to the local time of the site given in the Event tag.  The Date
517 tag value field always uses a standard ten character format: "YYYY.MM.DD".  The
533 8.1.1.4: The Round tag
535 The Round tag value gives the playing round for the game.  In a match
539 the tag value.
556 8.1.1.5: The White tag
558 The White tag value is the name of the player or players of the white pieces.
565 the tag value.
567 The intent is to allow meaningful ASCII sorting of the tag value that is
588 8.1.1.6: The Black tag
590 The Black tag value is the name of the player or players of the black pieces.
591 The names are given here as they are for the White tag value.
604 8.1.1.7: The Result tag
643 symbol tokens on the same line in the movetext.  As with the tag pair section,
729 are needed for use in some tag pair and annotation constructs.
888 movetext of a game must match the value of the game's Result tag pair.  (While
889 the marker appears as a string in the Result tag, it appears as a symbol
893 9: Supplemental tag names
895 The following tag names and their associated semantics are recommended for use
902 (White or Black) tag, then there will be corresponding multiple fields in any
903 of the following tags.  For example, if the White tag has the three field value
904 "Jones:Smith:Zacharias" (a consultation game), then the WhiteTitle tag could
925 Federation) ratings.  Similar tag names can be constructed for other rating
950 This uses a date value, similar to the Date tag field, that gives the starting
979 The following tag pairs are used for traditional opening names.  The associated
980 tag values will vary according to the local language in use.
986 vary by locale.  This tag pair is associated with the use of the EPD opcode
992 This uses a string; this is used to further refine the Opening tag.  This will
993 vary by locale.  This tag pair is associated with the use of the EPD opcode
999 This uses a string; this is used to further refine the Variation tag.  This
1000 will vary by locale.  This tag pair is associated with the use of the EPD
1006 The following tag pairs are used for representing opening identification
1017 This tag pair is associated with the use of the EPD opcode "eco" described in a
1024 Chess_ database.  This tag pair is associated with the use of the EPD opcode
1036 This uses a time-of-day value in the form "HH:MM:SS"; similar to the Date tag
1039 separators for the Time tag value.  The value is taken from the local time
1040 corresponding to the location given in the Site tag pair.
1045 This tag is similar to the Time tag except that the time is given according to
1051 This tag is similar to the Date tag except that the date is given according to
1057 The follwing tag is used to help describe the time control used with the game.
1082 It should only be used for the last descriptor in a TimeControl tag value.  It
1085 would be represented with a TimeControl tag value of "300".
1088 It should only be used for the last descriptor in a TimeControl tag value and
1094 be given by "4500+60" in the TimeControl tag value.
1098 TimeControl tag value and is usually the only descriptor in the value.  The
1106 minute egg timer sandclock would have a tag value of "*180".
1119 This tag takes an integer that denotes the "set-up" status of the game.  A
1122 position is given in the "FEN" tag pair.  This tag must appear for a game
1123 starting with a set-up position.  If it appears with a tag value of "1", a FEN
1124 tag pair must also appear.
1129 This tag uses a string that gives the Forsyth-Edwards Notation for the starting
1131 document.  If a SetUp tag appears with a tag value of "1", the FEN tag pair is
1137 There is a single tag that discusses the conclusion of the game.
1143 While the Result tag gives the result of the game, it does not provide any
1144 extra information and so the Termination tag is defined for this purpose.
1146 Strings that may appear as Termination tag values:
1175 This tag uses a name or names in the format of the player name tags; this
1188 This tag takes a single integer that gives the number of ply (moves) in the
1393 or incomplete Date tag pair data are to be avoided.  Any question mark
1394 characters in a Date tag value will be treated as zero digits for collation
1446 is based on eight keys; these are the seven tag values of the STR and also the
1449 The first (most important, primary key) is the Date tag.  Earlier dated games
1455 The second key is the Event tag.  This is sorted in ascending ASCII order.
1457 The third key is the Site tag.  This is sorted in ascending ASCII order.
1459 The fourth key is the Round tag.  This is sorted in ascending numeric order
1464 The fifth key is the White tag.  This is sorted in ascending ASCII order.
1466 The sixth key is the Black tag.  This is sorted in ascending ASCII order.
1468 The seventh key is the Result tag.  This is sorted in ascending ASCII order.
2452 The usage is similar to that of the "ECO" tag pair of the PGN standard.
2509 The usage is similar to that of the "NIC" tag pair of the PGN standard.
2665 <PGN-game> ::= <tag-section> <movetext-section>
2667 <tag-section> ::= <tag-pair> <tag-section>
2670 <tag-pair> ::= [ <tag-name> <tag-value> ]
2672 <tag-name> ::= <identifier>
2674 <tag-value> ::= <string>
2808 1) string-1 (Event tag value)
2810 2) string-1 (Site tag value)
2812 3) string-1 (Date tag value)
2814 4) string-1 (Round tag value)
2816 5) string-1 (White tag value)
2818 6) string-1 (Black tag value)
2820 7) string-1 (Result tag value)
2825 20.4.2: Marker 0x02: tag pair
2827 Marker 0x02 is used to indicate a single tag pair.  There are two items that
2828 follow marker 0x02 to form the "tag pair" record; in order these are:
2830 1) string-1 (tag pair name)
2832 2) string-1 (tag pair value)