[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff-omos] Changes to schema discussed in last meeting.
The JLIFF repo is updated: A JLIFF root is on of these three choices: Files array of file (fragment) Subfiles array of subfile Unit or group (a subfile) identified by “kind”:”unit” (default) or “kind”:”group” Subunits in case of unit Subfiles in case of group, an array of subfile (unit or group) Subfiles array of subfile Unit or group (a subfile) identified by “kind”:”unit” (default) or “kind”:”group” Subunits in case of unit Subfiles in case of group, an array of subfile (unit or group) Subunits I believe this captures our conversation. I could not use “type” to identify “unit” or “group” since “type” is a property of the unit and group types. I think “kind” works fine. I also updated the XLIFF-JLIFF wiki page to reflect this structure: I’ve updated the examples to reflect the use of “subfiles” and added a 5th example that highlights the use of “kind”:”group”. The list of changes (see also the README): - added `subfiles` array type and `subfile` object type with unit or group content identified by `"kind": "unit"|"group"` where `"unit"` is the default, using `"kind"` instead of `"type"` due to a name clash; - changed `"type": "segment"|"ignorable"` to `"kind": "segment"|"ignorable"` for consistency of the `"kind"` type selector; - changed `fragment` to `file` for sake of naming consistency; - reduced top-level jliff type choices to three: `"files"`, `"subfiles"`, and `"subunits”`; - added `"NMTOKEN"` type for `"id"` values with value space identical to XLIFF id NMTOKEN values. Thanks and enjoy! Dr. Robert van Engelen, CEO/CTO Genivia Inc. voice: (850) 270 6179 ext 104 fax: (850) 270 6179 mobile: (850) 264 2676
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]