IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

  1. 14 May, 2020 2 commits
  2. 22 Apr, 2020 5 commits
  3. 22 Nov, 2019 2 commits
  4. 18 Nov, 2019 1 commit
    • Charles King's avatar
      Minor Fixes · 75198077
      Charles King authored
      Removed name and updates 'object_id' definition
      75198077
  5. 04 Nov, 2019 2 commits
  6. 16 Sep, 2019 5 commits
  7. 12 Aug, 2019 1 commit
    • Charles King's avatar
      ETag · 31aeb7de
      Charles King authored
      Comment ID: 26446300023
      Page: 3
      Line: 21
      Comment: ".. should be included in the generation of the hash"  - Hashsum calculation of JSON object trees are non-trivial and must be clearly defined. Out of scope for BioCompute?
      Must Be Satisfied: Yes
      Proposed Change: Reference a formal specification of JSON object hashing, or remove 'hash'. (alternative: rename to 'etag' and have looser definition)
      31aeb7de
  8. 17 Jul, 2019 2 commits
    • Charles King's avatar
      Comment #: i-56, are the bundled domain extensions part of P2791 or not? · 46a98682
      Charles King authored
      RE: Comment #: i-56, are the bundled domain extensions part of P2791 or not?
      
      Issue #57
      
      The `extension_domain` folder has been removed.
      
      Page: 3
      
      Line: 21
      
      Remove: "Two Extension Domain example files exist... FHIR...SCM"
      
      Replace with: "The Extension Domain is for the inclusion of any additional structured information. A valid JSON schema for each extension used in this domain has to be specified. The schema should be name spaced, and it is RECOMMENDED that resolving the namespaced URI will provide the extension's JSON Schema. The URL should be provided in the **required** `"extension_schema"` field."
      46a98682
    • Charles King's avatar
      Comment #: i-59, empirical_error and algorithmic_error definition? · 410081a9
      Charles King authored
      RE: Comment #: i-59, empirical_error and algorithmic_error definition?
      
      Issue #60
      
      Comment ID: 26446700023
      Page: 3
      Line:37
      Replace: "Fields in the Error Domain..."
      With: "Fields in the Error Domain are open-ended and not restricted nor defined by the current BioCompute standard. It is RECOMMENDED that the keys directly under empirical_error and algorithmic_error use a full URI. Resolving the URI SHOULD give a JSON Schema or textual definition of the field. Other keys are not allowed error_domain"
      410081a9
  9. 16 Jul, 2019 2 commits
    • Charles King's avatar
      Comment #: i-59, empirical_error and algorithmic_error definition? · 1b6b6ad9
      Charles King authored
      issues #60
      
      I think for this version we should not allow additional keys in the error_domain. Any other additions can be put in the extension_domain
      'It's RECOMMEND that the keys directly under empirical_error and algorithmic_error use a full URI for their "$ref": value. Resolving the URI SHOULD give a JSON Schema or textual definition of the field. At this time it is RECOMMENDED that no other keys be used in this domain"
      1b6b6ad9
    • Charles King's avatar
      Comment #: i-52, clarifications sought about the error domain · 6a2e2143
      Charles King authored
      issue #53
      Change: "The error_domain.json is an optional domain that further describes a bioinformatics workflow"
      
      To: "The error_domain.json is an optional domain to further describe empirical and algorithmic sources and measures of error for a bioinformatics workflow"
      
      - error_domain is no longer **required** in biocompute.json.
      6a2e2143
  10. 01 Apr, 2019 2 commits