Leonard Rosenthol

> plaintext with markers for non-editable content should usually be enough Using only Plaintext with markers is (for the most part) the equivalent of tying the software's hands behind its...

>Are there spell checkers as of now that take formatting such as bold and font-size 28px into consideration? Absolutely! The one built into MSOffice, for example, uses styling and semantics...

There is no need to fork the repo...just go ahead and create a branch with your changes and when ready raise the PR for us to review. If you'd like...

The original “Core Asset Data Model”, on which the core asset and other schemas were defined, started from XMP. As such, those definitions take precidence.

Oliver and I have a proposal we are working through for how to resolve this - its' related to our discussion about setting up a separate git repo...

My big concern here is that activity streams are an open standard from a well defined SDO, while CloudEvents are a proprietary spec from an unknown industry consortium. I would...

@dauwhe - great questions. IMO, they are all product questions not spec questions. Each of those items that you asked about would be consider an implementation decision of a given...

@msporny Why wouldn't we use namespaces/contexts here instead? Isn't the whole point of such things to avoid the need for a registry?

I'm a bit confused here... The JSON Schema spec, as referenced, is very clear that NUMBER/Integer is arbitrary precision - which means that there is no need to specify if...

@kstreeter The limitation of 53bits is only in specific implementations (eg. JavaScript), not systemic to XDM or JSON. JSON itself is format & implementation agnostic (as noted in its spec).