Standardized Layout - First Run #312
Conversation
Military Service should be an event. It has been observed in several GED files as `_MILT`.
First take on changes to the Event Strucutre
First stab at changes to the attributes
Using Automation Tool v1
Automation Update 5/22/2023
Automation Update 5/22/2023
Automation Update, Standardized Layout
Automation Update Standardized
|
"Military Service" has a specific meaning, as well as a general one.
Do we need to distinguish these? |
|
Can you help me see this difference better? I see “military service” as “having been in the military”, regardless for how the person got there, branch, war-time/peace. The only question I my mind would be is this only restricted to the military of a country, or can rebellious militaries (anti government) be included as well. My suspicion is that maybe the “service” part is what is throwing you! In the USA we have the “Selective Service” which is the act of registering, but not yet participating in the military. That word can be removed and/or a better definition can be generate. |
|
|
||
| ### Used | ||
| - Part of the [GEDCOM X specification](https://github.com/FamilySearch/gedcomx/blob/master/specifications/fact-types-specification.md) as a distinct stucture with URI `http://familysearch.org/v1/CoupleNeverHadChildren |
There was a problem hiding this comment.
| - Part of the [GEDCOM X specification](https://github.com/FamilySearch/gedcomx/blob/master/specifications/fact-types-specification.md) as a distinct stucture with URI `http://familysearch.org/v1/CoupleNeverHadChildren | |
| - Part of the [GEDCOM X specification](https://github.com/FamilySearch/gedcomx/blob/master/specifications/fact-types-specification.md) as a distinct structure with URI `http://familysearch.org/v1/CoupleNeverHadChildren` |
|
|
||
| ## Lived together | ||
| ### Absence | ||
|
|
There was a problem hiding this comment.
I think the "encoded as NCHI 0 point would belong here under Absence
|
|
||
|
|
||
| ### Used | ||
| *In [GEDCOM X](https://github.com/FamilySearch/gedcomx/blob/master/specifications/event-types-specification.md)* with URI http://gedcomx.org/Census |
There was a problem hiding this comment.
| *In [GEDCOM X](https://github.com/FamilySearch/gedcomx/blob/master/specifications/event-types-specification.md)* with URI http://gedcomx.org/Census | |
| *In [GEDCOM X](https://github.com/FamilySearch/gedcomx/blob/master/specifications/event-types-specification.md)* with URI `http://gedcomx.org/Census` |
|
|
||
|
|
||
| ### Used | ||
| *In [GEDCOM X](https://github.com/FamilySearch/gedcomx/blob/master/specifications/event-types-specification.md)* with URI `http://gedcomx.org/Annulment` |
There was a problem hiding this comment.
Some had it that way in the original other did not. This should be universally applied or not!
| ''' | ||
| 1 MARR | ||
| 2 TYPE Common Law |
|
|
||
| ### Used | ||
| - Part of the GEDCOM v7.0 Specification | ||
| - Part of the GEDCOM X specification with URI http://gedcomx.org/Baptism |
There was a problem hiding this comment.
| - Part of the GEDCOM X specification with URI http://gedcomx.org/Baptism | |
| - Part of the GEDCOM X specification with URI `http://gedcomx.org/Baptism` |
| ## Burial | ||
| ### Description | ||
| - Burial can be defined as the disposition of a decedent which can include: Inhumation, Burial at Sea, Cremation, Donation to Research, Lost, Natural, Green, Burial Tree or Scaffolding, cave and probably many other ones depending on culture. -The BURI event can can therefore have BURI.TYPE enumerations of: a) Inhumation, b) Burial at Sea, c) Cremation, d) Donation to Research, e) Lost, f) Natural, g) Green, h) Burial Tree or Scaffolding, i) cave, j) other/phrase |
There was a problem hiding this comment.
| - Burial can be defined as the disposition of a decedent which can include: Inhumation, Burial at Sea, Cremation, Donation to Research, Lost, Natural, Green, Burial Tree or Scaffolding, cave and probably many other ones depending on culture. -The BURI event can can therefore have BURI.TYPE enumerations of: a) Inhumation, b) Burial at Sea, c) Cremation, d) Donation to Research, e) Lost, f) Natural, g) Green, h) Burial Tree or Scaffolding, i) cave, j) other/phrase | |
| - Burial can be defined as the disposition of a decedent which can include: Inhumation, Burial at Sea, Cremation, Donation to Research, Lost, Natural, Green, Burial Tree or Scaffolding, cave and probably many other ones depending on culture. | |
| -The `BURI` event can therefore have `BURI`.`TYPE` enumerations of: a) Inhumation, b) Burial at Sea, c) Cremation, d) Donation to Research, e) Lost, f) Natural, g) Green, h) Burial Tree or Scaffolding, i) cave, j) other/phrase |
|
|
||
| ### Used | ||
| - Part of the GEDCOM v7.0 Specification | ||
| - Part of the GEDCOM X specification with http://gedcomx.org/Burial |
There was a problem hiding this comment.
| - Part of the GEDCOM X specification with http://gedcomx.org/Burial | |
| - Part of the GEDCOM X specification with `http://gedcomx.org/Burial` |
|
|
||
| ### Value | ||
| In [GEDCOM X](https://github.com/FamilySearch/gedcomx/blob/master/specifications/fact-types-specification.md) with URI `http://gedcomx.org/Burial` |
There was a problem hiding this comment.
Seems like this should be under Used
| -------------------------- | ||
| ## Graduation | ||
| ### Description | ||
| A fact of a person's graduation from a scholast institution, may include, public, private, trade, or other schools of study. |
There was a problem hiding this comment.
| A fact of a person's graduation from a scholast institution, may include, public, private, trade, or other schools of study. | |
| A fact of a person's graduation from a scholastic institution, may include, public, private, trade, or other schools of study. |
|
Thanks dthaler! Updating as we speak! |
It's possible I'm creating a distinction that doesn't exist. But as I understand it, some countries have laws stating that all citizens must complete 1 or 2 years of military training before the age of 25. In the UK, this was called your "National Service". I've always called this "Military service", and I considered it a separate activity to joining your country's standing army as a full-time employee. edit/ webtrees has (inherited from phpGedView, inherited from other/unknown applications) two custom tags:
I have always used them as I described above. |
|
These changes were in part created via a database and script to make sure that all parts get added. Some of the markdown is automated, others is not! Having not worked with GitHub or its change mechanism before I'm not sure how changes are identified. My expectation was to regenerate the entire .md file with new proposed events/attributes and minor changes like the ones suggested already. Since this is just a draft it can sit that way for an extended time until the list of new and updated tags slows. This is all your call, I just wanted to start with all Tag entries having the same components. You don't even have to use what I made, but I'm happy to continue this process! |
|
I started a github review, but had some questions first. What do you mean by "Proposed" in the "Since" column? At first I thought you added it in all the empty cells (which I found unnecessary but at least consistent), but then I noticed it was just some of them (e.g. you left Clan blank and changed SSN to be blank) leaving me very confused. You and I seem to disagree on what * means. I defined it as
and added it only when there was an exact translation of the concept (such as "Childless" == "NCHI 0"), indicating what that translation was and which version added support for it. I think you put it in every blank cell instead, but I'm not sure why. Is it because EVEN and FACT can cover everything, or some other interpretation? |
|
Proposed means not found in the GEDCOM v5.5.1 or v7 so it was proposed to be added. I can leave this out if it is too confusing! I missed a few "Since" like SSN, Nobility Title, Number of Children. I did not review my stuff very well after my data entry. Clan is not a Event/Attribute as far as I know so it should be "proposed". I've made these changes, and others such as moving some of the "Where used" out of "Value" to "Used", when I started this database and script it was very early into the request for input and had not reconciled your documentation. GEDCOM X does not differentiat Event and Attribute. Will GEDCOM v7 continue to differentiate these two or follow GEDCOM X? Personally, if events start supporting Typification we will need a value after the each event tag just like attributes, they become very similar! I misunderstood the true meaning of the "*". I removed it from some of the tags in my database. I don't have to generate this information from my database. I just find it very difficult to enter changes/suggestions to the document when they had no standard layouts or editor. I want to participate in helping to better define Event/Attribute tags, implement better tag reuse via "Typification" and adding a way to add additional I have a newer draft version. |
Update 5/25/2023
Update 5/25/2023
Update 5/25/2023
Update 5/25/2023
5/25/2023 v2
05/25/2023 v2
5/25/2023 v2
Looking at Wikipedia they use “Military Service” to combine both voluntary and conscripted militaries. Saying:
My thoughts are that _MILI and _MILT are the same just two different programs trying to add a tag without knowing about the other! I’ve seen the following in documentation. But none have both, so they probably mean the same. |
Standardized sections for each Tag.
Added MILT, DNA, MEDI tag proposals.
Include enumeration suggestions for BIRT, MILT, DNA, MEDI tags