It's probably a good idea to include the web service API (cpath2 software) and data release version(s) in the search, traverse, top_pathways query XML schema and results (XML, JSON).
Can add to the root element, e.g., attributes: release="9" apiVersion="7.0.0-SNAPSHOT"
This can be useful to a client apps that request for metadata (provenance), top pathways, or all pathways (or all objects of a particular type) - i.e., data which does not change between PC2 releases - so apps could request new data only when the version(s) change...
It's probably a good idea to include the web service API (cpath2 software) and data release version(s) in the search, traverse, top_pathways query XML schema and results (XML, JSON).
Can add to the root element, e.g., attributes: release="9" apiVersion="7.0.0-SNAPSHOT"
This can be useful to a client apps that request for metadata (provenance), top pathways, or all pathways (or all objects of a particular type) - i.e., data which does not change between PC2 releases - so apps could request new data only when the version(s) change...