Related changes
Jump to navigation
Jump to search
Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on your Watchlist are in bold.
List of abbreviations:
- N
- This edit created a new page (also see list of new pages)
- m
- This is a minor edit
- b
- This edit was performed by a bot
- (±123)
- The page size changed by this number of bytes
14 April 2026
|
|
21:44 | Main Page 7 changes history +3 [Lorikrammer (7×)] | |||
|
|
21:44 (cur | prev) 0 Lorikrammer talk contribs | ||||
| m |
|
21:43 (cur | prev) 0 Lorikrammer talk contribs | |||
| m |
|
21:42 (cur | prev) 0 Lorikrammer talk contribs | |||
| m |
|
21:29 (cur | prev) 0 Lorikrammer talk contribs | |||
| m |
|
21:28 (cur | prev) 0 Lorikrammer talk contribs | |||
| m |
|
21:11 (cur | prev) +1 Lorikrammer talk contribs | |||
| m |
|
21:10 (cur | prev) +2 Lorikrammer talk contribs | |||
|
|
N 21:36 | Extension Domain 3 changes history +2,892 [Lorikrammer (3×)] | |||
| m |
|
21:36 (cur | prev) 0 Lorikrammer talk contribs (→Extension Domain Examples) | |||
| m |
|
21:36 (cur | prev) −29 Lorikrammer talk contribs (→Extension Domain Examples) | |||
| N |
|
21:16 (cur | prev) +2,921 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Extension Domain ''(extension_domain)'' == The ''extension_domain'' is a space for a user to add additional structured information that is not defined in the BioCompute schema. It is '''optional'''. While the extension domain is not defined by IEEE-2791-2020, each extension in this domain must provide a reference to the schema that defines it in order to validate. The extension domain allows a user to define additional fields and is...") | |||
| N 21:26 | Top Level Fields diffhist +3,543 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Top Level Fields == These header fields uniquely define this BCO. These fields are required for every BCO and are represented at the top level object. Condensed example: { "object_id": "https://example.com/BCO_948701/1.0", "spec_version" : "https://w3id.org/ieee/ieee-2791-schema/2791object.json", "etag": "d41d8cd98f00b204e9800998ecf8427e", "provenance_domain": {...") | ||||
| N 21:23 | Error Domain diffhist +3,335 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Error Domain (''error_domain)'' == This section, also known as the ''acceptable range of variability'', is an optional domain comprised of two subdomains: empirical and algorithmic. The error domain IEEE schema and definition can be found [https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/error_domain.json here]. The possible keys within each subdomain are workflow-specific, human-readable free text. For data i...") | ||||
| N 21:22 | Parametric Domain diffhist +1,424 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Parametric Domain (parametric_domain) == This optional domain represents the list of parameters customizing the computational flow which can affect the output of the calculations. These fields can be custom to each kind of analysis and are tied to a particular pipeline implementation. The provenance domain IEEE schema and definition can be found [https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/parametric_domai...") | ||||
| N 21:19 | Execution Domain diffhist +7,419 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Execution Domain (''execution_domain'') == This section defines the ''execution_domain'' part of the BCO. The execution domain IEEE schema, and definition can be found [https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/execution_domain.json here]. The fields required for the execution of the BCO have been encapsulated together in order to clearly separate information needed for deployment, softwa...") | ||||
| N 21:17 | Description Domain diffhist +9,628 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Description Domain (''description_domain'') == This section defines the fields of the ''description_domain'' part of the BCO structure. The description domain IEEE schema and definition can be found [https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/description_domain.json here]. Structured field for description of external references, the pipeline steps, and the relationship of I/O objects. Info...") | ||||
| N 21:13 | Usability Domain diffhist +4,768 Lorikrammer talk contribs (Created page with "'''Go back to BCO Domains.''' == Usability Domain ''(usability_domain)'' == This section defines the ''usability_domain'' part of the BCO structure. The associated IEEE schema that contains the definition can be found [https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/usability_domain.json here]. The usability domain provides a specific scientific use case and a description of the function of the BCO. Condensed example: <pre>...") | ||||
|
|
m 20:59 | Input and Output Domain 2 changes history −12 [Lorikrammer (2×)] | |||
| m |
|
20:59 (cur | prev) 0 Lorikrammer talk contribs (→Input and Output Domain (io_domain)) | |||
| m |
|
20:48 (cur | prev) −12 Lorikrammer talk contribs Tag: Visual edit | |||
|
|
m 20:58 | Provenance Domain 2 changes history −12 [Lorikrammer (2×)] | |||
| m |
|
20:58 (cur | prev) 0 Lorikrammer talk contribs (→Provenance Domain (provenance_domain)) Tag: Visual edit | |||
| m |
|
20:50 (cur | prev) −12 Lorikrammer talk contribs | |||