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

Possible alignment of @style and @render #5

Open
kerstarno opened this issue Feb 12, 2019 · 6 comments
Open

Possible alignment of @style and @render #5

kerstarno opened this issue Feb 12, 2019 · 6 comments
Labels
EAC-CPFAttributes These are attributes specifically used in EAC-CPF only at the moment EAD3Attributes These are attributes specifically used in EAD3 only at the moment SuggestionToMerge For suggestions to merge existing elements/attributes SuggestionToRename For suggestions to rename elements/attributes in either EAC-CPF or EAD3

Comments

@kerstarno
Copy link
Contributor

Both, EAC-CPF and EAD3, use an attributes allowing "to specify a rendering style for string" (EAC-CPF) respectively to control "the formatting of the content of an element for display and print purposes" (EAD3). However, these attributes currently go by different names: style in EAC-CPF and render in EAD3.

@kerstarno kerstarno added EAC-CPFAttributes These are attributes specifically used in EAC-CPF only at the moment EAD3Attributes These are attributes specifically used in EAD3 only at the moment SuggestionToMerge For suggestions to merge existing elements/attributes SuggestionToRename For suggestions to rename elements/attributes in either EAC-CPF or EAD3 labels Feb 12, 2019
@kerstarno
Copy link
Contributor Author

kerstarno commented Feb 19, 2019

Further conversation:

  • Needs to include altrender (seems to be available in any element of EAD3 at the moment)
  • Needs to include the elements, where these attributes are used (<span> for style, <emph>, <foreign>, <title>, and <titleproper> for render)
  • Generally reconsider the use of formatting elements/attributes in EAC-CPF and EAD3

@kerstarno
Copy link
Contributor Author

Potentially also include althead with <head>. For formatting attributes on <table>and its subelements see #8.

@kerstarno
Copy link
Contributor Author

Further conversation came to the following conclusions:

  • We'd still want to provide the ability to specify formatting for part of a larger body of text. Seeing that <emph> with render and <span> essentially do the same thing, the recommendation would be to decide for one of these with an inclination towards using <span>
  • There still might be necessity for @render with <foreign>, <title>, <titleproper> to allow targeted manipulation. However, seeing that the same could also be accomplished via other ways (e.g. is currently available as a subelement for all of these), we'd recommend being more concise with regard to definitions, examples, recommendations in the documentation.

@kerstarno
Copy link
Contributor Author

To follow up:

  • Provided we'd only use one of <span> and <emph>, there is the question of data type with regard to the attributes currently used with these elements. style recommends W3C CSS, while render comes with a predefined list of values.
  • Decided to review W3C CSS in this regard to potentially recommend adapted list of predefined values. (for 5 March)

@wisserk
Copy link

wisserk commented Feb 26, 2019

CSS values that may apply to @style/@render:

color (color, initial, inherit)

direction (ltr (left-to-right), rtl (right-to-left), initial, inherit)

font-family (family-name generic-family, initial inherit)

font-kerning (spacing of letters) (auto, normal, none)

font-size (medium, xx-small, x-small, small, large, x-large, xx-large, smaller, larger, length, %, initial)

font-size-adjust (number, none, initial, inherit)

font-stretch (ultra-condensed, extra-condensed, condensed, semi-condensed, normal, semi-expanded, expanded, ultra-expanded, initial, inherit)

font-style (normal, italic, oblique, initial, inherit)

font-variant (normal, small-caps, initial, inherit)

font-weight (normal, bold, bolder, lighter, 100-900 (values at each 100; defines from thin to thick characters; 400 = normal, 700 = bold), initial, inherit)

quotes (quotation marks, single, double, left and right angle quotes)

text-direction-color (color, initial, inherit)

text-decoration-line (none, underline, overline, line-through, initial, inherit)

text-decoration-style (solid, double, dotted, dashed, wavy, initial inherit)

initial = default value
inherit = inherits this property from its parent

@kerstarno
Copy link
Contributor Author

kerstarno commented Mar 5, 2019

Summary of today's conversation:

  • Lean towards EAC-CPF solution
  • I.e. do not have a list of predefined values - recommend CSS (as a standard dedicated to formatting/style specifically)
  • Support with documentation/examples in tag library and with schematron extension(s) for validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EAC-CPFAttributes These are attributes specifically used in EAC-CPF only at the moment EAD3Attributes These are attributes specifically used in EAD3 only at the moment SuggestionToMerge For suggestions to merge existing elements/attributes SuggestionToRename For suggestions to rename elements/attributes in either EAC-CPF or EAD3
Projects
None yet
Development

No branches or pull requests

2 participants