gov.nasa.jpl.imce.ontologies.public
gov.nasa.jpl.imce.ontologies.public copied to clipboard
JPL-IMCE
JPL's IMCE ontologies for Model-Based Systems Engineering
The OML Converter reports an error for http://imce.jpl.nasa.gov/discipline/electrical/electrical Basically this ontology has an incomplete backbone, it is missing: ``` Declaration( ObjectProperty( electrical-backbone:topReifiedObjectProperty )) SubObjectPropertyOf( electrical-backbone:topReifiedObjectProperty, electrical-backbone:topObjectProperty ) SubObjectPropertyOf( electrical:provides, electrical-backbone:topReifiedObjectProperty)...
A named SWRL implication rule corresponds to an OML ChainRule. In OML, a ChainRule has an IRI, which is, the IRI of the OML TerminologyBox with the OML ChainRule label...
This ontology needs to be updated to the current ReifiedObjectProperty pattern. It is missing: - `state-analysis-functional-design-backbone:topReifiedObjectProperty` - Using SWRL rules instead of SubPropertyChainOf
Currently, the ontology has: ``` true ``` But it needs instead: ``` true ```
I have been looking at the ‘project’ ontology (http://imce.jpl.nasa.gov/foundation/project/project), and I am having trouble with the following construct: When I load this in protégé, I see the following image: I...
The name of the catalog file, 'imce.local.catalog.xml', was chosen a long time ago and kept as-is. The current OML tooling requires the catalog to be named 'oml.catalog.xml'. Whereas previously this...
`mission:Involves1` and `mission:Involves2` specialize `mission:Involves`. Unless I missed something, I don't see any ontologically significant difference among them. This is a violation of a pattern we've strived for in these...
Without this, we can't say that a mission:Component base:aggregates mission:Component.
According to R. Karban, NoMagic reported that MagicDraw has a lot of problems with using `UML::Component` stereotyped by `SysML::Block`; that is, `SysML-metamodel#Component.Block` This was fixed for the embedding of `mission:Component`,...