AccessServlet

This servlet handles schema accesses. It takes the following parameters, either from a GET or POST request:

• access method which should be just get to obtain the detail of a schema that includes its metadata and the schema file. This method also requires a common parameter object .

• get is followed by
  • identifier dictionary registry's identifier.
  • registryId registry identifier, a sequence number assigned after a successful registration.

In response, this servlet dispatches to a jsp page that displays the result from the access.

Examples:

http://metadata.jpl.nasa.gov/SchemaAccess?
object=urn:eda:corba:JPL.EDM.MetadataRegistry&
identifier=MDR.Dictionary.DTD&
get
	

ManagerServlet

This servlet provides methods that handle and manage schema registries.

Some methods involve too many input parameters for filling in the metadata information. The URL for HTTP interface can be very long. Therefore, it is better for the users to set up a html form page to feed the schema file and its metadata for processing. Please refer to jsp source http://metadata.jpl.nasa.gov/newSchema.jsp as an example to reserve a schema namespace or http://metadata.jpl.nasa. gov/registerSchema.jsp to register a schema file. These include create, add, and modify methods.

In response, this servlet dispatches to a jsp page that displays the registry status.

For validate method, because the input involves sending the schema file to the server via the HTTP interface, the user needs to set up a html form page to feed the file content. Please refer to jsp source http://metata.jpl.nasa.gov/validateSchema.jsp for sample code.

In response, this servlet dispatches to a jsp page, schemaValidateResult.jsp , that displays the registry status.

For other methods, the inputs are simpler. These include remove, removeAll, and release methods. All methods require a common parameter, object .

• remove method is followed by
  • identifier schema registry's identifier.
  • registryId registry identifier, a sequence number assigned after a successful registration.
• removeAll method is followed by
  • identifier schema registry's identifier.
• release method is followed by
  • identifier schema registry's identifier.
  • registryId registry identifier, a sequence number assigned after a successful registration.

In response, this servlet dispatches to a jsp page, schemaRegistryResult.jsp that displays the registry status.

SearchServlet

This servlet handles schema registries search. It takes the following parameters, eithe r from a GET or POST request:

• search methods which should be either browse , textSearch , keywordSearch , or xmlQuery indicating what kind of search to perform. All these methods require a common parameter object .

Then, depending on the option selected above, other parameters must be specified.

• browse : no parameter is further needed.
• textSearch is followed by:
  • textString is a string of characters.
• keywordSearch is followed by a set of keyword=value . The user will need to obtain a list of the attributes describing a dictionary. These attributes are derived from the Dublin Core standard.
  • keyword is an attribute describing dictionary.
  • value is value to keyword given above.
• xmlQuery is followed by
  • DIS-style query string is a query using triples linked in a logical expression. Each triple is in the format of (element, relation, literal).

In response, this servlet dispatches to a jsp page that displays the html result from the search except for xmlQuery method which displays profile xml structure compliant to http://oodt.jpl.nasa.gov/dtd/profile.dtd .

Examples:

http://metadata.jpl.nasa.gov/SchemaSearch?
object=urn:eda:corba:JPL.EDM.MetadataRegistry&
browse
	  

http://metadata.jpl.nasa.gov/SchemaSearch?
object=urn:eda:corba:JPL.EDM.MetadataRegistry&
textString=Dictionary&
textSearch
	  

http://metadata.jpl.nasa.gov/SchemaSearch?
object=urn:eda:corba:JPL.EDM.MetadataRegistry&
DC.Identifier=MDR.Dictionary.DTD&
keywordSearch
	  

http://metadata.jpl.nasa.gov/SchemaSearch?
object=urn:eda:corba:JPL.EDM.MetadataRegistry&
kwdString=Identifier=MDR.Dictionary.XMLSchema&
xmlQuery=Profiles