[MOBY-guts] biomoby commit
Mark Wilkinson
mwilkinson at pub.open-bio.org
Tue Dec 2 01:08:24 UTC 2003
mwilkinson
Mon Dec 1 20:08:24 EST 2003
Update of /home/repository/moby/moby-live/Perl/MOBY
In directory pub.open-bio.org:/tmp/cvs-serv21819/Perl/MOBY
Modified Files:
Central.html Central.pm
Log Message:
still calling Collection articles 'Complex' articles. This is confusing. It is now consistent thorughout the documentation
moby-live/Perl/MOBY Central.html,1.11,1.12 Central.pm,1.115,1.116
===================================================================
RCS file: /home/repository/moby/moby-live/Perl/MOBY/Central.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- /home/repository/moby/moby-live/Perl/MOBY/Central.html 2003/12/02 00:57:15 1.11
+++ /home/repository/moby/moby-live/Perl/MOBY/Central.html 2003/12/02 01:08:24 1.12
@@ -304,12 +304,10 @@
<ul>
<li><strong><a name="item_all_elements_are_required">all elements are required</a></strong><br />
</li>
-<li><strong><a name="item_a_service_must_have_at_least_one_input_or_output_o">a service must have at least one Input OR Output Object Class.</a></strong><br />
+<li><strong><a name="item_a_service_must_have_at_least_one_input_or_output_o">a service must have at least one Input OR Output Object Class. Either Input or Output may be blank to represent ``PUT'' or ``GET'' services respectively</a></strong><br />
</li>
<li><strong><a name="item_the_contactemail_address_must_be_valid%2c_as_it_is">the contactEmail address must be valid, as it is used to authorize deregistrations and changes to the service you registered.</a></strong><br />
</li>
-<li><strong><a name="item_the_object_classes%2c_namespaces%2c_and_service_ty">the Object Classes, Namespaces, and Service Types must all exist for the registration to be successful, so make sure you register these first, or ensure that they already exist in their respective ontologies.</a></strong><br />
-</li>
<li><strong><a name="item_the_%22authoritativeservice%22_tag_is_used_to_indi">the ``authoritativeService'' tag is used to indicate whether or not the registered service is ``authoritative'' for that transformation. i.e. if anyone else were to perform the same transformation they would have to have obtained the information to do so from you. This is similar to, but not necessarily identical to, mirroring someone elses data, since the data in question may not exist prior to service invocation.</a></strong><br />
</li>
<li><strong><a name="item_only_input_secondary_articles_are_defined_during_r">only Input Secondary articles are defined during registration; Output Secondary objects are entirely optional and may or may not be interpreted Client-side using their articleName tags.</a></strong><br />
@@ -319,24 +317,33 @@
<ul>
<li><strong><a name="item_structure">moby - for services that use the MOBY SOAP messaging format and object structure (i.e. the objects used in service transaction inherit from the root 'Object' Class in the MOBY Class ontology).</a></strong><br />
</li>
-<li><strong><a name="item_soap_%2d_for_other_soap_services_that_do_not_use_t">soap - for other SOAP services that do not use the MOBY messaging format. The other elements in the registration should be interpreted as follows:</a></strong><br />
-</li>
<ul>
<li><strong><a name="item_organization">authURI - a URI representing your organization (e.g. yourdomain.com); no http-prefix, and no trailing path information is allowed.</a></strong><br />
</li>
<li><strong><a name="item_servicename_%2d_an_arbitrary%2c_but_unique%2c_name">serviceName - an arbitrary, but unique, name for your service within your authURI namespace</a></strong><br />
</li>
+<li><strong><a name="item_url_%2d_the_url_to_a_soap_cgi_server_that_can_invo">URL - the URL to a SOAP CGI server that can invoke a method as described by your serviceName</a></strong><br />
+</li>
+</ul>
+<li><strong><a name="item_wsdl_%2d_for_other_soap_services_that_do_not_use_t">wsdl - for other SOAP services that do not use the MOBY messaging format. The other elements in the registration should be interpreted as follows:</a></strong><br />
+</li>
+<ul>
+<li><strong>authURI - a URI representing your organization (e.g. yourdomain.com); no http-prefix, and no trailing path information is allowed.</strong><br />
+</li>
+<li><strong>serviceName - an arbitrary, but unique, name for your service within your authURI namespace</strong><br />
+</li>
<li><strong><a name="item_url_%2d_the_url_from_which_a_wsdl_document_describ">URL - the URL from which a WSDL document describing your service can be retrieved by an HTTP GET call.</a></strong><br />
</li>
-<li><strong><a name="item_comments_about_input_and_output%3a">Comments about Input and Output:</a></strong><br />
+</ul>
+<li><strong><a name="item_comments_about_input_and_output_for_moby_and_non%2">Comments about Input and Output for MOBY and non-MOBY services</a></strong><br />
</li>
<ul>
<li><strong><a name="item_in_%22moby%22_services%2c_the_input_and_output_mes">in ``moby'' services, the input and output messaging structure is defined by the BioMOBY API, and the services use data Objects that are defined in the Class ontology as inheriting from the root ``Object'' Class.</a></strong><br />
</li>
-<li><strong><a name="item_for_%22soap%22_services%2c_there_is_additional_fle">For ``soap'' services, there is additional flexibility:</a></strong><br />
+<li><strong><a name="item_for_%22wsdl%22_services%2c_there_is_additional_fle">For ``wsdl'' services, there is additional flexibility:</a></strong><br />
</li>
<ul>
-<li><strong><a name="item_similar_to_a_%22moby%22_service%2c_your_%22soap%22">Similar to a ``moby'' service, your ``soap'' service must consume/produce named data types. These are represented as LSID's</a></strong><br />
+<li><strong><a name="item_similar_to_a_%22moby%22_service%2c_your_%22wsdl%22">Similar to a ``moby'' service, your ``wsdl'' service must consume/produce named data types. These are represented as LSID's</a></strong><br />
</li>
<li><strong><a name="item_you_do_not_need_to_register_these_data_types_in_mo">YOU DO NOT NEED TO REGISTER THESE DATA TYPES in MOBY Central; it is up to you what your LSID's represent, and MOBY Central WILL NOT try to resolve them!</a></strong><br />
</li>
@@ -356,7 +363,6 @@
</ul>
</ul>
</ul>
-</ul>
<pre>
Input XML :</pre>
<pre>
@@ -372,13 +378,13 @@
human readable COMPREHENSIVE description of your service]]>
</Description>
<Input>
- <!-- zero or more Primary (Simple and/or Complex) articles -->
+ <!-- zero or more Primary (Simple and/or Collection) articles -->
</Input>
<secondaryArticles>
<!-- zero or more INPUT Secondary articles -->
</secondaryArticles>
<Output>
- <!-- zero or more Primary (Simple and/or Complex) articles -->
+ <!-- zero or more Primary (Simple and/or Collection) articles -->
</Output>
</registerService></pre>
<pre>
@@ -553,10 +559,10 @@
<contactEmail>your at email.address</contactEmail>
<URL><a href="http://endpoint.of.service</URL>">http://endpoint.of.service</URL></a>;
<Input>
- <!-- one or more Simple and/or Complex Primary articles -->
+ <!-- one or more Simple and/or Collection Primary articles -->
</Input>
<Output>
- <!-- one or more Simple and/or Complex Primary articles -->
+ <!-- one or more Simple and/or Collection Primary articles -->
</Output>
<secondaryArticles>
<!-- one or more Secondary articles -->
===================================================================
RCS file: /home/repository/moby/moby-live/Perl/MOBY/Central.pm,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -r1.115 -r1.116
--- /home/repository/moby/moby-live/Perl/MOBY/Central.pm 2003/12/02 00:57:15 1.115
+++ /home/repository/moby/moby-live/Perl/MOBY/Central.pm 2003/12/02 01:08:24 1.116
@@ -905,13 +905,13 @@
human readable COMPREHENSIVE description of your service]]>
</Description>
<Input>
- <!-- zero or more Primary (Simple and/or Complex) articles -->
+ <!-- zero or more Primary (Simple and/or Collection) articles -->
</Input>
<secondaryArticles>
<!-- zero or more INPUT Secondary articles -->
</secondaryArticles>
<Output>
- <!-- zero or more Primary (Simple and/or Complex) articles -->
+ <!-- zero or more Primary (Simple and/or Collection) articles -->
</Output>
</registerService>
@@ -1019,13 +1019,12 @@
# <URL>http://URL.to.your/CGI.pl</URL>
# <authoritativeService>your.URI.here</authoritativeService>
# <Input>
-# <!-- zero or more pimary (simple or complex) articles -->
+# <!-- zero or more pimary (simple or collection) articles -->
# </Input>
# <Output>
-# <!-- zero or more pimary (simple or complex) articles -->
+# <!-- zero or more pimary (simple or collection) articles -->
# </Output>
# <secondaryArticles>
-# <!-- zero or more pimary (simple or complex) articles -->
# </secondaryArticles>
# <Description><![CDATA[
# human readable description of your service]]>
@@ -1119,7 +1118,7 @@
my $dbh = $SVC->dbh;
return (-1,'Bad node') unless $node->getNodeType == ELEMENT_NODE;
- # this is a Simple or a Complex object
+ # this is a Simple or a Collection object
my $simp_coll = $node->getTagName;
$debug && &_LOG("TAGNAME in $inout _registerArticle is $simp_coll");
@@ -1431,10 +1430,10 @@
<contactEmail>your at email.address</contactEmail>
<URL>http://endpoint.of.service</URL>
<Input>
- <!-- one or more Simple and/or Complex Primary articles -->
+ <!-- one or more Simple and/or Collection Primary articles -->
</Input>
<Output>
- <!-- one or more Simple and/or Complex Primary articles -->
+ <!-- one or more Simple and/or Collection Primary articles -->
</Output>
<secondaryArticles>
<!-- one or more Secondary articles -->
More information about the MOBY-guts
mailing list