Brendan O'Brien

Hi @yiminc! not at present, but it's something I've been wondering about myself. Do you have a use case in mind that would help flesh out such a feature?

Thankfully the spec has [guidance on regex interop](http://json-schema.org/latest/json-schema-validation.html#regexInterop). Specifically: > given the high disparity in regular expression constructs support, schema authors SHOULD limit themselves to the following regular expression tokens:...

I agree that this package is not 100% compliant with the spec, but not for this reason. The section from the spec you're quoting: > This string SHOULD be a...

Thanks for filing this @robfig. Totally agreed the error you've encountered is a bug that needs fixing. I think @handrews has articulated the we should try to tackle here: >...

@robfig I'd be happy to work with you on the change, I can write up a rough outline of a PR we'd accept if you're ok with implementing the change

hahah looks like we came to the same conclusion @robfig 😄

Sorry for the delay on this @robfig we would _absolutely_ be open to such a thing. We've been meaning to implement such facilities for a while, but are too bogged...

If there's anything you need from us before filing, like working out the interface, I'd be happy to collaborate on this issue. Otherwise I'll make sure a few of us...

This is looking _really_ good! Try adding this after line 646 of `schema_test.go` in that branch 😉 ```go rs.FetchRemoteReferences() ```

👋 @RandomFractals, thanks for filing! That is certainly not a helpful error message. This problem is an issue in the publication process getting into an unrecoverable state. Related issue: https://github.com/qri-io/qri/issues/1212...