Skip to content

Spec 015: BioPAX's exporter work ticked; the website's BioPAX planned - #750

Closed
adamjohnwright wants to merge 1 commit into
mainfrom
s015/biopax-tasks
Closed

adamjohnwright wants to merge 1 commit into
mainfrom
s015/biopax-tasks

Conversation

@adamjohnwright

Copy link
Copy Markdown
Contributor

Spec 015 (specs/015-graph-exports), tasks and research R10 only.

Ticked, from BioPAX3Exporter's own spec 001:

  • T045–T048 and T051 are ticked, each with the BioPAX3Exporter pull requests that did the work.
  • T031 is withdrawn in favour of BioPAX3Exporter's ci/compare.py and ci/contained.py, as T030 was for SBML.

Left open, with what is already done noted:

New: T052 becomes T069–T072, on the terms SBML set in T063–T067:

  • T069: the operation in the library service;
  • T070: node's endpoint;
  • T071: the route;
  • T072: the check on beta.

Research R10 is amended (29 Oct):

  • BioPAX joins the library service in deploy/java-library/ now, rather than waiting for spec 010's own repository.
  • Node is the service's client, as for SBML.
  • The legacy service's per-event answer is the reference.

🤖 Generated with Claude Code

BioPAX3Exporter's own spec 001 has done T045-T048 and T051, and the species
half of T049 and T050; each is ticked with its pull requests, and T031 is
withdrawn for its ci/compare.py, as T030 was for SBML. T049 and T050 keep the
website's part: the library's per-event files against the legacy service's.
T052 becomes T069-T072, on SBML's terms: the operation in the library
service, node's endpoint, the route, and the check on beta. Research R10 is
amended: BioPAX joins the service here, with node as its client.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adamjohnwright

Copy link
Copy Markdown
Contributor Author

Replaced by the next PR, which carries this one's commit and the fixes from its review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant