-
Notifications
You must be signed in to change notification settings - Fork 29
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
Revise 13: Linking Data #92
Comments
The linking data chapter has the following inconsistencies in regard to MEI v4:
If there is no objection, I will remove the whole section on Linking and Alignment and the xlink:title in the first part of the chapter. Also do some clean up of the first part. |
Yes, |
Thanks for the clarification. So I would remove the whole LinkAlign part of the current chapter and replace it with a placeholder for Linked Data approaches. @musicog and me will have another look on it next week. |
Yes. And I must not forget to cover |
Ok, good. Another question: The attributes from One reason: There is already a description and elaboration in chapter 10 (analysis): General Relationships between Elements. I would like to link there from the Linking chapter, but have the strong feeling that in general the chapter "Analysis" is the wrong place for the explanation of |
Yes and no. At first sight, this sounds reasonable. But then again, analysis in MEI historically means more than musical analysis in the sense of Riemann, Schenker etc. If someone states that one element is a |
I think this chapter is good enough to be included, or at least most of it. For now, I would just kick out 13.3 and 13.4, and merge the rest. What do you think, @musicEnfanthen? |
I'm currently working on content for 13.3 / 13.4 -- but I appreciate this is rather late! (sorry!) |
of course – and it's great to hear you're already working on this :-) So, let's include what we have already, and take care of the rest asap… |
The "(soon)" in my previous comment is doing some heavy lifting there, sorry :-( |
Ok, good. Will remove the whole section 13.3 for now. |
👍 |
this has been fixed by #168 |
This issue can be used to discuss chapter 13 of the guidelines.
The text was updated successfully, but these errors were encountered: