MuseData - Revision history

Craig at 00:16, 8 June 2025

2025-06-08T00:16:09Z

← Older revision		Revision as of 00:16, 8 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ~~ZZZ YYY XXX WWW VVV UUU TTT~~		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification.

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig at 00:15, 8 June 2025

2025-06-08T00:15:54Z

← Older revision		Revision as of 00:15, 8 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW VVV UUU		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW VVV UUU TTT

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig at 00:14, 8 June 2025

2025-06-08T00:14:49Z

← Older revision		Revision as of 00:14, 8 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW VVV		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW VVV UUU

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig at 23:46, 7 June 2025

2025-06-07T23:46:18Z

← Older revision		Revision as of 23:46, 7 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW VVV

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig at 23:44, 7 June 2025

2025-06-07T23:44:40Z

← Older revision		Revision as of 23:44, 7 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX WWW

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig at 23:37, 7 June 2025

2025-06-07T23:37:22Z

← Older revision		Revision as of 23:37, 7 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY XXX

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig: /* The MuseData dynamic score-generation system */

2025-06-07T23:37:08Z

The MuseData dynamic score-generation system

← Older revision		Revision as of 23:37, 7 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ YYY

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig: /* The MuseData dynamic score-generation system */

2025-06-07T23:36:59Z

The MuseData dynamic score-generation system

← Older revision		Revision as of 23:36, 7 June 2025
Line 5:		Line 5:
	<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.		<i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.

	The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification.		The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format\|MuseData]] specification. ZZZ

	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

Craig: /* MuseData Encoded Repertories */

2025-04-13T13:26:58Z

MuseData Encoded Repertories

← Older revision		Revision as of 13:26, 13 April 2025
Line 9:		Line 9:
	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

	The Center for Computer Assisted Research in the Humanities (CCARH), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format.		The Center for Computer Assisted Research in the Humanities ([[About CCARH\|CCARH]]), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format.

	===Repertory by Composer===		===Repertory by Composer===

Craig: /* MuseData Encoded Repertories */

2025-04-13T13:22:52Z

MuseData Encoded Repertories

← Older revision		Revision as of 13:22, 13 April 2025
Line 9:		Line 9:
	==MuseData Encoded Repertories==		==MuseData Encoded Repertories==

	The Center for Computer Assisted Research in the Humanities (~~[https://www.ccarh.org~~ CCARH]), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format.		The Center for Computer Assisted Research in the Humanities (CCARH), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format.

	===Repertory by Composer===		===Repertory by Composer===