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.

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

L1v4: need to implement change: SedLine / SedMarker attribute names were renamed from 'style' to 'type' #96

Closed
luciansmith opened this issue Mar 17, 2021 · 5 comments

Comments

@luciansmith
Copy link
Collaborator

luciansmith commented Mar 17, 2021

Libsedml thinks that the types of a line and a marker are set in the attribute 'style', but should be 'type'.

@luciansmith luciansmith changed the title L1v4: Line type is 'type' not 'style' L1v4: Line and marker types are 'type' not 'style' Mar 17, 2021
@fbergmann
Copy link
Owner

This was a recent change in the last draft, before it was just 'marker', 'line' and such, which caused conflicts and inconsistencies (#67). The sed-ml generated should be fine though. Do you need this to change urgently? This would break the opencor implementation, right @agarny ?

fbergmann added a commit that referenced this issue Mar 19, 2021
@luciansmith
Copy link
Collaborator Author

No, it affects the SED-ML. libsedml produces:

<line style="dashDot" color="#FF00FF" thickness="4"/>

when it should produce:

<line type="dashDot" color="#FF00FF" thickness="4"/>

I dunno how urgent this is; it creates incorrect/invalid SED-ML, but it still demonstrates proof of concept.

@fbergmann fbergmann changed the title L1v4: Line and marker types are 'type' not 'style' L1v4: need to implement change: SedLine / SedMarker attribute names were renamed from 'style' to 'type' Mar 19, 2021
@fbergmann
Copy link
Owner

yup that needs doing

@agarny
Copy link
Contributor

agarny commented Mar 19, 2021

This was a recent change in the last draft, before it was just 'marker', 'line' and such, which caused conflicts and inconsistencies (#67). The sed-ml generated should be fine though. Do you need this to change urgently? This would break the opencor implementation, right @agarny ?

When it comes to L1V4, it's still in a special branch of OpenCOR. So, we can change whatever we need to change, this won't break the current version of OpenCOR (which uses annotations for lines, markers, etc.).

luciansmith added a commit that referenced this issue Apr 2, 2021
Mostly accomplished using emacs search/replace which preserves case.
@fbergmann
Copy link
Owner

this is now in the release 2.0.18, i hope it works for all. thanks @luciansmith

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants