GENMSC-L Archives

Archiver > GENMSC > 2007-07 > 1184744719


From: Peter J Seymour <>
Subject: Re: Beyond GEDCOM
Date: Wed, 18 Jul 2007 08:47:20 +0100
References: <slrnf9ol6e.cvf.usenet@goodwill.larseighner.com><1184689853.767732.28500@x35g2000prf.googlegroups.com><2h6ni.9164$zA4.5373@newsread3.news.pas.earthlink.net><slrnf9pttu.fnh.usenet@goodwill.larseighner.com><2t7ni.8570$Od7.2064@newsread1.news.pas.earthlink.net><9Kdni.12915$LH5.785@trnddc02><9Beni.9298$zA4.985@newsread3.news.pas.earthlink.net><iuvq93105be5ochbsi73dh7u0rforplirg@4ax.com><Hagni.8705$Od7.4359@newsread1.news.pas.earthlink.net>
In-Reply-To: <Hagni.8705$Od7.4359@newsread1.news.pas.earthlink.net>


Robert Melson wrote:
> In article <>,
> Denis Beauregard <> writes:
>
>>On Wed, 18 Jul 2007 02:07:01 GMT, (Robert
>>Melson) wrote in soc.genealogy.computing:
>>
...
>
> The advantage of XML, though, as I understand it, is that there can
> be a centrally defined stylesheet which can be imported into the
> local environment and modified locally without affecting the base
> stylesheet. You could even, if I remember correctly, have multiple
> stylesheets - the base, a vendor version, an o/s specific version,
> one for your company and your personal version. In terms of the
> GED standard, you might have the central "standard" maintained at
> and by the LDS, a FTM version maintained by the vendor, and a
> local version you maintain yourself to fix problems you see in
> the other two.
>
...
>
> Bob Melson
>
There might be something in this is if there were several versions on a
straight line dependency, but once you have a tree of dependecies (as
you inevitably would) you're stuck. Also if you encountered a data field
that
isn't defined in the definitions you have because it's defined
elsewhere, you also also stuck. The problem with local versions is that
they probably won't be known in all the places they need to be known.
Basically XML doesnt help.
Regards
Peter

This thread: