Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

API JSON: `verify`, flow ends, message ends and a transition's `then` use other metaclasses than the grammar

Cerrado
  • ¿Algo no está bien?
#651 0 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
api, backend-api-design

Línea de trabajo

Start with the sysml -convert api-json <file> entry point and reproduce the four examples with sysml -validate; compare each exported metaclass with the grammar references in the issue. Read rdf-mapping.md:1548 for the existing verify mapping, then verify that the API output matches the listed grammar constructs for verification, flow ends, message events and transition succession.

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

Descripción

sysml -convert api-json <file> on develop (72081f8). Each file below validates cleanly in sysml -validate and in SysIDE 0.10.3.

Source Exported Grammar (SysML-textual-bnf)
verification def T { objective { verify r; } } FeatureMembership owning a SatisfyRequirementUsage (sysx:declaredKeyword "verify") RequirementVerificationMembership owning a RequirementUsage (:1551-1557)
flow of Fuel from a.p.fuel to b.p.fuel; each end a ReferenceUsage with isEnd EndFeatureMembership owning a FlowEnd (:864-869)
message m from a to b; each end a ReferenceUsage under an EndFeatureMembership ParameterMembership owning an EventOccurrenceUsage (:823-827)
transition t first a then b; TransitionUsage with source/target set; it owns no Succession OwningMembership owning a Succession (TransitionSuccessionMember, :1340-1344)

The examples, one file each:

package V {
    requirement r;
    verification def T { objective { verify r; } }
}

package F {
    item def Fuel;
    port def P { out item fuel : Fuel; }
    part a { port p : P; }
    part b { port p : ~P; }
    flow of Fuel from a.p.fuel to b.p.fuel;
}

package M {
    part a;
    part b;
    occurrence def Talk { message m from a to b; }
}

package T {
    state def S {
        state a;
        state b;
        transition t first a then b;
    }
}

Why it matters for a consumer of the API form: a verify is read as a satisfaction, which a verification report must keep apart, and code that finds flow ends, message events or a transition's succession by metaclass finds none.

rdf-mapping.md:1548 calls verify a synonym of satisfy. In a requirement body the grammar gives it its own membership (:1551), so it isn't one there.

Lenguaje dominante
Go
Estrellas
39
Forks
12
Merge medio
16 h 37 min
PR fusionados (30 d)
770

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 Open-MBEE/OpenSysML

Todos los issues de Open-MBEE/OpenSysML

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.