Lines Matching refs:data
24 chess game data using ASCII text files. PGN is structured for easy reading and
27 the sharing of public domain chess game data among chessplayers (both organic
33 Instead, PGN is proposed as a universal portable representation for data
35 applications that can quickly and easily process chess game data using PGN for
39 2: Chess data representation
43 generate, access, and propagate chess game data. Some of these programs are
45 Laws of Chess and handle users' data with reasonable care. Unfortunately, many
47 representation of chess game data. Sometimes these problems become more
48 visible when a user attempts to move significant quantities of data from one
50 data, then the chances for a successful transfer are small at best.
59 designs a data format using encryption or some other secret, proprietary
79 of the data without the need for third party assistance.
85 artificial requirements created by a secret data format.
93 must include handling data items that may not exist currently but could be
96 arbitrary restrictions concerning the quantity of stored data. Also, planned
104 6) Finally, the system should handle the same kinds and amounts of data that
135 same PGN data according to its source. The details of the two formats are
140 is no recommendation that either of these be an ultimate mode of chess data
142 various techniques at their disposal to enhance the display of chess data at
149 3.1: Import format allows for manually prepared data
151 The import format is rather flexible and is used to describe data that may have
153 language. A program that can read PGN data should be able to handle the
159 The export format is rather strict and is used to describe data that is usually
166 For a given PGN data file, export format representations generated by different
197 construction of simple data translation programs that can easily scan PGN data
218 PGN data is composed of characters; non-overlapping contiguous sequences of
224 PGN data is represented using a subset of the eight bit ISO 8859/1 (Latin 1)
231 character in ISO 8859/1; it is not used for PGN data representation.)
234 characters. They are not used for PGN data representation. The 32 code values
236 PGN data is discouraged as their graphic representation varies considerably
244 in string data and in commentary. They are not permitted for use in symbol
249 critical commentary or string values in game data that may be referenced in
253 display eight bit character data, but the display graphics may differ among
271 characters may not appear inside of string data.
276 PGN data are organized as simple text lines without any special bytes or
291 Comment text may appear in PGN data. There are two kinds of comments. The
307 There is a special escape mechanism for PGN data. This mechanism is triggered
309 data on the rest of the line is ignored by publicly available PGN scanning
311 developers and researchers to embed non-PGN commands and data in PGN streams.
319 PGN character data is organized as tokens. A token is a contiguous sequence of
333 string is limited to a maximum of 255 characters of data.
439 data. This is the STR (Seven Tag Roster). The interpretation of these tags is
442 STR is the common ground that all programs should follow for public data
644 a single empty line follows the last line of data to conclude the movetext
836 data appearing in export format is in all cases guaranteed to be importable
1030 The following tags assist with further refinement of the time and data
1196 external PGN data.
1355 File names chosen for PGN data should be both informative and portable. The
1364 11.1: File name suffix for PGN data
1367 PGN data.
1370 11.2: File name formation for PGN data for a specific player
1376 11.3: File name formation for PGN data for a specific event
1382 11.4: File name formation for PGN data for chronologically ordered games
1384 PGN data files used for chronologically ordered (oldest first) archives use
1387 "YYYY.pgn". A file containing PGN data for a given month would have a ten
1393 or incomplete Date tag pair data are to be avoided. Any question mark
1397 Large quantities of PGN data arranged by chronological order should be
1398 organized into hierarchical directories. A directory containing all PGN data
1426 * PGN/MGR/YYYY/News: news and status for year YYYY data
1440 * PGN/Tools: software utilities that access PGN data
1499 provided an ftp site (chess.uoknor.edu) for the storage of chess related data
1517 export and can be used to "regularize" PGN data into reduced export format by
1529 graphical user interface for scanning PGN data files. This program includes a
1539 The program "mail2pgn" produces a PGN version of chess game data generated by
1556 now handles PGN data. It is available from the chess.uoknor.edu ftp site in
1563 The program "cupgn" converts game data stored in the ChessBase format into PGN.
1689 The program "MV2PGN" can be used to convert game data generated by both current
1701 The Hansen utilities are used to convert among various chess data
1737 "CBASCII" is a general utility for converting chess data between ChessBase
1768 own PGN data as well. CHESSOP takes 3 Mbyte of hard disk, costs US$39 and can
1785 The program "CAT2PGN" is a utility that translates data from the format used by
1801 14: PGN data archives
1803 The primary PGN data archive repository is located at the ftp site
1973 16: Additional chess data standards
1975 While PGN is used for game storage, there are other data representation
1985 A single FEN record uses one text line of variable length composed of six data
1989 A text file composed exclusively of FEN data records should have a file name
2008 many hours of tedious data entry can be saved. Additionally, a position
2031 16.1.3.1: Piece placement data
2040 used to separate data of adjacent ranks.
2122 ASCII character set. It is intended for data and command interchange among
2126 A single EPD uses one text line of variable length composed of four data field
2130 A text file composed exclusively of EPD data records should have a file name
2137 use with opening library preparation and also for general data and command
2167 Each EPD data field is composed only of non-blank printing ASCII characters.
2168 Adjacent data fields are separated by a single ASCII space character.
2171 16.2.3.1: Piece placement data
2180 used to separate data of adjacent ranks.
2226 (fourth) data field by a single space character.
2238 data.
2631 for local presentation or scanning of chess move data may find it convenient to
2633 as PGN data that resides in archival storage or that is exchanged among
2705 representation standard of PGN data designed for the dual goals of storage
2706 efficiency and program I/O. A file containing PGC data should have a name with
2710 newlines, PGC files have data that does not vary due to local processing
2721 PGC data is composed of a sequence of PGC records. Each record is composed of
2730 At the lowest level, PGC binary data is organized as bytes, words (two
2763 Move sequence data is represented using a length header followed by move
2764 ordinal data. The length header is an unsigned integer that may be a byte or a
2767 are called "mvseq-1" items. Move sequence data using a word header are called
2770 Move set data is represented using a length header followed by move ordinal
2771 data. The length header is an unsigned integer that is a byte. The integer
2778 20.3: String data
2780 PGC string data is represented using a length header followed by bytes of
2781 character data. The length header is an unsigned integer that may be a byte, a
2784 header; these are called "string-1" items. String data using a word header are
2785 called "string-2" items and string data using a doubleword header are called
2800 format. This refers to a game that has only the Seven Tag Roster data, played
2802 alternative to the general game data begin/end record pairs described below.
2803 The general marker pair (0x05/0x06) is used to help represent game data that
2851 20.4.5: Marker 0x05: general game data begin
2853 Marker 0x05 is used to indicate the beginning of data for a game. It has no
2856 corresponding "general game data end" record are considered to be part of the
2860 cases where the latter is too restrictive to contain the data for a game.)
2863 20.4.6: Marker 0x06: general game data end
2865 Marker 0x06 is used to indicate the end of data for a game. It has no
2868 (and earlier appearing) "general game data begin" record are considered to be
2889 rav-begin/data/rav-end structures can be nested.
2899 pair. The rav-begin/data/rav-end structures can be nested.
2906 PGN. The data that is escaped is the sequence of characters immediately
2909 record is limited to use for non-archival data. There is one item that follows
2910 marker 0x0a to form the "escape-string" record; this is the string data being
2913 1) string-2 (escaped string data)