[kepler-dev] confused about the MOML file

[Matthew Jones]

The ptolemy DTD and documentation for MoML is a good place to start, but 
note that we have added features to accommodate semantic annotation in 
the Kepler release that are not documented in Ptolemy.  You'll need to 
accommodate those changes when creating your MoML.  Kepler creates MoML 
for you when you create a new composite actor or specialize an atomic 
actor and save it in the library. So the easiest way to create the MoML 
for this is to create a new composite on the canvas, add the ports, then 
select 'Export as KAR' from the context menu.  The generated MoML will 
be in the KAR file. Is there a reason you need to modify the MoML directly?

Chad Berkley is the most knowledgeable about this system, but is on 
leave until Thursday.  If you're still having issues then he might be 
able to help.

Matt

Christopher Brooks wrote:
> Have you seen the MoML documentation for Ptolemy that is in the
> Ptolemy Design doc?
> http://ptolemy.eecs.berkeley.edu/papers/05/ptIIdesign1-intro/ptIIdesign1-intro.pdf
> It does not include the Kepler LSID work, but it might give you a
> better sense of the details.
> Also, you might look at other MoML files and see how they do it.
> 
> --------
> 
>     I am trying to create a KAR for an actor, but can't seem to make my output
>     port visible.  I wish to have an input port and an output port.  I can't
>     seem to find any documentation on the exact specifics of how the MOML file
>     is to be setup (the XML descriptor of the actor).  Here's my XML file
>     below:
>     
>     <?xml version="1.0"?>
>     <entity name="VorbLogger" class="ptolemy.kernel.ComponentEntity">
>     	<property name="entityId"
>     value="urn:lsid:kepler-project.org:actor:2000:1"
>     class="org.kepler.moml.NamedObjId" />
>     	<property name="class" value="org.ROADnet.Vorb.VorbLogger"
>     class="ptolemy.kernel.util.StringAttribute">
>     		<property name="id" value="urn:lsid:kepler-project.org:class:20
>    00:1"
>     class="ptolemy.kernel.util.StringAttribute" />
>     	</property>
>     	<property name="filePath" class="org.kepler.moml.PortAttribute">
>     		<property name="direction" value="input"
>     class="ptolemy.kernel.util.StringAttribute" />
>     		<property name="dataType" value="object"
>     class="ptolemy.kernel.util.StringAttribute" />
>     		<property name="isMultiport" value="false"
>     class="ptolemy.kernel.util.StringAttribute" />
>     	</property>
>     	<property name="triggerReady" class="org.kepler.moml.PortAttribute">
>     		<property name="direction" value="output"
>     class="ptolemy.kernel.util.StringAttribute" />
>     		<property name="dataType" value="object"
>     class="ptolemy.kernel.util.StringAttribute" />
>     		<property name="isMultiport" value="false"
>     class="ptolemy.kernel.util.StringAttribute" />
>     	</property>
>     	<property name="semanticType11"
>     value="urn:lsid:localhost:onto:2:1#DatabaseInputFunction"
>     class="org.kepler.sms.SemanticType" />
>     </entity>
>     
>     
>     _______________________________________________
>     Kepler-dev mailing list
>     Kepler-dev at ecoinformatics.org
>     http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
> --------
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matthew B. Jones
jones at nceas.ucsb.edu                Ph: 541-888-2581 ext. 287
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara
http://www.nceas.ucsb.edu/ecoinformatics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~