I suggest we create and use in the future for RESTful PC web services endpoint URL like:
api.pathwaycommons.org/v2/ (api version: v2), and keep using www.pathwaycommons.org/pc2/ for the documentation, logs/stats, downloads, providers, Admin, and perhaps for metadata and help json web services, pages (i.e., all not related to searching and querying the BioPAX database).
This will allow to separate our clean stable core bioinformatic api (that we have to keep backward compatible unless we change version to v3, v4...) from the rest of api and pages (less stable supplementary web services and views for docs and web sites built on top of main api)...
I suggest we create and use in the future for RESTful PC web services endpoint URL like: api.pathwaycommons.org/v2/ (api version: v2), and keep using www.pathwaycommons.org/pc2/ for the documentation, logs/stats, downloads, providers, Admin, and perhaps for metadata and help json web services, pages (i.e., all not related to searching and querying the BioPAX database). This will allow to separate our clean stable core bioinformatic api (that we have to keep backward compatible unless we change version to v3, v4...) from the rest of api and pages (less stable supplementary web services and views for docs and web sites built on top of main api)...
See also: http://codeplanet.io/principles-good-restful-api-design/