Closed aphillips closed 2 years ago
@r12a If you could take a close look at the changes I just added to the glossary. I applied the "definition" style to definitions and, in the course of doing that, re-arranged the order to be more logical (fewer "forward" definitions). I also made the UBA definition more-or-less consistent with i18n-glossary and made light edits to the "base direction" materials. It may be easier to view my edits from my repo, i.e. https://aphillips.github.io/string-meta
It could get worse: The direction of the value of the title value is given by the direction value value. ;-)
We're defining here the two uses of direction. Would direction metadata
work better than direction value
?
I think it's better than 'direction value', yes. But attributes also provide metadata – what's different is the mechanism used. I wonder whether there's another alternative: tuplet? property?
Perhaps 'key'? As in key/value pairs.
An attribute contains a name eq value sequence (per the XML spec).
JSON has key/value pairs.
So how about balancing the 'direction attribute' term with the term 'direction key/value pair' ?
So how about balancing the 'direction attribute' term with the term 'direction key/value pair' ?
I went a different direction with directional metadata field
since k-v pairs are just one way of doing this. Admittedly most data fields and data structures are basically key-value pairs. I also made edits (see d1c091e) to make clear(er) that attributes can be used to transmit or store metadata also.
@r12a Is this ready to merge yet? I want to do other work on string-meta (to answer my action items and to help with the explainer), but am blocked by these changes. I think we discussed them in telecon and have fixed all the issues?
Per I18N-ACTION-1125 merging this PR will the results of 573cb9b. @r12a should take a look at the resulting terminology section.
This also includes some minor updates and incorporates Felix's pull request (which was against my repo???) for action-1036.
Preview | Diff