From: Jérôme <rom...@ya...> - 2012-01-31 09:04:52
|
About Gedcom file format, there is many issues. I suppose you already saw the 'shortcomings of Gedcom'[1] or others related pages[2] on the BetterGedcom wiki? About implementing 'Sources on notes' for next releases, maybe this might wait new 'BetterGedcom' or 'GedcomX' specifications? At a glance, this sounds rather like end/footnotes[3], children of a source. ie. handled on citation (text, note) or new DB objects related to source only. So, maybe a part of GEPS_018. [1] http://bettergedcom.wikispaces.com/Shortcomings+Of+GEDCOM [2] http://bettergedcom.wikispaces.com/Sources+and+Citations#GEDCOM [3] http://bettergedcom.wikispaces.com/Citation+Graphics [4] http://gramps-project.org/wiki/index.php?title=GEPS_018:_Evidence_style_sources Regards, Jérôme Tim Lyons a écrit : > On 29 Jan 2012, at 10:27, Benny Malengier wrote: > >> It is also not because GEDCOM does something, that it is a good thing. > > > OK, I'll not add sources to notes! > > > > > > > Not trying to get you to change your mind, at least not for this > release:-), but just explaining some of the thinking. > > > >> The moment we allow sources attached to a note, we introduce two >> different ways to do something, > > There are already many different ways to record things: the point > about having more than one way to do record something is that some > people might find one way best while other people find a different way > best. I keep seeing this point made on advice given to users, with the > important thing being that each individual user should be consistent > in the way he stores information. > >> which will just make it more difficult >> to maintain the code and move forward. > > Having multiple user interfaces to achieve the same effect is a > maintenance problem, but I am not sure why sources on notes would be. > >> The probablity of duplicate >> notes becomes high, > > I'm not sure why this would be true. If duplicate notes were thought > to be a problem, then surely it would equally be a problem with the > current arrangements, and then some automated merge (like of > citations) could be implemented to help the user. > >> and the cyclic loops that Jerome talks about will >> be something users actually want to do, > > Incidentally, cyclic loops were already possible, for example, Media- > >Attribute->Source->Media->. I came up with recursion problems when > testing out TestDataGenerator, and had to slightly change the > frequency of generating some constructs so as not to get Python 'too > deep recursion' errors. > >> but which we can't handle in a >> logical way in software. > > I'm not sure that the software has any problems with this kind of > situation. The only real impact on software is in reports, but reports > are already a VERY SELECTIVE choice of exactly which elements are > output. I first got into coding Gramps because one of the reports > wasn't outputting something I was using (I think it was attributes of > person as it happens). > > Regards, > Tim. > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |