Julia Signell

> Hey there, let me know if you want me to take on any of the todos above, and if so if I should PR to your branch. No worries...

> More generally, I wouldn't want us to use a different data structure just for doctests. However in some cases, like the HLG case above, it probably does make sense...

Yeah I agree, not a blind effort, but maybe a good-faith attempt to unskip. I think there have been some doctests where the doctests are just skipped because of copy/pasting...

It seems that it might be useful to support this in general in holoviews. There are hints at it in the docs: http://holoviews.org/user_guide/Customizing_Plots.html#Yaml-equivalent

I have definitely not thought about this as much as you guys, but I was definitely not trying to suggest that any data be stored, just field names, ranges, options...

Good question. I do like the recommendation to only include fields that are useful (especially for self-describing file formats where the metadata already exists within the dataset itself). I think...

Hmm. I agree that the best practices could use some updates, but I'm not persuaded that this means they need to move from the spec repo. Lot's of libraries store...

After writing that I realized that the master branch is the released version and is the default. I think if we just change that setting in github, so that dev...

The best practices doc (from branch `dev`) with its git history has now been moved to the new repo.

Hmm. Yeah I don't think you are misreading. That stac-examples repo is also archived, so I don't imagine the stac-spec docs ought to be linking to it anymore. @m-mohr was...