User Tools

Site Tools


start

====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2014/02/24 12:37]
rmbell
start [2019/03/14 09:42] (current)
admin Add links to Working Specification / Reference Implementation
Line 1: Line 1:
 ====== API4KB Wiki ====== ====== API4KB Wiki ======
 This WIKI is the work space for assembling responses to the %%OMG%% %%API%% for Knowledge Bases (API4KB) {{api4kb:​rfp.pdf|RFP}} This WIKI is the work space for assembling responses to the %%OMG%% %%API%% for Knowledge Bases (API4KB) {{api4kb:​rfp.pdf|RFP}}
 +
 +
 +===== **NEW Specification (Work in progress) NEW** =====
 +
 +  * [[https://​docs.google.com/​document/​d/​1IPJwiBhkTKXryfuioqeMe5fL3KFHYrVOOGIwjnkvEBQ/​edit?​usp=sharing|Standard Specification (Google Docs)]]
 +  * [[https://​github.com/​API4KBs|Computable Artifacts and Reference Implementation (GitHub)]]
 +  * [[https://​api4kbs.github.io/​|Technical Documentation (GitHub pages)]]
  
  
Line 15: Line 22:
  
 If we want to integrate various reasoning systems in a loosely coupled, hybrid environment,​ though, we will need integration apis that can allow you to build up these more complex sets of services. ​ Thus, the APIs need to support both levels of development:​ (1) a very abstract interface to some service, and (2) more complex, lower level apis that provide access to the individual services and allow us to build up more complicated apps from these lower level services. If we want to integrate various reasoning systems in a loosely coupled, hybrid environment,​ though, we will need integration apis that can allow you to build up these more complex sets of services. ​ Thus, the APIs need to support both levels of development:​ (1) a very abstract interface to some service, and (2) more complex, lower level apis that provide access to the individual services and allow us to build up more complicated apps from these lower level services.
 +
  
 ===== Use Cases ===== ===== Use Cases =====
-The proposed solution must support [[API4KB_UseCases|these Use Cases]], and it must also support the following architecture styles+The proposed solution must support [[API4KB_UseCases|these Use Cases]], and it must also support the following ​[[architecture_styles|architecture styles]].
-   * Service Oriented Architecture (SOA) +
-   * REpresentational State Transfer (REST) +
-   * a simple software library +
-   * (optional) streaming to a cloud+
  
  
 ===== Issues ===== ===== Issues =====
-Our list of issues can be found [[API4KB_Issue|here]]:+Our list of issues can be found [[API4KB_Issues|here]]:
  
 ===== Strategy ===== ===== Strategy =====
Line 53: Line 57:
      * [[http://​informatics.mayo.edu/​cts2/​rest/​codesystem/​SNOMEDCT/​version/​2010_01_31/​entity/​1532007/​children?​      * [[http://​informatics.mayo.edu/​cts2/​rest/​codesystem/​SNOMEDCT/​version/​2010_01_31/​entity/​1532007/​children?​
 maxToReturn=5|Sample 2]] maxToReturn=5|Sample 2]]
-  * {{api4kb.zip|API4KB Work in progress - MagicDraw model}}+  ​* [[https://​github.com/​API4KBs/​md-models|Github repo for MagicDraw models]] 
 +     * {{api4kb.zip|API4KB Work in progress - MagicDraw model}} ​an older version?
  
  
Line 59: Line 64:
   * [[http://​ontolog.cim3.net/​cgi-bin/​wiki.pl?​OntoIOp|OntoIOp]]   * [[http://​ontolog.cim3.net/​cgi-bin/​wiki.pl?​OntoIOp|OntoIOp]]
   * [[http://​www.fipa.org/​specs/​fipa00001/​SC00001L.html|Foundation for Intelligent Physical Agents (FIPA) Abstract Architecture Specification]]   * [[http://​www.fipa.org/​specs/​fipa00001/​SC00001L.html|Foundation for Intelligent Physical Agents (FIPA) Abstract Architecture Specification]]
 +    * [[http://​www.fipa.org/​specs/​fipa00086/​XC00086C.html|FIPA Ontology Service Specification]]
 +  * The RDA (Resource Description and Access) Vocabularies
 +    * [[http://​www.rdaregistry.info/​|RDA Registry]]
 +    * [[http://​www.rda-jsc.org/​archivedsite/​rda.html|RDA Steering Committee and Development Site]]
 +    * [[http://​www.dlib.org/​dlib/​january10/​hillmann/​01hillmann.html|Summary article about the RDA effort, D-Lib Magazine]]
 +    * [[http://​metadataregistry.org/​rdabrowse.htm|Open Metadata Registry, Registered RDA Vocabularies]]
   * [[http://​www.w3.org/​2005/​rules/​wiki/​RIF_Working_Group|RIF]]   * [[http://​www.w3.org/​2005/​rules/​wiki/​RIF_Working_Group|RIF]]
     * [[http://​www.w3.org/​TR/​rif-overview/​|Overview]]     * [[http://​www.w3.org/​TR/​rif-overview/​|Overview]]
Line 64: Line 75:
   * [[http://​ruleml.org/​|RuleML]]   * [[http://​ruleml.org/​|RuleML]]
     * [[http://​www.ruleml.org/​papers/​Primer|Primer]]     * [[http://​www.ruleml.org/​papers/​Primer|Primer]]
-    * [[http://​ruleml.org/​1.0/​|Version 1.0]] +    * [[http://​ruleml.org/​1.0/​|Deliberation RuleML ​Version 1.0]] 
-    * [[http://www.slideshare.net/​swadpasc/​reaction-ruleml-ruleml2012paschketutorial|Reaction RuleML Version 1.0 slides]] [[http://​www.springerlink.com/​content/​k13040qqqv262882/|Reaction RuleML Version 1.0 paper]]+    * [[http://reaction.ruleml.org/|Reaction RuleML Version 1.0]]
     * [[http://​ruleml.org/​RuleResponder/​|Rule Responder]]     * [[http://​ruleml.org/​RuleResponder/​|Rule Responder]]
     * [[http://​www.cs.unb.ca/​~boley/​papers/​AbstractSyntaxRuleML.pdf|The Abstract Syntax of RuleML - Towards a General Web Rule Language Framework]]     * [[http://​www.cs.unb.ca/​~boley/​papers/​AbstractSyntaxRuleML.pdf|The Abstract Syntax of RuleML - Towards a General Web Rule Language Framework]]
Line 79: Line 90:
     * Linked Data Profile     * Linked Data Profile
     * Linked Data API (Jenni Tennison)     * Linked Data API (Jenni Tennison)
 +  * Other W3C Resources
 +    * [[http://​www.w3.org/​TR/​sparql11-entailment/​ | SPARQL 1.1 Entailment Regimes]]
 +    * [[http://​www.w3.org/​TR/​sparql11-service-description/​ | SPARQL 1.1 Service Description]]
   * [[http://​docs.geoserver.org/​stable/​en/​user/​introduction/​overview.html|Geoserver]] An example (SOAP or RESTful) API for a portal:   * [[http://​docs.geoserver.org/​stable/​en/​user/​introduction/​overview.html|Geoserver]] An example (SOAP or RESTful) API for a portal:
     * [[http://​en.wikipedia.org/​wiki/​Web_Feature_Service|Web Feature Service (WFS)]] This is the web service standard that is used for CRUD operations for spatially-aware online datastores. It is based on a conceptual model that is specific to geographic domain, and so is not directly applicable to our situation, but does provide a model that may be of benefit.     * [[http://​en.wikipedia.org/​wiki/​Web_Feature_Service|Web Feature Service (WFS)]] This is the web service standard that is used for CRUD operations for spatially-aware online datastores. It is based on a conceptual model that is specific to geographic domain, and so is not directly applicable to our situation, but does provide a model that may be of benefit.
Line 88: Line 102:
     * [[http://​en.wikipedia.org/​wiki/​Restlet|REST framework used in Geoserver: Restlets]]     * [[http://​en.wikipedia.org/​wiki/​Restlet|REST framework used in Geoserver: Restlets]]
     * [[http://​geoserver.org/​display/​GEOS/​GSIP+61+-+WFS+2.0#​GSIP61-WFS2.0-SOAP SOAP]]     * [[http://​geoserver.org/​display/​GEOS/​GSIP+61+-+WFS+2.0#​GSIP61-WFS2.0-SOAP SOAP]]
 +  * {{API4KB_Metamodel_for_Heterogeneous_Knowledge_Platforms.pdf|API4KB Metamodel For Heterogeneous Knowledge Platforms}}
 +
  
start.1393263429.txt.gz · Last modified: 2014/02/24 12:37 by rmbell