core-spec `relationships` have no cardinality field

Abierto
#694 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
data

Línea de trabajo

Start with spec.md relationships, then compare their current fields with the ontology layer's Multiplicity and the relational semantics in #246. Decide how cardinality should be declared on each side and how disagreement with inferred cardinality becomes a typed error. Done means the core-spec representation and rule are defined, including whether to reuse Multiplicity or use to_one | to_many.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs-triage

spec.md relationships carry from, to, from_columns, to_columns, and nothing that declares whether the relationship is to-one or to-many. The ontology layer has multiplicity (ManyToOne, OneToOne); the core model has no equivalent, so a model that never reaches Layer 4 cannot say "a customer has many sales areas; each sales area belongs to one customer" except as prose.

Sources like SAP CSN always declare cardinality on associations (cardinality: { max: '*' }, managed to-one), and never infer it. Two consequences today: a CSN → core-spec converter must drop it (apache/ossie-converters#54 keeps it in the SAP_CSN extension, which is the right workaround and also the symptom); and the portability ladder cannot grade it, because there is nothing in the document to grade.

#246's relational semantics infer join cardinality from keys (unique_keys, §6.4), which covers evaluation but not declaration. Request: an optional declared cardinality on core-spec relationships — minimum to_one | to_many per side, or the ontology layer's Multiplicity reused — and a rule that declared-vs-inferred disagreement is a typed error, not silent trust of either side. Raised earlier in Discussion #50 from the ontology side; this is the core-spec half.

Lenguaje dominante
Python
Estrellas
2.7k
Forks
353
Merge medio
3 d 19 h
PR fusionados (30 d)
86

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/ossie

Todos los issues de apache/ossie

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.