| Line 7 was replaced by line 7 |
| - __Agenda:__ A response to the following points put forth in an email from Robert and Aimee. |
| + __Agenda:__ A response to the following points put forth in an email from Robert and Aimee. Most other points raised in the last 2 months have been agreed upon or tabled in emails. |
| Lines 13-14 were replaced by line 13 |
| - Teleconference: |
| - JK agreed that yes, Napier is considering that there are some assumptions/rules on how different |
| + ;Teleconference: JK agreed that yes, Napier is considering that there are some assumptions/rules on how different groups (i.e. SEEK) would interpret the data from the schema. They will document these assumptions for later discussion. |
| Line 16 was replaced by line 15 |
| - groups (i.e. SEEK) would interpret the data from the schema. They will document these assumptions |
| + ;KU Email: The Assertion element name should be changed since it is already established as something different in Taxonomer. Perhaps something less ambiguous - Relationship, Link ...? |
| Line 18 was replaced by line 17 |
| - for later discussion. |
| + ;Teleconference: Napier agrees that this is a problematic element name, but would prefer to address this issue after more discussion at the TDWG conference in October. |
| Lines 20-21 were replaced by line 19 |
| - KU Email: |
| - The Assertion element name should be changed since it is already established as something |
| + ;KU Email: Metadata (and sub elements Creator and CreationTime) should be required |
| Line 23 was replaced by line 21 |
| - different in Taxonomer. Perhaps something less ambiguous - Relationship, Link ...? |
| + ;Teleconference: Fine with Napier. |
| Lines 25-26 were replaced by line 23 |
| - Teleconference: |
| - Napier agrees that this is a problematic element name, but would prefer to address this issue |
| + ;KU Email: Define elements before they are referenced - so put Vouchers and Publications right after Metadata. |
| Line 28 was replaced by line 25 |
| - after more discussion at the TDWG conference in October. |
| + ;Teleconference: Fine with Napier. |
| Lines 30-31 were replaced by line 27 |
| - KU Email: |
| - Metadata (and sub elements Creator and CreationTime) should be required |
| + ;KU Email: Add Repositories (before Vouchers) and AccordingTos (after Publications) and allow both of them to be referenced. |
| Lines 33-34 were replaced by line 29 |
| - Teleconference: |
| - Fine with Napier. |
| + ;Teleconference: KU does not see these as elements receiving GUIDs, only elements that may be reused in a document. Repositories sound fine to Napier, but they are not convinced that AccordingTos are an element that will be reused much. KU would like AccordingTos, but does not see it as a key issue. We agreed to revisit this after more reaction at TDWG. |
| Lines 36-37 were replaced by line 31 |
| - KU Email: |
| - Define elements before they are referenced - so put Vouchers and Publications right after |
| + ;KU Email: Add the ability to transfer an existing TaxonConcept by its GUID. The GUID would be sufficient, no data would be allowed, to prevent a GUID being sent with incorrect data. |
| Line 39 was replaced by line 33 |
| - Metadata. |
| + ;Teleconference: Napier explained that the GUID of an existing TaxonConcept (in the TaxonConcepts element) can be transfered in the TaxonConcept id attribute with the type attribute equal to "empty". KU now understands the thinking behind this, though would prefer for GUIDs in this element to be treated similarly to the GUIDs in the FromTaxonConcepts and ToTaxonConcepts elsewhere in the schema. There may not be an elegant way to prevent the transfer of a GUID with incompatible data, so we will table this disagreement for the time being. |
| Lines 41-42 were replaced by line 35 |
| - Teleconference: |
| - Fine with Napier. |
| + ;KU Email: Add the ability to transfer an existing "Assertion" by its GUID alone. |
| Lines 44-45 were replaced by line 37 |
| - KU Email: |
| - Add Repositories (before Vouchers) and AccordingTos (after Publications) and allow both of them to |
| + ;Teleconference: KU explained that this would allow the transfer of GUID-labeled relationships between data providers, just as a provider might wish to transfer a single GUID-labeled taxonConcept. Napier suggested that this could be done by putting the GUID in the Assertion id attribute, but acknowledged that the current solution is not ideal because there is no "type=empty" attribute that would indicate this element is a GUID and needs no further data. |
| Line 47 was replaced by line 39 |
| - be referenced. |
| + __Additional Discussion__ |
| Lines 49-50 were replaced by line 41 |
| - Teleconference: |
| - KU does not see these as elements receiving GUIDs, only elements that may be reused in a document. |
| + Robert Kukla offered to create an updated version of the schema, with the agreed upon modifications for internal use by SEEK Taxon. The publicly presented schema will not change for the time being. With the new internal schema, Aimee will return to coding the parser for use in the EnterProviderData API. |
| Line 52 was replaced by line 43 |
| - Repositories sound fine to Napier, but they are not convinced that AccordingTos are an element that |
| + Robert Kukla and Jessie will be leaving October 2 for TDWG in New Zealand. They will be presenting the schema as a global solution to the problem of exchanging taxonomic data. They would also like to represent the SEEK viewpoint (at the same conference, but at a separate time) on the definition of a taxonomic concept, and how the SEEK Taxon system will interact with the community. |
| Line 54 was replaced by line 45 |
| - will be reused much. KU would like AccordingTos, but does not see it as a key issue. We agreed to |
| + Jessie will go directly from New Zealand to Kansas, joined by Trevor Paterson, for the SEEK All-hands meeting. |
| Lines 56-114 were replaced by line 47 |
| - revisit this after more reaction at TDWG. |
| - |
| - KU Email: |
| - Add the ability to transfer an existing TaxonConcept by its GUID. The GUID would be sufficient, |
| - |
| - no data would be allowed, to prevent a GUID being sent with incorrect data. |
| - |
| - Teleconference: |
| - Napier explained that the GUID of an existing TaxonConcept (in the TaxonConcepts element) can be |
| - |
| - transfered in the TaxonConcept id attribute with the type attribute equal to "empty". KU now |
| - |
| - understands the thinking behind this, though would prefer for GUIDs in this element to be treated |
| - |
| - similarly to the GUIDs in the FromTaxonConcepts and ToTaxonConcepts elsewhere in the schema. There |
| - |
| - may not be an elegant way to prevent the transfer of a GUID with incompatible data, so we will table |
| - |
| - this disagreement for the time being. |
| - |
| - KU Email: |
| - Add the ability to transfer an existing "Assertion" by its GUID alone. |
| - |
| - Teleconference: |
| - KU explained that this would allow the transfer of GUID-labeled relationships between data |
| - |
| - providers, just as a provider might wish to transfer a single GUID-labeled taxonConcept. Napier |
| - |
| - suggested that this could be done by putting the GUID in the Assertion id attribute, but |
| - |
| - acknowledged that the current solution is not ideal because there is no "type=empty" attribute that |
| - |
| - would indicate this element is a GUID and needs no further data. |
| - |
| - |
| - Teleconference: |
| - Robert Kukla offered to create an updated version of the schema, with the agreed upon |
| - |
| - modifications for internal use by SEEK Taxon. The publicly presented schema will not change for the |
| - |
| - time being. With the new internal schema, Aimee will return to coding the parser for use in the |
| - |
| - EnterProviderData API. |
| - |
| - Robert Kukla and Jessie will be leaving October 2 for TDWG in New Zealand. They will be |
| - |
| - presenting the schema as a global solution to the problem of exchanging taxonomic data. They would |
| - |
| - also like to represent the SEEK viewpoint (at the same conference, but at a separate time) on the |
| - |
| - definition of a taxonomic concept, and how the SEEK Taxon system will interact with the community. |
| - |
| - Jessie will go directly from New Zealand to Kansas, joined by Trevor Paterson, for the SEEK |
| - |
| - All-hands meeting. |
| - |
| - The [next conference call | TaxonWGConferenceCallAvailableTimes] is tentatively scheduled for |
| - |
| - Thursday, 2 September 2004, 15:00 GMT. |
| + The [next conference call | TaxonWGConferenceCallAvailableTimes] is tentatively scheduled for Thursday, 2 September 2004, 15:00 GMT. |
