Stream: committers
Topic: Shading non-supported elements in the dictionary view
Lloyd McKenzie (Aug 25 2016 at 21:41):
A while back, I'd introduced shading of the lines in the snapshot view to show which elements were "mustSupport" vs. not. General feedback was that it was too busy, so we changed to the bright "S" icons. The same need to differentiate between "mustSupport" and other elements also exists on the data dictionary page (the one with all of the definitions). I don't think the icon approach will work there, as you actually want to visually distinguish the complete set of text. (And we also don't use icons on those pages). I think the shading would be much less busy because you won't have close-proximity alteration of background color. Does anyone object to me making the change so we can see how it looks? (Worst case, I can roll it back.)
Grahame Grieve (Aug 25 2016 at 21:42):
it seems to me that this is something that is only appropriate for terminal profiles - as in, implementable profiles that are not expected to be constrained further
Grahame Grieve (Aug 25 2016 at 21:43):
and not for stuff in the spec.
Grahame Grieve (Aug 25 2016 at 21:44):
So I think that this should be configurable. Two options come to mind:
- a setting in the IG control file
- surfacing this is a class on the <tr> in the generated html so it can be in the css
Lloyd McKenzie (Aug 25 2016 at 22:12):
I'm not sure what constitutes a terminal profile. I would expect it to be useful for things like DAF - it's not necessarily terminal, but it's still useful to be able to go through and quickly scan "what I have to worry about" vs not. We're not removing the content. If you want to look at the not-supported stuff, you can, but it'd just obvious what are the parts that are "important" in the context of this particular profile.
Lloyd McKenzie (Aug 25 2016 at 22:13):
That said, I'm ok with the css approach. IGs can then make the decision. I might make it a distinct color in the default IG so that publishers are even aware it's an option, they can then override it back if they want.
Grahame Grieve (Aug 26 2016 at 02:35):
better to document it than make it the default
Eric Haas (Aug 27 2016 at 06:34):
I think having a way to toggle between the must support elements and the full snapshot in the definitions page would be nice. So is easier to filter out the none must supports and all the DomainResource stuff
Last updated: Apr 12 2022 at 19:14 UTC
