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/07/14 04:33:42 UTC
(ossie) branch main updated: chore: trim trailing whitespace (#181)
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 5260080 chore: trim trailing whitespace (#181)
5260080 is described below
commit 52600802065fadd4b6565b525bc25c9a6d3609f5
Author: Emil Sadek <es...@hotmail.com>
AuthorDate: Mon Jul 13 21:33:38 2026 -0700
chore: trim trailing whitespace (#181)
Co-authored-by: Emil Sadek <es...@users.noreply.github.com>
---
.asf.yaml | 2 +-
CONTRIBUTING.md | 2 +-
converters/salesforce/src/main/resources/mappings.yaml | 2 +-
core-spec/spec.md | 10 +++++-----
core-spec/spec.yaml | 12 ++++++------
ontology/ontology.json | 4 ++--
ontology/ontology.md | 10 +++++-----
7 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 462fcf8..acad1eb 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -16,7 +16,7 @@
# specific language governing permissions and limitations
# under the License.
#
-
+
# The format of this file is documented at
# https://github.com/apache/infrastructure-asfyaml
# also at
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9307ff3..15bf5b9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -59,7 +59,7 @@ it didn't happen.*
[archives](https://lists.apache.org/list.html?dev@ossie.apache.org).
- **commits@ossie.apache.org** — automated notifications for commits, pull requests.
Subscribe via `commits-subscribe@ossie.apache.org`.
-- **issues@ossie.apache.org** — automated notifications for issues.
+- **issues@ossie.apache.org** — automated notifications for issues.
Subscribe via `issues-subscribe@ossie.apache.org`.
- **private@ossie.apache.org** — the Podling Project Management Committee (PPMC)
private list, used only for confidential matters such as committer nominations.
diff --git a/converters/salesforce/src/main/resources/mappings.yaml b/converters/salesforce/src/main/resources/mappings.yaml
index 57552cf..15f70cb 100644
--- a/converters/salesforce/src/main/resources/mappings.yaml
+++ b/converters/salesforce/src/main/resources/mappings.yaml
@@ -19,7 +19,7 @@
# Ossie-Salesforce Converter - Mapping Configuration
# =============================================================================
#
-# This file defines ONLY straightforward property mappings between Ossie YAML
+# This file defines ONLY straightforward property mappings between Ossie YAML
# format and Salesforce Semantic Model JSON format.
#
# Complex mappings (arrays, routing, transformations) are handled programmatically
diff --git a/core-spec/spec.md b/core-spec/spec.md
index 918ee8d..8b9c10a 100644
--- a/core-spec/spec.md
+++ b/core-spec/spec.md
@@ -252,7 +252,7 @@ expression:
- dialect: ANSI_SQL
expression: customer_id
description: Customer identifier
- dimension:
+ dimension:
is_time: false
```
@@ -463,14 +463,14 @@ semantic_model:
- dialect: ANSI_SQL
expression: order_id
description: Order identifier
-
+
- name: customer_id
expression:
dialects:
- dialect: ANSI_SQL
expression: customer_id
description: Customer identifier
-
+
- name: order_date
expression:
dialects:
@@ -479,7 +479,7 @@ semantic_model:
dimension:
is_time: true
description: Order date
-
+
- name: amount
expression:
dialects:
@@ -498,7 +498,7 @@ semantic_model:
- dialect: ANSI_SQL
expression: id
description: Customer identifier
-
+
- name: email
expression:
dialects:
diff --git a/core-spec/spec.yaml b/core-spec/spec.yaml
index c108690..a5617e8 100644
--- a/core-spec/spec.yaml
+++ b/core-spec/spec.yaml
@@ -18,7 +18,7 @@
# Apache Ossie - Core Metadata Spec (YAML Schema)
# DRAFT version - in development, schema may change before 0.2.0 is released
version: 0.2.0.dev0
-#
+#
# Goals:
# - Standardization: Establish uniform language and structure for semantic model definitions
# - Extensibility: Support domain-specific extensions while maintaining core compatibility
@@ -44,7 +44,7 @@ dialects:
# Examples: "COMMON", "SNOWFLAKE", "SALESFORCE", "DBT", "DATABRICKS", "GOODDATA"
vendor_name: string
-
+
# Top-level semantic model definition
semantic_model:
# Required: Unique identifier for the semantic model
@@ -64,7 +64,7 @@ semantic_model:
# See Relationships section below for detailed structure
relationships: []
- # Optional:
+ # Optional:
# These metrics can span one or more logical datasets and use relationships
# See Metrics section below for detailed structure
metrics: []
@@ -86,7 +86,7 @@ datasets:
# Required: Reference to the underlying physical table/view or query
# Format should be either database_name.schema_name.table_name or query
source: string
-
+
# Optional: Primary key definition that uniquely identifies rows in this dataset
# Can be a single column or a composite of multiple columns
# This is the preferred unique identifier for this dataset and is used in relationships to determine many-to-one or one-to-one.
@@ -107,8 +107,8 @@ datasets:
# - [column2, column3]
#
# unique_keys:
- # - [column1, column2]
- # - [column3, column4]
+ # - [column1, column2]
+ # - [column3, column4]
unique_keys:
- [] # Array of column names (single or composite)
diff --git a/ontology/ontology.json b/ontology/ontology.json
index 72dcb34..943f6aa 100644
--- a/ontology/ontology.json
+++ b/ontology/ontology.json
@@ -58,7 +58,7 @@
"concept": {
"$ref": "#/$defs/Concept"
},
- "relationships": {
+ "relationships": {
"type": "array",
"items": {
"$ref": "#/$defs/Relationship"
@@ -181,7 +181,7 @@
"$ref": "#/$defs/ObjectMapping"
},
"description": "Mappings from logical constructs that populate the concept in this component. Valid only when the concept is an entity type"
- },
+ },
"link_mappings": {
"type": "array",
"items": {
diff --git a/ontology/ontology.md b/ontology/ontology.md
index 05ad614..3e9593f 100644
--- a/ontology/ontology.md
+++ b/ontology/ontology.md
@@ -101,7 +101,7 @@ concept plays the first role:
Concepts represent the types of things that have meaning in a business setting, e.g., person, company,
or salary. Every ontology implicitly includes all of the [built-in concepts](#built-in-concepts) and
-may refer to them by name without declaring them.
+may refer to them by name without declaring them.
Concepts have the following schema:
@@ -187,7 +187,7 @@ ontology:
the relationship is identified by the string `Person.earns`. This convention naturally supports
expressions that navigate over the links of relationships using the “dot-join” operator in a
manner that is familiar to object-oriented programming languages. This relationship links
-`Person` and `Salary` objects and verbalizes each link as “Person earns Salary.”
+`Person` and `Salary` objects and verbalizes each link as “Person earns Salary.”
#### Roles
@@ -285,7 +285,7 @@ idnetifier of a concept.
### Derivation expressions
-Concepts and relationships may be derived using expressions. Think of a derived concept or
+Concepts and relationships may be derived using expressions. Think of a derived concept or
relationship as a view whose objects or links are derived from those of other concepts or
relationships. For instance:
@@ -306,7 +306,7 @@ ontology:
name: "descendant"
derived_by:
- "Person.parent_of(descendant)"
- "Person.ancestor_of.parent_of(descendant)"
+ "Person.ancestor_of.parent_of(descendant)"
- name: taxed_at
roles:
- concept: TaxRate
@@ -458,7 +458,7 @@ then mapping those values to `Person` objects using the declared identifier. The
concept_mappings:
- concept: Person
object_mappings:
- - expression: PERSONS.SSN
+ - expression: PERSONS.SSN
...
```
maps values from the `SSN` field of dataset `PERSONS` into `Person` objects.