Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Wed, Sep 10, 2008 05:46 PM UTC:Poor ★
Gilman makes no mention of name of Omega inventor Gabriel Vicente Maura, although mentioning Duniho's name. [The Latin American Omega Chess is named two decades earlier than commercial Canadian Omega.] This BOC is stealing too much of Maura's concept in the core game Omega Chess from year 1974, although at least acknowledging it. Gilman's entire Rules section reads ''Rules, as Omega.'' That's it for the rules of ''Beyond Omega Chess.'' Inappropriate warping enlargement of Maura's game suitable only for a Comment under Maura's Omega by commonsense standards that would prevail away from CVPage. Beyond Omega is not being appropriate of separate write-up attributable to Gilman laying claim to be ''inventor.'' Gilman attempts rationalization defensively in his very first paragraph by citing Duniho's Storm the Ivory Tower. Copying as it does Smess, Storm the Ivory Tower is also unfortunate variety of self-acknowledged plagiarism. Sure there are fine lines. If either Beyond Omega or Storm the Ivory Tower were presented as satire or humour, they could be tolerable or acceptable. Instead, these ''artworks'' are shown by respective authors Gilman and Duniho as improvements of earlier products Omega and Smess. We now know there could be ''umpteen'' thousands of ''variants'' of any fundamental underlying Rules-set. Why not just put personal adaptations, intrinsically the same as prior art on some basic level, in Comment or two under the original work? Especially since they are not going to be played anyway. And even if having pretty good idea of one's own -- as Gilman has here with ''Alpha-Lambda'' representing ''incomplete'' Knight or Camel according to orientation. Sorry, Charles, it's not enough novelty, Gabriel got there first; and it is Maura's CV not Gilman's.

Edit Form

Comment on the page Beyond Omega

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.