User Tools

Site Tools


api4kb_parsing

====== 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
api4kb_parsing [2013/03/17 16:41]
admin
api4kb_parsing [2013/05/20 12:45] (current)
rmbell
Line 2: Line 2:
    * Multiple forms of syntax checking    * Multiple forms of syntax checking
       * RDF/XML, Turtle (for RDF/OWL), ?       * RDF/XML, Turtle (for RDF/OWL), ?
-   * Parser attempts to determine whether or not the resource is valid per the language selected +   * Validation API 
-   * Translation API -- given a resource in a declared input language, provide an artifact in the target language (or as close as possible given distinctions in expressivity;​ with logging to say why it couldn'​t do something), may need state management in cases where the client is not asserting the translation to the KB: if the source is maintained in the KB, then translation could be done on demand -- source could be added incrementally,​ but translation could be executed on the fly and either instantiated in the KB or serialized out per the export capability of the CRUD APIs+      ​* Parser attempts to determine whether or not the resource is valid per the language selected 
 +      * Parser ensures that input file does not contain invalid characters (the character set is specified in the first line of an XML file) 
 +   * Translation API -- given a resource in a declared input language, provide an artifact in the target language (or as close as possible given distinctions in expressivity;​ with logging to say why it couldn'​t do something, what was lost, if anything, etc. in cases where the content language is different rather than strictly the format 
 +      * typically batchstateless 
 +      * can be invoked by CRUD APIs as needed 
 +      * may need state management in cases where the client is not asserting the translation to the KB: if the source is maintained in the KB, then translation could be done on demand -- source could be added incrementally,​ but translation could be executed on the fly and either instantiated in the KB or serialized out per the export capability of the CRUD APIs
    * Support for error handling    * Support for error handling
       * Should not “blow up” due to input validation errors       * Should not “blow up” due to input validation errors
api4kb_parsing.1363552897.txt.gz · Last modified: 2013/03/17 16:41 by admin