This week, I'm going to concentrate on my post on Wednesday, 18 July, titled Whither FHISO and GEDCOM X? Observations and Commentary.
1) Louis Kessler said:
"I'm surprised you think all the activity you talked about that happened since RootsTech (only 5 months ago) has quietened down.
"I guarantee that if you go to BetterGEDCOM or go to GEDCOMX and post a comment, you will get a number of responses quite quickly. GEDCOM X's coming out with its conversion tool only 6 weeks ago was very significant, and they are assessing and incorporating all the feedback as we speak.
"As far as FHISO goes, there is an excellent dedicated international group of people involved in that, and there are rumblings that they are working diligently behind the scenes to get the major players on board with them. They can use support from respected genealogical community members such as yourself. If you'd like to get involved, I'm sure they'll accept you with open arms."
It was not to be.
In the months since RootsTech, the FHISO organizers have worked to devise opportunities for and communicate with FamilySearch, but they have opted to continue developing GEDCOM X in a proprietary fashion. If widely adopted, it will become what is known as a de facto standard.
In its own right, FamilySearch makes decisions that are in its best interest. While we may continue to hope for better outcomes, accepting and respecting the decisions of others is a golden rule in community standards development.
What does this mean for Randy and others? In a community standards organization, everyone's needs are considered, and the democratic process rules. This is not required when the work is proprietary. In the case of GEDCOM X, FamilySearch decides which needs are met and which are not.
What does this mean for FHISO? We can assume that GEDCOM X satisfies the requirements of its author, FamilySearch. So, ironically enough, the organization from which the need for FHISO was expressed is unlikely to have need for, nor reason to support, FHISO.
No one likes complications, but without the support of FamilySearch, things for FHISO become complicated by rules and guidelines. For example, because FamilySearch engages in developing proprietary standards, it is possible FHISO will not be able to establish itself as a community standards organization.
The organizers have opened a dialog about the complications with American National Standards Institute (http://ansi.org/), and we are communicating with vendors as part of this process.
We thank you, Randy, for your blog article. It will help FHISO widen the public comment about developing community standards and the organization.
One community, one standard. We are stronger and better together. Let's sort out the issues and start making things happen.
Here's how your readers can find more information or get involved.
(1) Comments are always welcome on the FHISO blog or on the FHISO Open Discussion page at the BetterGEDCOM wiki. http://fhiso.org/blog/
(2) FHISO representatives attend the open BetterGEDCOM meeting held Monday mornings (1:00 EDT/US). A part of each meeting is set aside for questions, answers and discussion about FHISO.
(3) Join the organizing effort. We are now a nine member international group; usually on five different continents, though today we are on six. Most of our work is done asynchronously (e-mail or common workspace). We hold a GoToMeeting session weekly (Wednesday at 1:30 EDT/US); attendance is encouraged, but optional. Those interested should email email@example.com.
(4) Speak out and let us know about it. If you blog or develop a posting about FHISO, send a notice to us at firstname.lastname@example.org .
If you are interested in learning more about standards and conformity assessment, check out http://www.standardslearn.org/"