Answers.Body: <p>Glorfindel cited the PGN standard, so if you feel you need to include fields that you're not familiar with, by all means consult it.</p>
  
  <p>But like <em>many</em> standards, it's far too comprehensive to be implemented fully in most situations.  For example, the standard provides for the [Date] of the game, and the [EventDate] of the tournament; both White's and Black's clock time at the end of the game; the 3-letter acronym for the player's country, the name of the player's team (in an Olympiad or World Team Championship, these will match, but otherwise the team is normally unrelated); the name of the source publication for the game, the [SourceDate] for the date of the publication that the game appeared in; the <em>Site</em> and the <em>EventSite</em>; ... you get the idea.</p>
  
  <p>Way over the top for all but the professionals, primarily those involved in publishing tournament bulletins and chess e-/magazines.</p>
  
  <p>I'd also encourage you to make sure your PGN fields include:</p>
  
  <p>[Event]
  [Date]
  [White]
  [Black]
  [Result]</p>
  
  <p>Of the seven mentioned, the following are optional, even in published games:
  [Site]
  [Round]</p>
  
  <p>The Site can be multiple things: the city name, such "Baku", the server organization name (if online) such as "playchess.com", the correspondence chess association (if CC) such as "ICCF", or the tournament name, such as "Dos Hermanas".  </p>
  
  <p>The Round is used when there are multiple games in one event, as in most tournaments, but can also be a combination of Board # <em>and</em> Round # in team tournaments.  So, in the Baku Olympiad, for example, "Round 1.1" signifies a game played on Board 1 in Round 1.  In most older tournament scores, the Round information is often missing, although it could be reconstructed from the tournament crosstable.</p>
  
  <p>Note that [Event] <em>must</em> be the first field for most PGN import processing.</p>
  
  <p>If the game score doesn't begin from the start position, you can insert a <a href="https://en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation" rel="nofollow">FEN</a> field to represent the position, who's on move, what castling rights remain, and any e.p. capture that is possible at the beginning position. Just look up <a href="https://en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation" rel="nofollow">Forsyth-Edwards Notation</a> for more information.</p>
  
  <p>Use spaces to separate the moves and move numbers as follows:</p>
  
  <ol start="9">
  <li>[white move] [black move] 10. etc.</li>
  </ol>
  
  <p>You may run into trouble with variations, if you transcribe them manually. Keep the following rules in mind.</p>
  
  <p>A. The variation immediately follows the move that it varies from, so:</p>
  
  <ol start="4">
  <li>e5 dxe5 (4... d5)</li>
  </ol>
  
  <p>shows the alternative move 4...d5 in the proper position in the score, immediately following the main (or parent-variation) move.</p>
  
  <p>B. Certain codes are used by some PGN translators to represent the position evaluations at the end of a variation. They don't always import and export them the same way, and they don't always accept the "+/-" Informator symbology.</p>
  
  <p>C. The game score should end with the result. e.g. "1-0", or "*" if it is only a line.</p>
  
  <p>D. The FEN diagram / game replayer used on Chess.StackExchange is non-conforming, so don't use your experience with it as a guide. Two examples: </p>
  
  <ul>
  <li>It doesn't require the [Event] field at all</li>
  <li>It requires all PGN information lines to have a 4-space prefix. The
  latter helps distinguish the games from the language of the rest of
  the post on C.SE; such text outside of a game is not an option in the
  PGN standard.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-05T23:15:29.197Z
Answers.LastActivityDate: 2016-10-07T13:55:11.033Z
Answers.LastEditDate: 2016-10-07T13:55:11.033Z
Answers.UserDisplayName: jaxter
Answers.Body: <p>PGN specification makes differences between import and output formats. For example, the seven tags event, site, date, round, white, black, result are mandatory for output in a specific order, but when importing you shouldn't be that strict - missing tags are ok, other order is ok, etc.</p>
  
  <p>Then, there are a number of frequently used additional tags, like tags for rating, opening, title, etc. Open some of your favourite PGN files in an editor and have a look.</p>
  
  <p>Then, when importing, I'd more or less accept <em>anything</em> that looks like a "key-value-pair" tag, and ignore (but maybe store) it if it's unknown.</p>
  
  <p>I don't think most chess software give perfect PGN output, but most of them will also accept rather "exotic" interpretations. What does this mean for your use-case? Ask yourself what games you want to transfer, what info is in there, and then you'll probably find good tags for that. Maybe consider how your friend is going to process the PGN files.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-05T18:44:25.547Z
Answers.LastActivityDate: 2016-10-05T18:44:25.547Z
Answers.UserDisplayName: Eiko
Answers.Body: <p>I just have seen that old question, and I think I have a new (more complete) answer to it.</p>
  <p>The PGN specification of course is the reference, because of its old state, I decided to have it published in a new fashion. See <a href="https://github.com/mliebelt/pgn-spec-commented" rel="nofollow noreferrer">my GitHub repository on PGN Spec Commented</a> for that. The following links are all linking to that repository:</p>
  <ul>
  <li><a href="https://github.com/mliebelt/pgn-spec-commented/blob/main/pgn-specification.md#81-tag-pair-section" rel="nofollow noreferrer">PGN Spec Chapter 8.1</a> about the tag pairs. It explains in detail the so called seven rooster tags.</li>
  <li><a href="https://github.com/mliebelt/pgn-spec-commented/blob/main/pgn-specification.md#9-supplemental-tag-names" rel="nofollow noreferrer">PGN Spec Chapter 9</a> which contains the so called supplemental tag names.</li>
  <li><a href="https://github.com/mliebelt/pgn-spec-commented/blob/main/pgn-spec-supplement.md#5-the-running-clock" rel="nofollow noreferrer">PGN Spec Supplement 5</a> the running clock. So if you want to stream a game, you may deliver the current clock as that.</li>
  <li><a href="https://github.com/mliebelt/pgn-spec-commented/blob/main/pgn-spec-supplement.md#6-clock-start-time" rel="nofollow noreferrer">PGN Spec Supplement 6</a> the clock start time. Allows to have additional information, if you want to show a game that has different start times for the players (e.g. because the game is in the middle).</li>
  </ul>
  <p>So I have no idea if these additional tags are used at all, but they are at least described.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-01-25T15:52:49.507Z
Answers.LastActivityDate: 2023-01-25T15:52:49.507Z
Answers.UserDisplayName: mliebelt
Answers.Body: <p>PGN standards are described <a href="http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm" rel="nofollow noreferrer">here</a>. There are seven more-or-less required tags:</p>
  
  <pre><code>[Event]
  [Site]
  [Date]
  [Round]
  [White]
  [Black]
  [Result]
  </code></pre>
  
  <p>and many different <a href="http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c9" rel="nofollow noreferrer">supplemental tags</a>, for example <code>[WhiteElo]</code> and <code>[BlackElo]</code> for the players' ratings, <code>[Board]</code> for the board number in team events, and <code>[TimeControl]</code> for information about the time-control used.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-08T20:11:32.307Z
Answers.Text: The set of seven tags you mention is required for a PGN _export_ to be standards-compliant, but the standard allows for an _import_ to be much less rigorous.  The standard states that this is done to accommodate the laxity of manually-prepared PGN, and to tolerate that laxity.
Answers.UserDisplayName: jaxter
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-05T05:41:47.663Z
Answers.LastActivityDate: 2017-07-16T09:07:22.373Z
Answers.LastEditDate: 2017-07-16T09:07:22.373Z
Answers.UserDisplayName: Glorfindel
Body: <p>In a PGN file, there are tags like:</p>
  
  <pre><code>[Event "Tournament"]
  [White "John Smith"]
  </code></pre>
  
  <p>And so on. I would like to know all the possible tags for PGN files so I can use them in a PGN file that my friend is demanding for.</p>
  
Tags: <pgn>
Title: What are all of the possible tags for PGN?
ThreadText: # What are all of the possible tags for PGN?
  
  (Asked by: username_0 on 2016-10-05)
  
  In a PGN file, there are tags like:
  [Event "Tournament"]
  [White "John Smith"]
  
  And so on. I would like to know all the possible tags for PGN files so I can use them in a PGN file that my friend is demanding for.
  
  **Tags:** pgn
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_4 on 2016-10-05. Score: 9 | Accepted answer
  
  PGN standards are described here. There are seven more-or-less required tags:
  [Event]
  [Site]
  [Date]
  [Round]
  [White]
  [Black]
  [Result]
  
  and many different supplemental tags, for example [WhiteElo] and [BlackElo] for the players' ratings, [Board] for the board number in team events, and [TimeControl] for information about the time-control used.
  
  > **Comments:**
  > **username_1**: The set of seven tags you mention is required for a PGN _export_ to be standards-compliant, but the standard allows for an _import_ to be much less rigorous.  The standard states that this is done to accommodate the laxity of manually-prepared PGN, and to tolerate that laxity.  
  
  ---
  
  ### Answer by username_1 on 2016-10-05. Score: 4
  
  username_4 cited the PGN standard, so if you feel you need to include fields that you're not familiar with, by all means consult it.
  
  But like *many* standards, it's far too comprehensive to be implemented fully in most situations. For example, the standard provides for the [Date] of the game, and the [EventDate] of the tournament; both White's and Black's clock time at the end of the game; the 3-letter acronym for the player's country, the name of the player's team (in an Olympiad or World Team Championship, these will match, but otherwise the team is normally unrelated); the name of the source publication for the game, the [SourceDate] for the date of the publication that the game appeared in; the *Site* and the *EventSite*; ... you get the idea.
  
  Way over the top for all but the professionals, primarily those involved in publishing tournament bulletins and chess e-/magazines.
  
  I'd also encourage you to make sure your PGN fields include:
  
  [Event]
  [Date]
  [White]
  [Black]
  [Result]
  
  Of the seven mentioned, the following are optional, even in published games:
  [Site]
  [Round]
  
  The Site can be multiple things: the city name, such "Baku", the server organization name (if online) such as "playchess.com", the correspondence chess association (if CC) such as "ICCF", or the tournament name, such as "Dos Hermanas".
  
  The Round is used when there are multiple games in one event, as in most tournaments, but can also be a combination of Board # *and* Round # in team tournaments. So, in the Baku Olympiad, for example, "Round 1.1" signifies a game played on Board 1 in Round 1. In most older tournament scores, the Round information is often missing, although it could be reconstructed from the tournament crosstable.
  
  Note that [Event] *must* be the first field for most PGN import processing.
  
  If the game score doesn't begin from the start position, you can insert a [FEN](https://en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation) field to represent the position, who's on move, what castling rights remain, and any e.p. capture that is possible at the beginning position. Just look up [Forsyth-Edwards Notation](https://en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation) for more information.
  
  Use spaces to separate the moves and move numbers as follows:
  
  9. [white move] [black move] 10. etc.
  
  You may run into trouble with variations, if you transcribe them manually. Keep the following rules in mind.
  
  A. The variation immediately follows the move that it varies from, so:
  
  4. e5 dxe5 (4... d5)
  
  shows the alternative move 4...d5 in the proper position in the score, immediately following the main (or parent-variation) move.
  
  B. Certain codes are used by some PGN translators to represent the position evaluations at the end of a variation. They don't always import and export them the same way, and they don't always accept the "+/-" Informator symbology.
  
  C. The game score should end with the result. e.g. "1-0", or "\*" if it is only a line.
  
  D. The FEN diagram / game replayer used on Chess.StackExchange is non-conforming, so don't use your experience with it as a guide. Two examples:
  
  * It doesn't require the [Event] field at all
  * It requires all PGN information lines to have a 4-space prefix. The
    latter helps distinguish the games from the language of the rest of
    the post on C.SE; such text outside of a game is not an option in the
    PGN standard.
  
  
  ---
  
  ### Answer by username_2 on 2016-10-05. Score: 1
  
  PGN specification makes differences between import and output formats. For example, the seven tags event, site, date, round, white, black, result are mandatory for output in a specific order, but when importing you shouldn't be that strict - missing tags are ok, other order is ok, etc.
  
  Then, there are a number of frequently used additional tags, like tags for rating, opening, title, etc. Open some of your favourite PGN files in an editor and have a look.
  
  Then, when importing, I'd more or less accept *anything* that looks like a "key-value-pair" tag, and ignore (but maybe store) it if it's unknown.
  
  I don't think most chess software give perfect PGN output, but most of them will also accept rather "exotic" interpretations. What does this mean for your use-case? Ask yourself what games you want to transfer, what info is in there, and then you'll probably find good tags for that. Maybe consider how your friend is going to process the PGN files.
  
  
  ---
  
  ### Answer by username_3 on 2023-01-25. Score: 0
  
  I just have seen that old question, and I think I have a new (more complete) answer to it.
  
  The PGN specification of course is the reference, because of its old state, I decided to have it published in a new fashion. See [my GitHub repository on PGN Spec Commented](https://github.com/username_3/pgn-spec-commented) for that. The following links are all linking to that repository:
  
  * [PGN Spec Chapter 8.1](https://github.com/username_3/pgn-spec-commented/blob/main/pgn-specification.md#81-tag-pair-section) about the tag pairs. It explains in detail the so called seven rooster tags.
  * [PGN Spec Chapter 9](https://github.com/username_3/pgn-spec-commented/blob/main/pgn-specification.md#9-supplemental-tag-names) which contains the so called supplemental tag names.
  * [PGN Spec Supplement 5](https://github.com/username_3/pgn-spec-commented/blob/main/pgn-spec-supplement.md#5-the-running-clock) the running clock. So if you want to stream a game, you may deliver the current clock as that.
  * [PGN Spec Supplement 6](https://github.com/username_3/pgn-spec-commented/blob/main/pgn-spec-supplement.md#6-clock-start-time) the clock start time. Allows to have additional information, if you want to show a game that has different start times for the players (e.g. because the game is in the middle).
  
  So I have no idea if these additional tags are used at all, but they are at least described.
  
  
  ---
  
  