This extension doesn't scale well

[m-mohr]

Binding specific language-specific implementation details to the metadata, seems like a bad idea.
If we would have extensions for R, C, Java, Julia, JS, whatever, the metadata would explode.
If at some point xarray changes, you'd need to update your whole metadata, too.
I think this extension should either be generalized to work for various languages and environments or just go away (sorry, hot take, I know.)

[TomAugspurger]

I'm not too worried about that.

[TomAugspurger]

One thing that has changed since this was started is xpystac exists now. But that will use information in xarray-assets to load the data.

If I were starting from scratch, it'd be better to put some bits of information (like the storage account of some dataset) in a separate azure-blob-storage extension, chunking information in some other extension, and then have a library like xpystac collect all that necessary information to open the asset. But oh well.

Still, it's worth linking to xpystac from the readme.