Çağtay Fabry

can you try opening a dev-console on your browser (should be F12 on most browsers) and see if and what kind of error gets reported there if for example there...

Glad to hear, I could really see this simplifying some things From my understanding whatever goes into the `tag:` value should actually be independent from URI structure requirements since it...

Using regex would certainly be more powerful, especially when trying to parse the string part of the URI. Personally I would prefer keeping it simple wherever possible. In this case...

See my comment on https://github.com/asdf-format/asdf/pull/858 (which apparently I was typing at the same time ;) ) besides I don't mind using `http://stsci.edu/schemas/asdf/core/software-1.*` over `http://stsci.edu/schemas/asdf/core/software-1` at all If tag and version...

I also thought about something like `subtype` (basically how we handly numpy datetime dtypes in our own classes currently). It might prevent bloating the supported dtypes and end up more...

> That's a good point, `subtype` is more convenient for that sort of thing. We could add another custom validator to allow schema authors to restrict the subtype value. >...

quick reminder that ```yaml tag: http://asdf-format.org/schemas/ndarray* ``` should also be possible now > I also thought about something like `subtype` (basically how we handly numpy datetime dtypes in our own...

Listing and supporting document schemas in the file (regardless of implementation) would be an excellent addition to the standard in my opinion.

this would be a great addition to ASDF 👍

Does the update workflow also work on 'exploded' asdf files? That could prevent any changes to the binary files unless changed.