diff --git a/Board_Documents_2014/2014-09-25 ALTO Board Meeting Minutes.html b/Board_Documents_2014/2014-09-25 ALTO Board Meeting Minutes.html index 41a681c..0554d39 100644 --- a/Board_Documents_2014/2014-09-25 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2014/2014-09-25 ALTO Board Meeting Minutes.html @@ -87,17 +87,17 @@ Board meeting minutes and agendas are not yet on Github.
  • - Miscellanous folder contains internal documents such as description of change request process, membership criteria. All these items are not yet on GitHub, but should be moved to “Board” repository in Github. + Miscellaneous folder contains internal documents such as description of change request process, membership criteria. All these items are not yet on GitHub, but should be moved to “Board” repository in Github.
  • - Member proposals do/can contain private information that we do wish to make publically available. Either (1) delete member proposals, or (2) get a private Github respoitory so that information can be hidden. + Member proposals do/can contain private information that we do wish to make publicly available. Either (1) delete member proposals, or (2) get a private Github respoitory so that information can be hidden. Suggestion was to delete member proposals.
  • Old comments and minutes need to be moved. Comments to be deleted (notes are not clear about this).
  • - Use the 'board' repository as a miscellanous container; it is currently unused. + Use the 'board' repository as a miscellaneous container; it is currently unused.
  • Discussion about Action Items and Meetings: Jukka proposed to document Action Items more formally. diff --git a/Board_Documents_2015/2015-02-05 ALTO Board Meeting Minutes.html b/Board_Documents_2015/2015-02-05 ALTO Board Meeting Minutes.html index 105a965..e64f088 100644 --- a/Board_Documents_2015/2015-02-05 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2015/2015-02-05 ALTO Board Meeting Minutes.html @@ -75,7 +75,7 @@

    -Jukka remarks that the date on action items is not necesary. Frederick responds that the date corresponds to the meeting from which the action item arose. +Jukka remarks that the date on action items is not necessary. Frederick responds that the date corresponds to the meeting from which the action item arose.

    diff --git a/Board_Documents_2015/2015-03-05 ALTO Board Meeting Minutes.html b/Board_Documents_2015/2015-03-05 ALTO Board Meeting Minutes.html index a7b7bcd..ecb48f6 100644 --- a/Board_Documents_2015/2015-03-05 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2015/2015-03-05 ALTO Board Meeting Minutes.html @@ -59,7 +59,7 @@

    Frederick asks if it is possible to add capabilities similar to ePub - and CSS Writing Modes to ALTO and maintain backward compability. + and CSS Writing Modes to ALTO and maintain backward compatibility. For example, Jean Philippe says that it is quite common to include Western words in the text of Japanese newspapers. Further research needed.

    diff --git a/Board_Documents_2015/2015-05-06 ALTO Board Meeting Minutes.html b/Board_Documents_2015/2015-05-06 ALTO Board Meeting Minutes.html index ed17e61..fd7006a 100644 --- a/Board_Documents_2015/2015-05-06 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2015/2015-05-06 ALTO Board Meeting Minutes.html @@ -74,7 +74,7 @@ Jukka will draft a proposal for discussion of board member terms and voting quorum at the next board meeting (cf. action item 17).

    -Recruiting new board members was the next topic of discussion. No attending member had objections to recruiting a board member from commerical companies. +Recruiting new board members was the next topic of discussion. No attending member had objections to recruiting a board member from commercial companies. Brian suggested someone from Northern Micrographics or from iArchives / Ancestry. Brian will contact someone from Northern Micrographics about board membership; Frederick will contact someone from iArchives / Ancestry about board membership.

    diff --git a/Board_Documents_2015/2015-09-14 ALTO Board Meeting Minutes.html b/Board_Documents_2015/2015-09-14 ALTO Board Meeting Minutes.html index f078e0c..300b402 100644 --- a/Board_Documents_2015/2015-09-14 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2015/2015-09-14 ALTO Board Meeting Minutes.html @@ -46,8 +46,8 @@

    Reviewed the board action items. Closed action item #12 and action item #5 -because the board decided in an earlier meeting that transfering documents from PBWorks (previous ALTO repository) would be too much work. -Remaing action items (issues) in the board repository remain open. +because the board decided in an earlier meeting that transferring documents from PBWorks (previous ALTO repository) would be too much work. +Remaining action items (issues) in the board repository remain open.

    Frederick re-announced the time (Nov 6, 2015) and location of the ALTO board face-to-face meeting @ iPRES 2015 in Chapel Hill NC () diff --git a/Board_Documents_2015/2015-12-02 ALTO Board Meeting Agenda.html b/Board_Documents_2015/2015-12-02 ALTO Board Meeting Agenda.html index 51bcbd4..95117ed 100644 --- a/Board_Documents_2015/2015-12-02 ALTO Board Meeting Agenda.html +++ b/Board_Documents_2015/2015-12-02 ALTO Board Meeting Agenda.html @@ -16,7 +16,7 @@

  • Review proposed changes to ALTO Board Membership. See items in italics and marked [PROPOSED] on the ALTO Board Membership page. [Frederick leads discussion]
  • Discuss new board member recruited by Jean Philippe. [Jean Philippe leads discussion]
  • Decide when the schema changes necessary for Shape change request (issue 22) will be published. Will we combine it with some other (simple) issue? [Evelien leads (brief) discussion.]
    • -
  • Summarize the face-to-face meeting discussion of the fragement identifier API for ALTO change request (issue 33). [Jean Philippe leads discussion.]
    • +
  • Summarize the face-to-face meeting discussion of the fragment identifier API for ALTO change request (issue 33). [Jean Philippe leads discussion.]
  • Summarize the face-to-face meeting discussion and continue to discuss OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • diff --git a/Board_Documents_2015/2015-12-02 ALTO Board Meeting Minutes.html b/Board_Documents_2015/2015-12-02 ALTO Board Meeting Minutes.html index 9ddf1c1..52c218b 100644 --- a/Board_Documents_2015/2015-12-02 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2015/2015-12-02 ALTO Board Meeting Minutes.html @@ -16,7 +16,7 @@
  • Review proposed changes to ALTO Board Membership. See items in italics and marked [PROPOSED] on the ALTO Board Membership page. [Frederick leads discussion]
  • Discuss new board member recruited by Jean Philippe. [Jean Philippe leads discussion]
  • Decide when the schema changes necessary for Shape change request (issue 22) will be published. Will we combine it with some other (simple) issue? [Evelien leads (brief) discussion.]
    • -
  • Summarize the face-to-face meeting discussion of the fragement identifier API for ALTO change request (issue 33). [Jean Philippe leads discussion.]
    • +
  • Summarize the face-to-face meeting discussion of the fragment identifier API for ALTO change request (issue 33). [Jean Philippe leads discussion.]
  • Summarize the face-to-face meeting discussion and continue to discuss OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • @@ -94,7 +94,7 @@ He suggests that it might be useful to contact IIIF and ask their opinion about the usefulness of such a AFIF. Frederick remarked that a AFIF would amount to a guarantee by the ALTO board that the ALTO schema will not change so much that it would break the API. Clemens said that the ALTO schema can be considered as the AFIF; he cited an example of work that he is doing in his own library. -Jean Philippe said that IIIF syntax is very simple and the AFIF would similarily be simple. +Jean Philippe said that IIIF syntax is very simple and the AFIF would similarly be simple. Evelien said that AFIF would amount to a guarantee that identifiers in ALTO files are permanent. Clemens remarked that IIIF permits a reference to an image or a part of an image which is not possible without IIIF. He further said that this is possible already with ALTO because ALTO data already has internal "markers" or identifiers which can be referenced. diff --git a/Board_Documents_2016/2016-01-27 ALTO Board Meeting Agenda.html b/Board_Documents_2016/2016-01-27 ALTO Board Meeting Agenda.html index 7c3a18d..06913fd 100644 --- a/Board_Documents_2016/2016-01-27 ALTO Board Meeting Agenda.html +++ b/Board_Documents_2016/2016-01-27 ALTO Board Meeting Agenda.html @@ -15,7 +15,7 @@
  • Review action items [Frederick leads discussion]
  • Discuss new board members recruited by Jean Philippe and Frederick. [Jean Philippe and Frederick lead discussion]
  • Review (briefly) the release of the schema changes necessary for Shape change request (issue 22). Note that the schema change has been in public comment since our last teleconference and will be released as schema version 3.1 following our Jan 27 teleconference. [Evelien leads discussion.]
    • -
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • diff --git a/Board_Documents_2016/2016-01-27 ALTO Board Meeting Minutes.html b/Board_Documents_2016/2016-01-27 ALTO Board Meeting Minutes.html index 40c4c1b..01859d7 100644 --- a/Board_Documents_2016/2016-01-27 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2016/2016-01-27 ALTO Board Meeting Minutes.html @@ -15,7 +15,7 @@
  • Review action items [Frederick leads discussion]
  • Discuss new board members recruited by Jean Philippe and Frederick. [Jean Philippe and Frederick lead discussion]
  • Review (briefly) the release of the schema changes necessary for Shape change request (issue 22). Note that the schema change has been in public comment since our last teleconference and will be released as schema version 3.1 following our Jan 27 teleconference. [Evelien leads discussion.]
    • -
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • diff --git a/Board_Documents_2016/2016-02-24 ALTO Board Meeting Agenda.html b/Board_Documents_2016/2016-02-24 ALTO Board Meeting Agenda.html index 3c86bbe..a610f11 100644 --- a/Board_Documents_2016/2016-02-24 ALTO Board Meeting Agenda.html +++ b/Board_Documents_2016/2016-02-24 ALTO Board Meeting Agenda.html @@ -19,7 +19,7 @@ [Frederick leads discussion]
  • Review action items [Frederick leads discussion]
  • Review status of ALTO schema version 3.1 [Evelien and Frederick lead discussion]
    • -
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • diff --git a/Board_Documents_2016/2016-02-24 ALTO Board Meeting Minutes.html b/Board_Documents_2016/2016-02-24 ALTO Board Meeting Minutes.html index 051fbb8..f2b168f 100644 --- a/Board_Documents_2016/2016-02-24 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2016/2016-02-24 ALTO Board Meeting Minutes.html @@ -19,7 +19,7 @@ [Frederick leads discussion]
  • Review action items [Frederick leads discussion]
  • Review status of ALTO schema version 3.1 [Evelien and Frederick lead discussion]
    • -
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • diff --git a/Board_Documents_2016/2016-03-23 ALTO Board Meeting Agenda.html b/Board_Documents_2016/2016-03-23 ALTO Board Meeting Agenda.html index 9e96f00..38133db 100644 --- a/Board_Documents_2016/2016-03-23 ALTO Board Meeting Agenda.html +++ b/Board_Documents_2016/2016-03-23 ALTO Board Meeting Agenda.html @@ -17,7 +17,7 @@
  • Review Doodle poll results for a face-to-face meeting in 2016. [Frederick leads discussion]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • -
  • Continue discussion (if needed) of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Continue discussion (if needed) of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Continue discussion (if needed) of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
    • diff --git a/Board_Documents_2016/2016-03-23 ALTO Board Meeting Minutes.html b/Board_Documents_2016/2016-03-23 ALTO Board Meeting Minutes.html index 85d6602..c01d06a 100644 --- a/Board_Documents_2016/2016-03-23 ALTO Board Meeting Minutes.html +++ b/Board_Documents_2016/2016-03-23 ALTO Board Meeting Minutes.html @@ -17,7 +17,7 @@
  • Review Doodle poll results for a face-to-face meeting in 2016. [Frederick leads discussion]
  • Continue discussion of Glyphs change request (issue 26). (See item 10 in minutes from London face-to-face meeting) [Joachim leads discussion.]
    • -
  • Continue discussion (if needed) of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    • +
  • Continue discussion (if needed) of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
  • Continue discussion (if needed) of OCR confidence value change request (issue 23). [Jukka and Nate lead discussion.]
    • diff --git a/Board_Documents_2016/2016-04-2x ALTO Board Meeting Agenda.html b/Board_Documents_2016/2016-04-2x ALTO Board Meeting Agenda.html index ff50913..76796ed 100644 --- a/Board_Documents_2016/2016-04-2x ALTO Board Meeting Agenda.html +++ b/Board_Documents_2016/2016-04-2x ALTO Board Meeting Agenda.html @@ -13,7 +13,7 @@
    1. Review design principles for ALTO. [Frederick leads discussion]
      2. -
    2. Continue discussion (if needed) of the fragement identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
      3. +
    3. Continue discussion (if needed) of the fragment identifier API for ALTO change request (issue 33) and subsequent actions. [Jean Philippe leads discussion.]
    4. Continue discussion (if needed) of OCR confidence value change request (issue 23). [Jukka leads discussion.]
    diff --git a/misc/ALTO Board Membership Criteria.html b/misc/ALTO Board Membership Criteria.html index ace9f23..fc3c2b3 100644 --- a/misc/ALTO Board Membership Criteria.html +++ b/misc/ALTO Board Membership Criteria.html @@ -65,7 +65,7 @@

    ALTO Board Membership

    Exceptions to the length of board membership terms shall be made as necessary to accomodate this policy.
  • Current board members must approve new board members. New members shall be approved by a voice or email vote.
  • Board membership terms shall be renewable with the consent of the member whose term is expiring and with the agreement of the board members whose terms are not expiring.
    • -
  • Before December 31 of each year, a Board chair shall be choosen for the subsequent year from amongst current board members. The board shall strive to choose board chairs in fall of each year, and, if possible, at the annual face-to-face meeting. +
  • Before December 31 of each year, a Board chair shall be chosen for the subsequent year from amongst current board members. The board shall strive to choose board chairs in fall of each year, and, if possible, at the annual face-to-face meeting. Candidates for board chair include board members whose terms will expire in the current year provided that they will renew their board membership.
  • Current Board member term expirations: