9. The OpenMICompliancyInfo file

OpenMI compliant components must be associated with an OpenMI compliance info file. This file provides useful information for people that are planning to use the component in an OpenMI configuration. The OpenMI compliance info file must comply to the schema OpenMICompliancyInfo.xsd ((http://www.openmi.org/schemas/OpenMICompliancyInfo.xsd)).

You can see other examples of OpenMI compliancy info files here.

The openmi compliance xml file for the Simple River is shown below:

<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2006 rel. 3 sp1 (http://www.altova.com)-->
<OpenMICompliancyInfo xmlns="http://www.openmi.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openmi.org ..\..\..\..\..\..\OpenMI.Standard\src\OpenMICompliancyInfo.xsd">
	<generalSoftwareInfo>
		<component name="SimpleRiver" version="1.4.0.0">
			<description>Fortran wrapping sample</description>
			<url>public.wldelft.nl/display/OPENMI/Oatc.OpenMI.Examples.ModelComponents.SimpleRiver</url>
		</component>
		<contactInfo>
			<supplierName>OATC (OpenMI Association Technical Committee)</supplierName>
			<contactPerson>Jan Borge Gregersen</contactPerson>
			<supplierEmail>association@openmi.org</supplierEmail>
		</contactInfo>
		<availability component="free" source="available">
			<comment>Available as part of OATC Software Development Kit</comment>
		</availability>
	</generalSoftwareInfo>
	<supportForOpenMI>
		<compliancy>
			<technology>dotNet</technology>
			<openMIStandardVersion>1.4.0.0</openMIStandardVersion>
		</compliancy>
		<exchangeItems>
			<dataOperations setId="spatial/time/buffering">
				<dataOperation>Nearest XYPolyLine to XYPoint</dataOperation>
				<dataOperation>Inverse XYPolyLine to XYPoint</dataOperation>
				<dataOperation>Weighted Mean XYPolyLine to XYPolyGon</dataOperation>
				<dataOperation>Weighted Sum XYPolyLine to XYPolyGon</dataOperation>
				<dataOperation>LinearConversion</dataOperation>
				<dataOperation>Buffering and temporal extrapolation</dataOperation>
			</dataOperations>
			<inputExchangeItem>
				<quantity>
					<description>Flow</description>
					<dimension lenght="3" time="-1"/>
				</quantity>
				<elementSet elementType="IDBased">
					<description>An ElementSet for each branch. Each ElementSet is identified by 'branch-N', where N is the branch number.</description>
				</elementSet>
			</inputExchangeItem>
			<outputExchangeItem>
				<quantity>
					<description>Outflow</description>
					<dimension lenght="3" time="-1"/>
				</quantity>
				<elementSet elementType="XYPolyLine">
					<description>An ElementSet with one element (line segment) for each branch, or an ElementSet with an element for each branch.</description>
				</elementSet>
				<dataOperations>spatial/time/buffering</dataOperations>
			</outputExchangeItem>
			<outputExchangeItem>
				<quantity>
					<description>Outflow</description>
					<dimension lenght="3" time="-1"/>
				</quantity>
				<elementSet elementType="XYPolyLine">
					<description>An ElementSet with one element (line segment) for each branch, or an ElementSet with an element for each branch.</description>
				</elementSet>
				<dataOperation>LinearConversion</dataOperation>
				<dataOperation>Buffering and temporal extrapolation</dataOperation>
			</outputExchangeItem>
			<inputExchangeItem>
				<quantity>
					<description>Flow</description>
					<dimension lenght="3" time="-1"/>
				</quantity>
				<elementSet elementType="XYPolyLine">
					<description>An ElementSet with one element (line segment) for each branch, or an ElementSet with an element for each branch.</description>
				</elementSet>
			</inputExchangeItem>
		</exchangeItems>
		<optionalInterfaces>
			<IManageState isSupported="false">
				<comment>Not implemented for this simple river example</comment>
			</IManageState>
			<IDiscreteTimes isSupported="false"/>
		</optionalInterfaces>
	</supportForOpenMI>
</OpenMICompliancyInfo>
  • No labels

Disclaimer