search

JPL-IMCE / gov.nasa.jpl.imce.oml

Ontology Modeling Language (OML) Workbench
14 stars 1 forks source link

OMLSpecificationTables.read functions problems w/ optional characteristics. #247

Closed NicolasRouquette closed 6 years ago

NicolasRouquette commented 6 years ago

Example:

OML NumericScalarRestriction:

{"uuid":"03bf5003-ddbd-5843-99fc-08a410111025",
 "tboxUUID":"c108fbcf-4357-57cd-a8c0-8799e467e87f",
 "restrictedRangeUUID":"7e6679ef-7ac5-5e61-a2d6-3950a7df92ee",
 "minExclusive":null,
 "minInclusive":null,
 "maxExclusive":null,
 "maxInclusive":{"literalType":"LiteralPositiveIntegerType","value":"0"},
 "name":"nonPositiveInteger"}

The logic for reading this information in OMLSpecificationTables doesn't handle the possibility of nullable fields like minExclusive above.