All, I've asked Kevin to go ahead with this and he relaid the request to Ian. He also asked me to notify you of this: "By the way, I'm currently having a problem with my ISP interacting with Google's email configuration. Turns out that my most recent message to tei-council (which said that I could ask Ian to do the CORS thing if you all reached consensus) is what triggered the messages that all people with Gmail accounts received about their subscription having been "disabled due to excessive bounces". I immediately re-enabled everyone's subscription, and no messages were sent to the list in the meantime, so no one missed anything." Raff On Tue, Nov 15, 2016 at 4:07 AM, James Cummings wrote:

Completely reasonable thing to do IMHO.

James

-- Dr James Cummings, Academic IT Services, University of Oxford

On 14 Nov 2016 22:30, Syd Bauman wrote: Since our main purpose in life is to disseminate this information, no objeciton here. That said, there is the risk that a JavaScript application hides from the end user that older versions of something (like the Guidelines or a schema) is being fetched. But the benefits outweigh that risk, IMHO.

...

Currently it doesn't seem to be possible to request files from the Vault via JavaScript. This is simple to solve by allowing CORS https://en.wikipedia.org/wiki/Cross-origin_resource_sharing on the server that holds the Vault, but the system admin will have to do that (Kevin?).

I can't imagine this would be problematic: it would simply allow anyone building a JavaScript application to obtain any text, XML, and JSON file on the fly. It certainly would be convenient for the Roma replacement I'm working on.

Any objections? -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived