From 62a29b943e56419cded5691955b60b1b589670f1 Mon Sep 17 00:00:00 2001 From: Todd Viegut Date: Fri, 9 Aug 2024 15:32:46 -0500 Subject: [PATCH] Update release-notes.md --- docs/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes.md b/docs/release-notes.md index 49b20c8..bef2ea7 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -11,7 +11,7 @@ Enhancement [Issue #108](https://github.com/cimug-org/CIMTool/issues/108): CIMTool did not yet support the new .qea and .qeax (64-bit) EA project file format introduced in the 64-bit Sparx EA 16.x releases. The new .qea and qeax file are now based on SQLite. Enhancement [Issue #114](https://github.com/cimug-org/CIMTool/issues/114): -CIMTool did not yet support the .eapx and .feap (32-bit) EA project file formats available in the 32-bit Sparx EA 15.x releases. The .feap format is an embedded Firebird database that works across both EA 15.x 32-bit and EA 16.x 64-bit release of the product. This specific type of EA project file is the only only file format that can be shared between both 32-bit Sparx EA 15.x and 64-bit EA 16.x releases. Note that this enhancements intersects the work identified in [Issue #114](https://github.com/cimug-org/CIMTool/issues/108). +CIMTool did not yet support the .eapx and .feap (32-bit) EA project file formats available in the 32-bit Sparx EA 15.x releases. The .feap format is an embedded Firebird database that works across both EA 15.x 32-bit and EA 16.x 64-bit release of the product. This specific type of EA project file is the only only file format that can be shared between both 32-bit Sparx EA 15.x and 64-bit EA 16.x releases. Note that this enhancements intersects the work identified in [Issue #108](https://github.com/cimug-org/CIMTool/issues/108). Enhancement [Issue #118](https://github.com/cimug-org/CIMTool/issues/118): This issues introduces a new builder to generate a [LinkML](https://linkml.io) representation of a CIMTool profile and is useful for a wide variety of downstream processing. The output from this builder can be leverage LinkML's core python toolchain which includes functionality like generators to convert schemas to other modeling languages and data converters and validators for working with data that conforms to LinkML (including RDF, JSON, and TSV). The following offer some useful background as to what LinkML is and how it can be leveraged: [LinkML FAQ](https://linkml.io/linkml/faq/modeling.html) and [LinkML Documentation](https://linkml.io/linkml/)