Profile

Yes, my thought was that it would be easier to reference the context. The fictional URI I used in the examples in my FEISGILTT slides was: ( "@context":" http://docs.oasis-open.org/xliff-omos/jliff/v2.1/jliff-v2.1.jsonld ", "jliff": "2.1" "srcLang": "en" ... ) It seemed to me that if we used @context ...

Hi all, I've pushed a working draft of a JSON-LD context file to github. Currently, this just defines all of the namespaces/prefixes from the XLIFF spec. A few notes about issues we should work through: I've included the 'xliff' prefix. In practice, we've been assuming that this namespace is implicit ...

No, I was just saying that there are cases where we can't guarantee that the data types are preserved, and this is bad, but it's also within the language of the spec. I think there's a difference between custom extensions and unsupported modules, however. For all modules, even unsupported ones, the schema ...

Picking this thread up after a long time. I included Yves's issue with data typing in unsupported extensions in the "challenges" section of the presentation on JLIFF I gave at FEISGILTT today. I had included the relevant text from the XLIFF 2.0 spec on a slide: "Writers that do not support a given custom ...

Hi Robert, On Tue, Oct 10, 2017 at 6:50 AM, Robert van Engelen wrote: I believe compact IRIs https://json-ld.org/spec/ latest/json-ld/#compact-iris p rovide a mapping for IRIs to prefixes, by using @context to hold prefix-IRI bindings. For example, given the context ( "@context": ( "gl": "urn:oasi ...