Lars Trieloff

Some additional info: https://www.w3.org/TR/xml/#charsets > `Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]` `#x1B` is not in that range and needs to be removed

I'm happy to incorporate this into #4527 (which has been auto-closed, unfortunately)

According to the change logs linked in http://json-schema.org/specification-links.html#draft-7 there are no functional changes in draft 07, just a clarification of language. It might still make sense to upgrade, as most...

After going through the history, it looks like `repo:createdDate` is the correct version. I might have confused it with `xmp:createDate` (XMP also uses `modifyDate`), but `repo:` in general uses `created*`...

The `repo` schemas only follow whatever the ACP is defining (albeit in a buggy way – see above). The `xdm` schemas are in our control and XDM contributors found it...

That would be @ogoldman

I think the CNCF is a reputable enough consortium with wide industry support and definitely not unknown. CloudEvents seems like a 100% match to our use case, opposed to Activity...

I assume with XDM/Activity Streams being the default. My concern would be that XDM/Activity Streams are being perceived as "Adobe's proprietary event format", just like I'd perceive Azure's default as...

In the console, and in the documentation, and in marketing collateral, and in the user's perception ;)

This is the extensibility mechanism we've implemented for XDM: https://github.com/adobe/xdm/blob/master/docs/extensions.md Moving it to a config sounds reasonable, but we should not break the way it works right now.