Answers.Body: <p>I'd like to provide some more details. I will answer &quot;bottom up&quot; (last bullet first).</p>
  <ul>
  <li><p>FEN is indeed much more common, at least, more commonly <em><strong>seen</strong></em> by &quot;normal users&quot;: major online chess sites (chess.com, lichess.org, ...) propose to millions of users at each moment to export the position they're looking at in the FEN format, sometimes also in other formats (including PGN which describes the whole game, as opposed to just the position, with all moves, metadata, possibly analysis with variations and annotations). You will almost never be proposed to share a position in EPD format. However, these same web sites might internally store their opening database and maybe even their entire puzzle database in the EPD format.</p>
  </li>
  <li><p>The purpose of the two is different: FEN contains just exactly the minimum information one has to know about the position to continue playing the game. EPD may contain a lot more subjective and also complementary factual information, see below. So, it depends on what you want to store.</p>
  </li>
  <li><p>As the name says, EPD is an <em>extended</em> position description, and it does extend the FEN format, in a slightly relaxed sense: The first four data fields (Piece placement, Side to move, Castling ability, En passant target square) are exactly the same.</p>
  <p>The FEN format then has exactly two more data fields: Halfmove clock, and Fullmove counter. They are specified as two integers following the ep square, and that's what the FEN string ends with. These last two data are not &quot;rigidly&quot; taken over in the EPD format, but implemented through EPD &quot;Operations&quot;.</p>
  <p>The EPD format has a first part consisting of the above mentioned four main data fields. That part is followed by an arbitrarily long list of so-called &quot;Operations&quot; each of which consist of a mandatory <code>&lt;opcode&gt;</code>, followed by zero or more space separated arguments called operands, and a mandatory semicolon <code>;</code>.</p>
  <p>The <code>&lt;opcode&gt;</code> has the form of a lowercase letter followed by at least one and at most 14 more lowercase letters and/or digits and/or underscores <code>_</code>. Examples include: <code>bm</code> (best move),
  <code>ce</code> (centipawn evaluation), <code>c0</code> (primary comment),
  <code>fmvn</code> (full move number: this is the FEN's Fullmove counter),
  <code>hmvc</code> (FEN's halfmove clock),
  <code>id</code> (position identification), <code>pv</code> (predicted variation, i.e., continuation), <code>v0</code>-<code>v9</code> (variation name, e.g., name of openings and their variations) etc.</p>
  <p>The operands may be (signed or unsigned, integer or decimal) numbers or strings (enclosed in &quot;...&quot;) or moves in SAN (standard algebraic notation, like e4, Nbd2+ or bxc1=Q#, without quotes, and not preceded by move numbers nor '...' when it's black's move, e.g., in <code>pv</code>).</p>
  <p>It is somewhat surprising that the halfmove clock is not mandatory in the EPD format, although it is necessary to apply the 75 move rule. But we must admit that application of the 3- or 5-fold repetition would also require to know all previous positions - at least, when the last move wasn't a pawn move or capture.</p>
  </li>
  </ul>
  <p>So, in short, the EPD contains annotations and other, possibly subjective data, which might be of interest especially in databases for use in chess programs (Opening database; test cases for program testing, debugging and/or machine learning, etc...). The FEN is just the raw position.</p>
  <p>Sources:</p>
  <ul>
  <li><a href="https://en.wikipedia.org/wiki/Extended_Position_Description" rel="nofollow noreferrer">https://en.wikipedia.org/wiki/Extended_Position_Description</a></li>
  <li><a href="https://www.chessprogramming.org/Extended_Position_Description" rel="nofollow noreferrer">https://www.chessprogramming.org/Extended_Position_Description</a></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-16T01:25:00.467Z
Answers.LastActivityDate: 2021-12-16T01:25:00.467Z
Answers.UserDisplayName: Max
Answers.Body: <ul>
  <li>What are the main differences between the two?</li>
  </ul>
  
  <blockquote>
    <p>Extended Position Description is a standard for describing chess
    positions along with an extended set of structured attribute values
    using the ASCII (American Standard Code for Information Interchange)
    character set. It is intended for data and command interchange among
    chess playing programs. It is also intended for the representation of
    portable opening library repositories. The first four fields of the
    EPD specification are the same as the first four fields of the closely
    related FEN specification. Like FEN, EPD can also be used for general
    position description. However, unlike FEN, EPD is designed to be
    expandable by the addition of new operations that provide new
    functionality as needs arise. More information can be found at this <a href="http://www.drpribut.com/sports/standard.txt">site</a>.</p>
  </blockquote>
  
  <ul>
  <li>When should I use one over the other one?</li>
  </ul>
  
  <blockquote>
    <p>EPD is more expandable by the additon of new operations and is more
    versatile and is used primarily in chess programs.  See bullet point one.</p>
  </blockquote>
  
  <ul>
  <li>Which one is more common to see?</li>
  </ul>
  
  <blockquote>
    <p>Overall, I would say FEN is more common, but this is relative to what you are trying to do.</p>
  </blockquote>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2012-12-13T04:49:53.253Z
Answers.Text: I agree that FEN is more common.
Answers.UserDisplayName: Seth
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2012-12-08T02:56:39.677Z
Answers.LastActivityDate: 2012-12-08T02:56:39.677Z
Answers.UserDisplayName: xaisoft
Body: <p>I just read the description of FEN (<em>Forsyth–Edwards Notation</em>) and EPD (<em>Extended Position Description</em>), I have a basic idea of what they are, but I still have some points that are not entirely clear:</p>
  
  <ul>
  <li>What are the main differences between those two?</li>
  <li>When should I use one over the other one?</li>
  <li>Which one is more common to see?</li>
  </ul>
  
  <p>I am trying to decide which one to use for a personal project, and I can't take this jump without knowing everything about them.</p>
  
Tags: <notation><fen>
Title: Differences between FEN and EPD?
ThreadText: # Differences between FEN and EPD?
  
  (Asked by: username_0 on 2012-12-08)
  
  I just read the description of FEN (*Forsyth–Edwards Notation*) and EPD (*Extended Position Description*), I have a basic idea of what they are, but I still have some points that are not entirely clear:
  
  * What are the main differences between those two?
  * When should I use one over the other one?
  * Which one is more common to see?
  
  I am trying to decide which one to use for a personal project, and I can't take this jump without knowing everything about them.
  
  **Tags:** notation, fen
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2012-12-08. Score: 5 | Accepted answer
  
  * What are the main differences between the two?
  
  > Extended Position Description is a standard for describing chess
  > positions along with an extended set of structured attribute values
  > using the ASCII (American Standard Code for Information Interchange)
  > character set. It is intended for data and command interchange among
  > chess playing programs. It is also intended for the representation of
  > portable opening library repositories. The first four fields of the
  > EPD specification are the same as the first four fields of the closely
  > related FEN specification. Like FEN, EPD can also be used for general
  > position description. However, unlike FEN, EPD is designed to be
  > expandable by the addition of new operations that provide new
  > functionality as needs arise. More information can be found at this [site](http://www.drpribut.com/sports/standard.txt).
  
  * When should I use one over the other one?
  
  > EPD is more expandable by the additon of new operations and is more
  > versatile and is used primarily in chess programs. See bullet point one.
  
  * Which one is more common to see?
  
  > Overall, I would say FEN is more common, but this is relative to what you are trying to do.
  
  > **Comments:**
  > **username_3**: I agree that FEN is more common.  
  
  ---
  
  ### Answer by username_1 on 2021-12-16. Score: 2
  
  I'd like to provide some more details. I will answer "bottom up" (last bullet first).
  
  * FEN is indeed much more common, at least, more commonly ***seen*** by "normal users": major online chess sites (chess.com, lichess.org, ...) propose to millions of users at each moment to export the position they're looking at in the FEN format, sometimes also in other formats (including PGN which describes the whole game, as opposed to just the position, with all moves, metadata, possibly analysis with variations and annotations). You will almost never be proposed to share a position in EPD format. However, these same web sites might internally store their opening database and maybe even their entire puzzle database in the EPD format.
  * The purpose of the two is different: FEN contains just exactly the minimum information one has to know about the position to continue playing the game. EPD may contain a lot more subjective and also complementary factual information, see below. So, it depends on what you want to store.
  * As the name says, EPD is an *extended* position description, and it does extend the FEN format, in a slightly relaxed sense: The first four data fields (Piece placement, Side to move, Castling ability, En passant target square) are exactly the same.
  
    The FEN format then has exactly two more data fields: Halfmove clock, and Fullmove counter. They are specified as two integers following the ep square, and that's what the FEN string ends with. These last two data are not "rigidly" taken over in the EPD format, but implemented through EPD "Operations".
  
    The EPD format has a first part consisting of the above mentioned four main data fields. That part is followed by an arbitrarily long list of so-called "Operations" each of which consist of a mandatory `<opcode>`, followed by zero or more space separated arguments called operands, and a mandatory semicolon `;`.
  
    The `<opcode>` has the form of a lowercase letter followed by at least one and at most 14 more lowercase letters and/or digits and/or underscores `_`. Examples include: `bm` (best move),
    `ce` (centipawn evaluation), `c0` (primary comment),
    `fmvn` (full move number: this is the FEN's Fullmove counter),
    `hmvc` (FEN's halfmove clock),
    `id` (position identification), `pv` (predicted variation, i.e., continuation), `v0`-`v9` (variation name, e.g., name of openings and their variations) etc.
  
    The operands may be (signed or unsigned, integer or decimal) numbers or strings (enclosed in "...") or moves in SAN (standard algebraic notation, like e4, Nbd2+ or bxc1=Q#, without quotes, and not preceded by move numbers nor '...' when it's black's move, e.g., in `pv`).
  
    It is somewhat surprising that the halfmove clock is not mandatory in the EPD format, although it is necessary to apply the 75 move rule. But we must admit that application of the 3- or 5-fold repetition would also require to know all previous positions - at least, when the last move wasn't a pawn move or capture.
  
  So, in short, the EPD contains annotations and other, possibly subjective data, which might be of interest especially in databases for use in chess programs (Opening database; test cases for program testing, debugging and/or machine learning, etc...). The FEN is just the raw position.
  
  Sources:
  
  * <https://en.wikipedia.org/wiki/Extended_Position_Description>
  * <https://www.chessprogramming.org/Extended_Position_Description>
  
  
  ---
  
  