Re: GEDOM as a database format

GEDCOM 5.5 is a standard for an 'interchange format' rather than a standard
for a 'database schema'. There's quite a big difference. As others have
rightly pointed out, you cannot work directly from a GEDCOM file. Those
programs that do use it for their main storage actually read it into some
type of in-memory database (e.g. a hash table) and manipulate it there
before writing the data back to a file at the end.

Tony Proctor

"singhals" <singhals@xxxxxxxxx> wrote in message
news:LLydnYXGNdlpmmHbnZ2dnUVZ_ozinZ2d@xxxxxxxxxx
And please what was GEDCOM Standard 5.5 if not a
standardized schema? Insufficiently standardized, perhaps,
but at least as close as anything that could be pulled off
today. At least GEDCOM S 5.5 had every interested
developer, a client, and 5 years behind it.


Cheryl

Tony Proctor wrote:

It's not an issue of "compliance" Wes. Developers could still go off and
do
their own thing. However, if the rest of the industry was starting to
use a
standardised schema then they would need a very, very good reason to
stay
out of the fold. In effect, I'm saying both consumers and developers
would
all benefit from an "open" data source format

Tony Proctor

"Wes Groleau" <groleau+news@xxxxxxxxxxxxx> wrote in message
news:SvGKi.7372$f%1.4450@xxxxxxxxxxx

Tony Proctor wrote:

convenient, in terms of development & testing as well as deployment, to

be

able to rely on a standardised SQL schema.

If software developers won't comply with the GEDCOM standard,
what makes you think they'll comply with your SQL schema?

--
Wes Groleau
----
The man who reads nothing at all is better educated
than the man who reads nothing but newspapers.
-- Thomas Jefferson





.

Relevant Pages

  • Re: need software to include to all spouses and all children in ancestor report and import irregul
    ... profess to support GEDCOM import/export really should comply with it. ... standard, then the program should handle them according to the standard. ... The DATE formats components are: ... that imports a date in DATE_PHRASE format should preserve it as such. ...
    (soc.genealogy.computing)
  • Re: GEDOM as a database format
    ... Applicability of independent genealogy utilities ... (GEDCOM ... there is no officially recognised standard ... Each vendor supports GEDCOM because the market expects it. ...
    (soc.genealogy.computing)
  • Re: Whither GEDCOM?
    ... players to support at least GEDCOM 5.5.1 in UTF-8? ... I'm sure you appreciate that genealogy relies on data sharing. ... GEDCOM became a de facto standard but it was never envisioned as that ... This is what FHISO are all about. ...
    (soc.genealogy.computing)
  • Re: Ancestry.co.uk + 1911 Census
    ... census records and the transcribed Scottish census records is ... I would have expected that they would have provided a GEDCOM ... I decide to nolonger use Ancestry then all of this needs to be ... that GEDCOM is not a standard. ...
    (soc.genealogy.britain)
  • Re: Open source GEDCOM 6 application?
    ... The fact is that interest in genealogy outside the LDS ... the process of getting a "standard" devised and accepted has become ... Yes, of course, that's the whole problem with GEDCOM. ... every genealogy application developer invents his own ...
    (soc.genealogy.computing)