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

FPWD Feedback by Sebastian #45

Closed
sebastiankb opened this issue Oct 7, 2020 · 2 comments
Closed

FPWD Feedback by Sebastian #45

sebastiankb opened this issue Oct 7, 2020 · 2 comments
Assignees
@mlagally
Labels
FPWD Feedback feedback on FPWD-ready documents

Comments

@sebastiankb
Copy link
Contributor

In the current draft, I miss some editorial notes about unclearified discussions in the group such as about the "name" Core Profile and its impact (also see #21 and #25).

In general, I miss some explanation about Figure 1 & 2 otherwise there will be misunderstanding about the profile concept such as that the "core" have to be always present in other possible profiles. I think this is not desired when I think about constrained profiles etc.
@sebastiankb sebastiankb added the FPWD Feedback feedback on FPWD-ready documents label Oct 7, 2020
@sebastiankb
Copy link
Contributor Author

@mlagally I can provide a PR about this today

mlagally added a commit that referenced this issue Oct 7, 2020
@mlagally
Issue #45: editors note about name Core Profile
c2ef0d7
mlagally added a commit that referenced this issue Oct 7, 2020
@mlagally
Issue #45: clarifying figure
d5e6f7f
@mlagally
Copy link
Contributor

@sebastiankb
We have added editor's notes that should be addressing your comments.

Cany you please check/confirm that your comments are addressed?

@mlagally mlagally changed the title FPWD Feedback FPWD Feedback by Sebastian Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mlagally mlagally

Labels
FPWD Feedback feedback on FPWD-ready documents
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sebastiankb @mlagally