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

ImageFrameWidthList and ImageFrameHeightList #33

Open
MarcAntoine-Arnaud opened this issue Aug 6, 2019 · 0 comments
Open

ImageFrameWidthList and ImageFrameHeightList #33

MarcAntoine-Arnaud opened this issue Aug 6, 2019 · 0 comments

Comments

@MarcAntoine-Arnaud
Copy link
Contributor

It's not safe to define 2 lists for resolutions.
As for example with the TSP 2121-1, the PDF document mention 2 resolutions:
1920x1080 and 3480x2160.

If we fill a Delivery Schema with these values, its possible to delivers files with these resolutions:
1920x1080
1920x2160
3480x2160
3480x1080

Why the model was not defined as:

ImageFrameList [
  {
    width
    height
  }
]
@thedpp
Copy link

thedpp commented Aug 6, 2019

In App2e this would be perfectly acceptable. My view is that it is up to the Delivery Schema instance to prevent this. Which is exactly where tool providers such as yourself come in.

All, I am currently designing a decision tree for TSP 2121 for Marc-Antoine to implement in his tool. I am using a flowchart drawn as SVG, which strikes me as not particularly clever ;-)
Is there a common language for defining decision trees that you know of? UML might work (can several branches merge back into on in UML?) and of course Netlist would work (you can take the engineer out of an electronics lab, but you can't take the electronics...)
Any suggestions welcome!

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

2 participants