Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Develop fully compliant XMI 2.5.1 lexical scope mapping component for the Quicksilver engine. #2

Open
binaryflesh opened this issue Dec 2, 2018 · 3 comments
Open

Develop fully compliant XMI 2.5.1 lexical scope mapping component for the Quicksilver engine. #2

binaryflesh opened this issue Dec 2, 2018 · 3 comments
Assignees
@binaryflesh
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone
engine

Comments

@binaryflesh
Copy link
Collaborator

xmiparser1-5 looks abandoned and not as extensible as I'd like it to be. It needs to take account for vanilla OMG specifications and have ability to modify/extend beyond that specification to be a genuine 'agnostic' and reliable tool.
link to current development effort.
Will eventually be a submodule.
@binaryflesh binaryflesh added enhancement New feature or request good first issue Good for newcomers labels Dec 2, 2018
@binaryflesh binaryflesh self-assigned this Dec 2, 2018
@binaryflesh
Copy link
Collaborator Author

EDIT: Project repository is located at https://github.com/binaryflesh/pyxmiparser .

@binaryflesh binaryflesh changed the title Create fully compliant XMI 2.5.1 parser/lexical scope mapper Create fully compliant XMI 2.5.1 parser/lexical scope mapping tool Dec 2, 2018
@binaryflesh binaryflesh changed the title Create fully compliant XMI 2.5.1 parser/lexical scope mapping tool Create fully compliant XMI 2.5.1 lexical scope mapping tool Dec 3, 2018
@binaryflesh
Copy link
Collaborator Author

After digging through both the normative and informative documentation, I am deciding on making all parts of this in python. This will set quicksilver in stone to stick with UML 2.5.1, which will work for my use case.

@binaryflesh
Copy link
Collaborator Author

EDIT: Renamed repository to reflect now being a library. https://github.com/binaryflesh/xmilib

@binaryflesh binaryflesh added this to the engine milestone Dec 3, 2018
@binaryflesh binaryflesh changed the title Create fully compliant XMI 2.5.1 lexical scope mapping tool Create fully compliant XMI 2.5.1 lexical scope mapping component Dec 3, 2018
@binaryflesh binaryflesh changed the title Create fully compliant XMI 2.5.1 lexical scope mapping component Develop fully compliant XMI 2.5.1 lexical scope mapping component for the Quicksilver engine Dec 3, 2018
@binaryflesh binaryflesh changed the title Develop fully compliant XMI 2.5.1 lexical scope mapping component for the Quicksilver engine Develop fully compliant XMI 2.5.1 lexical scope mapping component for the Quicksilver engine. Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@binaryflesh binaryflesh

Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
engine
Development

No branches or pull requests
1 participant
@binaryflesh