processcomponent.java

开发owl的API,提供了W3C规定标准接口,是目前比较少的API.

// The MIT License
//
// Copyright (c) 2004 Evren Sirin
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to
// deal in the Software without restriction, including without limitation the
// rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
// sell copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in
// all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
// FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
// IN THE SOFTWARE.

/*
 * Created on Dec 27, 2003
 *
 */
package org.mindswap.owls.process;

import org.mindswap.owl.OWLResource;

/**
 * Represents the OWL-S process component. This is the top level element in the process hierarchy
 * that is the superclass for {@link org.mindswap.owls.process.Process Process} and
 * {@link org.mindswap.owls.process.ControlConstruct ControlConstruct} classes 
 *   
 * 
 * OWL-S concept: http://www.daml.org/services/owl-s/1.0/Process.owl#ProcessComponent 
 * 
 * @author Evren Sirin
 *
 */
public interface ProcessComponent extends OWLResource {

	/**
	 * Get the dataflow for this process component. Data flow is given by the process:sameValues property
	 * in the process description. It is not clear what the data flow means for Atomic or Simple
	 * processes but OWL-S specification defines this property at this level so the method is defined 
	 * here. In practice, it makes more sense to use data flows only for CompositeProcess descriptions.
	 * 
	 * @return
	 */	
	public DataFlow getDataFlow();
		
	/**
	 * Check if this process component is invocable. 
	 * 
	 * @return
	 */
	public boolean isInvocable();
	
	/**
	 * Return a list of all the Process objects used (directly or indirectly) in this process 
	 * component. An AtomicProcess only uses itself. A CompositeProcess uses all the processes
	 * its ControlConstruct uses. A ControlConstruct uses all the processes used by its 
	 * components. 
	 * 
	 * @return
	 */
	public ProcessComponentList getAllProcesses();
}