RE: [xliff-omos] Modules and extensions

In 0.9.4 the text property of the element-xx objects has been removed. It made serialization nice and easy and simplified the model. Was it deemed unnecessary?

Phil Ritchie

Chief Technology Officer

Vistatec

Vistatec House, 700 South Circular Road,
Kilmainham, Dublin 8, Ireland.

Tel:

+353 1 416 8000

Direct:

+353 1 416 8024

Email:

phil.ritchie@vistatec.com

www.vistatec.com

ISO 9001

ISO 13485

ISO 17100

Think Global

From: xliff-omos@lists.oasis-open.org [mailto:xliff-omos@lists.oasis-open.org] On Behalf Of Robert van Engelen
Sent: 20 June 2017 19:18
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org>
Subject: Re: [xliff-omos] Modules and extensions

Yves, Chase, Felix, David and other TC members,

I have made the changes to the JLIFF draft schema 0.9.4 and the three examples, as we discussed in the meeting last week. Let me know if this looks OK.

I am working on examples of extensions based on JSON-LD.

Thanks.

Dr. Robert van Engelen, CEO/CTO Genivia Inc.
voice: (850) 270 6179 ext 104
fax: (850) 270 6179
mobile: (850) 264 2676
engelen@genivia.com

On May 25, 2017, at 8:27 AM, Yves Savourel <ysavourel@enlaso.com> wrote:

Thanks for the reminder Felix.

Like Phil, I’m just wondering about the cost of JSON-LD when various namespaces are mixed in the same object.

Looking at examples such as those here: https://json-ld.org/spec/latest/json-ld-api-best-practices/#dfn-json-ld-context, the resolution of the namespaces seems relatively complicated and changes the object structure. But I’m probably missing a lot.

Cheers,

-yves

Yves Savourel
Localization Solutions Architect | t: 303.951.4523 | f: 303.516.1701 | ENLASO®

From: Felix Sasaki [mailto:felix@sasakiatcf.com]
Sent: Thursday, May 25, 2017 12:55 AM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org>
Subject: Re: [xliff-omos] Modules and extensions

Hi Yves, all,

previously in this thread people said they are worried about ad hoc created namespace resolution systems. I understand the worry about json-ld complexity, but at least it is a standard solution, with many libraries available. Just my two cent ...

(I understand that it is likely that people won't go the json-ld path, this is just my last attempt to mention this approach)

- Felix

2017-05-25 4:28 GMT+02:00 Yves Savourel <ysavourel@enlaso.com>:

Hi Robert, all,

Ø  I’m inclined to stick to _ to separate prefix from name, assuming _ are forbidden in prefixes and names by self-imposed JLIFF conventions. Underscore is at least widely supported in variable names.

A ‘_’ would be fine with me.

I was just under the impression ‘$’ was the preference for you (and maybe others).

I just wanted to be sure it would work with _javascript_.

Ø  Other programming languages may not accept $ in hard-coded property/variable names…

Quite right. But I wonder if it matters: Languages other than _javascript_ are likely to go through some kind of marshalling of the JSON data into their own data structures and have ways to address such issue. Actually _javascript_ is probably a special case: the more I work on JLIFF, the more I think it’d be quite hard for most languages to just rely on default automated mapping mechanism to get the proper input/output. But hopefully I’m wrong.

Cheers,

-yves

From: Robert van Engelen [mailto:engelen@genivia.com]
Sent: Tuesday, May 23, 2017 11:11 AM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org>
Subject: Re: [xliff-omos] Modules and extensions

I’m inclined to stick to _ to separate prefix from name, assuming _ are forbidden in prefixes and names by self-imposed JLIFF conventions. Underscore is at least widely supported in variable names.

Other programming languages may not accept $ in hard-coded property/variable names (i.e. console.log(x.name.b) is "hard-coded" and so is console.log(x[“name.b”]) also hard-coded, but with a period in the property name that requires quotes).

- Robert

Dr. Robert van Engelen, CEO/CTO Genivia Inc.
voice: (850) 270 6179 ext 104
fax: (850) 270 6179
mobile: (850) 264 2676
  engelen@genivia.com

On May 23, 2017, at 1:03 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

Regarding separator, from quick tests:

Dollar-sign would work, but not period, IMO:

var x = {"name$b": "text"};

console.log(x.name$b); à ok

var x = {"name.b": "text"};

console.log(x.name.b); à error

More tests are probably needed.

cheers,

-yves

xliff-omos message