From: "Paolo Casaschi"
-------------------------------------------------------
It's an interesting feature, worth exploring.
I would consider both links to games in the same DB or
to games from another DB.
I did some work around the PGN standard, it's probably worth
considering how to save those games references into the PGN
export of the game/database and defining a "standard" method
for coding those references into PGN files. There's a proposed
extension to the PGN standard that allows for custom tags to
be defined within game comments, in the format
1. e4 e6 { [%proprietaryTag value of proprietary tag] } 2. d4 d5
A general syntax for your tag could be
[%gamelink plyNumber, gameNumber, fileName]
with fileName being an optional parameter defaulting to the same
database and gameNumber and plyNumber are self explanatory.
Your example in PGN could for example be:
1.e4 e5 2.Nf3 Nc6 3.Bc4 Nf6 4.Ng5 d5 (4...Bc5 { [%gameLink 8, 23, ] } )
5.exd5 b5
--
Paolo
-------------------------------------------------------
Thanks, Paolo, for your suggestions. Defining a generic PGN tag for
the links is very useful, I will do this.
A bit problematic is the idea to have links into games of other
databases. The following cases can occur with links:
1. The referenced game will be deleted physically.
2. The referenced game will change, so that the referenced position
is no longer existing.
If the referencee and the referenced game are in the same database,
it's no problem to handle these cases appropriately, but what should
I do if the referencee is in another database (and this database is
currently not accessible)?
1. Do no allow deleting the referenced game, and do not allow changes
so that the referenced position will be gone.
2. Do allow these operations, but in this case the link will become
invalid.
Both solutions are not nice.
Gregor
