You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ossie.apache.org by jb...@apache.org on 2026/09/06 16:24:44 UTC
(ossie) branch main updated: [Doc] Fix typo (#362)
This is an automated email from the ASF dual-hosted git repository.
jbonofre pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/ossie.git
The following commit(s) were added to refs/heads/main by this push:
new 146d2745 [Doc] Fix typo (#362)
146d2745 is described below
commit 146d2745c7dd3e434a7a83bc4e8881cc9a2154d1
Author: Yong Zheng <yo...@gmail.com>
AuthorDate: Sun Sep 6 11:24:38 2026 -0500
[Doc] Fix typo (#362)
* Fix typo
* Fix typo
---
core-spec/expression_language.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/core-spec/expression_language.md b/core-spec/expression_language.md
index db6b966b..38f5e1a7 100644
--- a/core-spec/expression_language.md
+++ b/core-spec/expression_language.md
@@ -36,7 +36,7 @@ There are two layers in Ossie that need an expression language:
* **Ontology layer.** This layer maps onto the ontology layer which sits above the logical layer. It maps more closely to modelling languages like OWL, [(Py)Rel](https://docs.relational.ai) from RelationalAI, and [Legend](https://legend.finos.org) from Goldman Sachs
* **Logical layer.** This layer maps directly to the databases and physical layer. It maps closely to traditional BI semantic models.
-This proposal is only targeted at the Logical Layer. It would be nice if the Ontological layer could re-use the same expression language, but that will be treated as a separate proposal.
+This proposal is only targeted at the Logical Layer. It would be nice if the Ontological layer could reuse the same expression language, but that will be treated as a separate proposal.
This document defines the SQL expression language subset that Ossie-compliant implementations MUST support. The goal is to provide a portable expression language that works across all Ossie implementations while allowing vendors to expose richer database-specific functionality through dialect extensions. In particular, it is meant for expressions at the logical layer. This means metrics, fields, filters, etc In the future, expressions such as arbitrary join expressions should also use [...]
@@ -80,7 +80,7 @@ The quote character for the Ossie dialect will follow ANSI SQL and support the d
#### Comparison Table
-| You type this in SQL | Equivalen to | Will it match a column created as id? |
+| You type this in SQL | Equivalent to | Will it match a column created as id? |
| :---- |:-------------|:--------------------------------------------------|
| id | ID | **Yes** (Standard behavior) |
| Id | ID | **Yes** (Standard behavior) |