API JSON: a flow's payload and a dependency's prefix metadata differ from the metamodel
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json
- Domain
- api
Research direction
Read rdf-mapping.md at lines 458-466 and 532, then compare those mappings with the corresponding entries in SysML-textual-bnf at lines 51-53, 845-852, and 1660-1662. Locate the API JSON serialization entry point and verify how flows and dependencies are represented. Done means the JSON form exposes the metamodel-aligned PayloadFeature and annotation while the documented Turtle mappings remain understood.
Written by the indexing model from the issue text.
Description
Both are documented choices in rdf-mapping.md, so this is a request, not a bug report. For the API's JSON form, could they follow the metamodel?
| Source | Exported (documented at) | Grammar (SysML-textual-bnf) |
|---|---|---|
flow of Fuel from a.p.fuel to b.p.fuel; (the flow example in #651) |
sysx:payload → a FeatureReferenceExpression under an OwningMembership (rdf-mapping.md:532) |
FeatureMembership owning a PayloadFeature (:845-852) |
#Tag dependency x to y; |
MetadataUsage under an OwningMembership of the dependency (rdf-mapping.md:458-466) |
an Annotation whose annotatingElement is the MetadataUsage (:51-53, :1660-1662) |
package A {
metadata def Tag;
part x;
part y;
#Tag dependency x to y;
}
A reader of standard API JSON finds no payload feature on the flow, and no annotation on the dependency.
:532 gives the reason for the payload: the 202407 ontology table has no payloadFeature property. The API form reads metaclasses rather than that table, so it could carry the PayloadFeature even if Turtle keeps the expression.
- Dominant language
- Go
- Stars
- 24
- Forks
- 5
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 536
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Open-MBEE/OpenSysML
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Open-MBEE/OpenSysML#608 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DataDog/dd-trace-go#5469 ·
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
l3montree-dev/devguard#3101 ·
Maintainers usually reply within 1 day
-
area:*of bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oapi-codegen/oapi-codegen#2593 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
DaoCloud/DaoCloud-docs#7432 ·
Maintainers usually reply within 1 day