Changes between Version 3 and Version 4 of SemanticWebServices

Show
Ignore:
Timestamp:
2009/03/18 12:36:29 (15 years ago)
Author:
markw
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SemanticWebServices

    v3 v4  
    44   * Create a list of datatypes representing the core datatypes for the WABI services 
    55   * Create OWL Classes representing these datatypes 
    6    * Documentation of SADI 
     6   * Documentation of SADI (This should include movies of the demo's so that people can see it in-action) 
    77 
    88 * Luke !McCarthy 
     
    1313 
    1414 = DECISIONS MADE =  
     15 == SADI API Decisions == 
    1516 
    1617 * Service provider will "decorate" input by adding a new predicate/object to the incoming data; this is no longer a client-side task 
     
    2021 * Service providers '''''must''''' semantically-type their output data according to the OWL document describing their output such that the client can recognize the nodes that have been decorated by the service.  Clients may chose (probably will want to) strip the rdf:type tag off of the returning data. 
    2122 
     23 == Web Services to Wrap == 
    2224 
     25 * We decided that WABI services cannot be efficiently wrapped ''en masse'' because many (most?) of them output non-standardized, tab-delimited flatfiles; adding semantics into these files would require us to write a special parser for each service... BZZZZT!  We suggest that, at a minimum, WABI services should output XML such that we can use generic parsers and generic tools (e.g. XSLT) to add semantics into these services. 
     26 * TOGO services are nicer, but don't have a WSDL (because they are RESTful).  As such, there is no way for us to wrap them other than one-by-one...  BZZZZZZT! 
     27 * We have asked Oswaldo to suggest which WABI services he thinks are most interesting/useful for his integration with the Spanish INB, and we will wrap these services during the hackathon as SADI and/or Moby services. 
     28