EagleUmlCommon
EagleUmlCommon copied to clipboard
Project EAGLE: Open Source Repository for Open Model, Profile and Tools
Issue statement: _The condition for a Pac is already specified in the stereotype. Do we still need the constraints and shown in the UML diagram?_ Reference: See Figure 7.5 in...
Issue statements: (1) Guidelines for using the **Deprecated** lifecycle stereotype: When deprecating an object class, do we need to also explicitly deprecate the attributes of the deprecated object class? (2)...
Similar to https://github.com/ict-strauss/COP/issues/2 This issue still exists with pyang verion 1.7
Some model compatibility ideas that can be added to a white paper. [Model compatibility.pptx](https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/files/1969997/Model.compatibility.pptx)
This issue is dealing with the «Specify» abstraction (i.e, not inheritance, «StrictComposite» or «ExtendedComposite») and supports the federation of models. A clear definition of the «Specify» abstraction is missing; like:...
Related: https://github.com/OpenNetworkingFoundation/Snowmass-ONFOpenTransport/issues/163 Alignment with RFC restconf will be needed: a) for configuration and state data: /restconf/data/… and not /restconf/config/… b) access to lists by key should look like: …/_topology=top0 and...
## How I'd like the translation to be like When I define a list within a container, such as: ```yang container virtualizers { description "Container with multiple virtualizers"; list virtualizer...
Type uint64 in yang was mapped to string in JSON.
Hi there, I just picked up the latest swagger.py and tried to generated a swagger json from my YANG module which references other YANG modules. What I noticed was the...
When I try to generate JSON file from Tapi yang file, pyang -swagger tool reports the following errors: > pyang -f swagger -o D:/YANG0329/tapi-topology.json D:/YANG0329/TapiTopology.yang > D:/YANG0329/TapiTopology.yang:4: error: module "Tapi"...