Sorry, the existing thread referred to here is "WHAT do you want to GED
in/out?" posted by singals. I decided to start a new thread for clarity and
forgot to change the reference
Tony Proctor
That's one of the things I dislike about XML: even its advocates
misuse it. Attributes are for metadata, not data.
Putting that aside, what advantage does this scheme give you over just
allowing user-defined tags? Or over the Gedcom equivalent: "2
_ADDRESS Claremont"? Sure, you get to run it through a validator, but
the validator won't understand the stuff inside the AdHoc tag, so
validation doesn't buy much. Especially since the validator can't
tell if the tags are being used correctly.
> The expectation would be that in programming terms at data entry time
> the application would simply throw up some form of double column control
> to allow the user to enter stuff.
Not all programs have GUIs.
I started a similar project a while back, but from a different direction. I
had been keeping my notes in a written form with a well-defined syntax, i.e.
one that could be parsed in principle. This was because I didn't trust the
functionality of any of he commercial products, and also didn't want to get
locked in to any one of them.
I started to think about how I wanted to store my own data. This thread is
touching on an XML format I experimented with - to the point of actually
creating some examples. This is why I described it as a definitive
source/backup format as well as an import/export format and database load
format. The same format would serve all purposes.
The second phase was to define a run-time object model around that data.
Unfortunately, my paid work took over at that point.
My final stage would have been to create a POC incorporating a relational
database. However, both the definitive source format and the object model
would be generic, and could be standardised in principle.
I was hoping to get back to this when my contract finishes. However, if
you're still interested in it yourself then I'd be willing to take it
offline and compare notes. From this thread, I think I realise that the
people who actually "get it", and can see the advantages, are in a minority.
I think that means it's either going to need a "killer product" or Microsoft
to force the quantum leap :-)
Tony Proctor
Sounds like PGV and webtrees do it, too, though some people point out
their displays aren't as "pretty" as the fluff sites.
I wasn't clear. I was merely saying that the family node as used in
Gedcom is a better way to represent the relation than separate child-
father and child-mother relations. Granted that Gedcom's FAM is a bit
ambiguous in that it includes foster children, etc., but it's still
more useful than distinct child-parent links.
> In effect, I don't believe it represents anything useful, and a bottom-up
> approach is much more practical and meaningful.
>
> The only universal events for a person are birth and death. All the others
> like baptism, marriage, divorce, burial, cremation, etc., are culturally
> dependent and so cannot be expected to be present. Multiple concurrent
> marriages may even be legal in some cultures.
Gedcom will handle multiple simultaneous marriages.
> For my own part, even my own marriage cannot be represented accurately in
> some products: I lived in England at the time, but I had a civil marriage in
> the US, followed a week later by a religious one in Ireland.
Such things were common in Scotland, with marriages a week apart in
different parishes. Nothing keeps a Gedcom FAM node from having two
MARR subnodes.
Nor can it prevent the program from playing Towers of Hanoi whenever
it encounters a date of 1 Apr in some event.
I was thinking more of the request side of the transaction. They are
in a position to say, "Use our schema and use it correctly, or you
won't get a response from us." With regular genealogy programs,
however, none has the clout to force the others to conform to any
standard, and users will reject any program that won't let them import
"invalid" data.
Obviously I disagree. If all relationships are stored, then the
GEDCOM-style FAM is trivially identified as the set of people
who have the same father and mother, along with that father
and mother.
So if you had a family that raised a child who came from an anonymous
sperm, you would have no link between the child and the father who
raised it?
>I wasn't clear. I was merely saying that the family node as used in
>Gedcom is a better way to represent the relation than separate child-
>father and child-mother relations. Granted that Gedcom's FAM is a bit
>ambiguous in that it includes foster children, etc., but it's still
>more useful than distinct child-parent links.
Why is it better?
I use a program that uses child-father and child-mother relationships only.
When I only know one of those relationships, that's what I enter.
But when I export it to GEDCOM it reports on how many "families" it created in
doing so.
It seems to work well. One thing it achieves is to keep the nature of
the relationship separate from the related persons. Also in Gendatam,
where a list of possible attributes is provided, "unset" and "unknown"
are always included, with "unset" tending to be the default value.
Hope this helps.
Peter
If you're without a schema then there's no such thing as validation.
I'm not sure but maybe you're confusing well-formedness and validity.
Well formed XML obeys certain structural constraints. For instance the
following isn't well formed XML:
<element1>
<element2>
</element1>
</element2>
The following is well formed XML:
<element1>
<element2>
</element2>
</element1>
However it would not be valid against a schema which doesn't make
provision for an element2 or which doesn't allow it to be nested inside
element1. If you don't have a schema at all it's just well formed and
neither valid nor invalid because the entire concept of validity doesn't
apply.
If you're supposed to be following a schema you can't invent your own
elements nor can you invent your own attributes.