Tuesday, June 16, 2009

6-16 Summary

Well, didn't post anything this morning as promised, but I got a late start to the day, and had a few meetings so I couldn't.

Today was more about the WSs than NeXML. I am still investigating the woden converter tool to convert WSDL1.1 to WSDL2.0 docs. This will be key for creating RESTful services down the road.

I am going to check in some code soon - not much but at least to get something on. Im envisioning the following directory structure:

root (trunk)

README.txt //Explanation of the project?

docs //Documents explaining this structure - may be better to have distributed help //documents
tutorials
DeployWS //step by step tutorial on the procedure for building and deploying //WSs

TransProcedure //procedure outlining the process of creating lifting and //lowering schema mappings

Clients //procedure outlining the creation of clients

javadocs //if needed

misc //others as required

environment //the required environment - may include dependencies, batch script, //etc, and certainly an explanation

tests // I plan on deploying/hosting WSs myself for some time - that information will be // explained here

xslt //just like the NeXML directory - will contain the liftingSchema (nexml2cdao) and //various loweringSchema transforms might be needed for specific use cases

spql //required sparql queries

xsd //NeXML (and perhaps other) schemas required

sawsdl //these are basically sample services - functionalities will vary; hopefully I can get //a lot different use cases using TreeBase, CIPRES, etc
//the input will be NeXML in various forms

README.txt //instructions on how to deploy, what dependencies are needed, etc

WSDL1.1 //SOAP services created with WSDL1.1 interfaces
//Includes the .war files

echo //basic echo service

matrix2tree //the first service recommended to me by Rutger - takes a //character state matrix and converts it to tree
//could be a wrapper service around CIPRES:

treebaseUseCase //Need to get more information

misc //other services may go here - maybe i can just go down the list on:

WSDL2.0 //SOAP services created with WSDL2.0 interfaces

echo //basic echo service

matrix2tree //the first service recommended to me by Rutger - takes a //character state matrix and converts it to tree
//could be a wrapper service around CIPRES:

treebaseUseCase //need to get more information

misc //other services may go here - maybe i can just go down the list on:

REST //REST services created with WSDL2.0 - probably future work

Composite // Compositions created with BPEL (a good indicator of the power of // SAWSDL)

clients // corresponding client files of the each of the use cases - will try to include both a // command line and web based client

WSDL1.1 //SOAP clients

echo //basic echo serviceclient

matrix2tree //client for this service

treebaseUseCase //client for this service

misc //clients

WSDL2.0 //SOAP sclients

echo //basic echo serviceclient

matrix2tree //client for this service

treebaseUseCase //client for this service

misc //clients

REST //REST client

Composite // composition client

No comments:

Post a Comment