When using the API you might see a slightly different JSON response depending on what type of URI you use.


For instance calling pathway info API method with the URI "http://www.conceptwiki.org/concept/7e08b683-a110-44d1-9a81-ecbf69cc9498"

primaryTopic": { 
  "_about": "http://www.conceptwiki.org/concept/7e08b683-a110-44d1-9a81-ecbf69cc9498",
  "exactMatch": {
  "_about": "http://identifiers.org/wikipathways/WP1019",
  "latest_version": {
  "_about": "http://rdf.wikipathways.org/Pathway/WP1019_r67219",
  "title_en": "FAS pathway and Stress induction of HSP regulation",
  "title": "FAS pathway and Stress induction of HSP regulation",
   "hasPart": [
  "http://identifiers.org/hmdb/HMDB01429",
  "http://identifiers.org/cas/104404-17-3",
  "http://identifiers.org/hmdb/HMDB00125"
  ],
  "inDataset": "http://www.wikipathways.org"
  }
  },



 calling it with the uri http://identifiers.org/wikipathways/WP1019

"primaryTopic": {
  "_about": "http://identifiers.org/wikipathways/WP1019",
  "latest_version": {
  "_about": "http://rdf.wikipathways.org/Pathway/WP1019_r67219",
  "title_en": "FAS pathway and Stress induction of HSP regulation",
  "title": "FAS pathway and Stress induction of HSP regulation",
  "hasPart": [
  "http://identifiers.org/hmdb/HMDB01429",
  "http://identifiers.org/cas/104404-17-3",
  "http://identifiers.org/hmdb/HMDB00125"
  ],
  "inDataset": "http://www.wikipathways.org"
  },
 


As you can see the JSON structure in the first example has the "exactMatch" but the JSON in the second example does not. This is because we had to invoke mapping (the IMS system) to obtain the data. I.e. in the Open PHACTS database, the pathway data (which is identical in both examples) is stored under the wikipathways URI. When you enter via a conceptwiki URI, you can only obtain this data via a mapping call to query direct links between concept wiki and wiki pathways. Thus, the API returns "exactMatch" to inform you that your data was found via a mapping step.


Parsers should test for the presence of this exactMatch property and act accordingly.


Note: In future versions, we may always return the exactMatch form. Thus, parsers should ensure that they support both JSON structures.