pe-ro

Results 33 issues of pe-ro

Currently, MEI can deal with a page header and footer on the first page, and on the following pages. However, sometimes a page footer on the last page is unique;...

Component: Core Schema
Priority: Low
Type: Feature Request
Status: Needs Discussion

To avoid duplicate attribute definitions, att.tuplet.vis is referenced by att.tupletSpan.vis. Fixes #1195

Component: Guidelines & Documentation
Component: Core Schema
Status: Needs Work

Component: Core Schema
Status: Ready To Merge

Allow `` in `` to accommodate textual descriptions, rather than bibliographic references or descriptions.

Component: Guidelines & Documentation
Component: Core Schema
Type: Feature Request
Status: Needs Work

Currently to point from metadata elements to elements elsewhere in the file that they apply to, one must use the `@data` attribute. I propose adding a `@select` attribute, also in...

Component: Core Schema
Priority: Low
Status: Needs Work

[@bwbohl EDIT] This PR relaxes the content model of the mentioned FRBR elements by removing the predefined order of their child elements. Doing so it accommodates broader use in different...

Component: Core Schema

Use of `@usage="rec"` and display of the attribute's status in the Data Dictionary will help clarify when an attribute is recommended. Since "rec" results in an optional attribute in RNG...

Component: Guidelines & Documentation
Component: Core Schema
Priority: Medium
Type: Feature Request
Status: Needs Discussion

This PR adds a new specialized `` element based on the more generic `` element. Fixes #845

Component: Core Schema

Currently MEI has no element for marking geographic coordinates. These could be useful for creating visualizations representing places of composition, birth, death, etc. So, I propose adding a `` element...

Type: Feature Request

Currently one can use ```xml 1525 1594 ``` to encode a date range starting in 1525 and ending in 1594. But, the same markup could also represent a choice between...

Type: Feature Request