OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-omos message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xliff-omos] locQualityIssue id


Robert, Phil, all

2 issues WRT the Localization Quality Issue ids.

1)Â There should be no id onÂlocQualityIssue, singular, the individual entry.. they are NOT referencable individually either in XLIFF 2.1 or in ITS 2.0. Having the individual ids would cause a data model disparity.
@Robert van EngelenÂÂwould you please remove the id from this one?

Â2) Great that we now have the id onÂlocQualityIssues, plural, the array wrapper
However, this id is not the regular XLIFF id which is an NMToken. This one comes from ITS 2.0 that reuses the xml:id which is stricter, i.e. NCName
@Robert van EngelenÂwould you please create the NCName type and use for this id? NCnames will satify NMToken but -- on top of NMToken restrictions -- MUST NOT start with numbers and MUST NOT contain colons.

Although this is the only NCName occurrence to my knowledge s far, I think this should be generalized same as the NMtoken type..Â

Cheers dF

Dr. David Filip
===========
Convenor, JTC 1/SC 42/WG 3 Trustworthiness of AI | National mirror chair, NSAI TC 02/SC 18 AI | Head of the Irish national delegation, ISO/IEC JTC 1/SC 42 AI | Chair & Editor, OASIS XLIFF OMOS TCÂ | Secretary & Lead Editor, OASIS XLIFF TC | NSAI expert to ISO/IEC JTC 1/SC 38 Cloud Computing, ISO TC 37/SC 3 Terminology management, SC 4 Language resources, SC 5 Language technology
Moravia Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122




On Sat, Nov 24, 2018 at 3:27 PM Robert van Engelen <engelen@genivia.com> wrote:

Hi Phil,

Please fetch commitÂd899655Âwith the latest changes, see the diffs:Âhttps://github.com/oasis-tcs/xliff-omos-jliff/commit/d8996559a57c1f2b8c53af852d44a08d9bf13314#diff-b89ba9003dca25e3d00f69ed10fdb1bfÂ

The BLUE part is what I changed in the schema to add the id property:

  "locQualityIssues": {
   "description": "A standoff wrapper element to group any number of single issue elements related to the same span of source or target content",
   "type": "object",
   "properties": {
    "id": { "$ref": "#/definitions/NMTOKEN" },
    "items": {
     "type": "array",
     "items": { "$ref": "#/definitions/locQualityIssue" },
     "minItems": 1
    }
   },
   "additionalProperties": false,
   "required": [ "items" ]
  },


TheÂlocQualityIssueÂtype had its id property added some time ago, so I left it untouched.

Thanks.

- Robert

 Dr. Robert van Engelen, CEO/CTOÂGenivia Inc.

On Nov 22, 2018, at 11:35 AM, Phil Ritchie <phil.ritchie@vistatec.com> wrote:


Robert
Â
Thanks for the commit but despite your explanation below it looks like you have added the id property to the contained locQualityIssueâs instead of the wrapper.
Â
<image001.png>
Â
Phil
Â


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Â|ÂISOÂ27001
Vistatec
ThinkÂGlobal
FacebookLinkedInTwitterGoogle Plus
Vistatec Ltd. Registered in Ireland 268483. Registered Office, Vistatec House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s).Â
âThe unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden.Â
If you have received this message in error please notify the sender immediately.

From:ÂRobert van Engelen <engelen@genivia.com>Â
Sent:ÂTuesday 13 November 2018 17:13
To:ÂPhil Ritchie <phil.ritchie@vistatec.com>
Cc:ÂXLIFF OMOS TC <xliff-omos@lists.oasis-open.org>
Subject:ÂRe: [xliff-omos] locQualityIssue id
Â
Â
Phil et al.
Â
The JLIFF 2.1 schema in the GitHub repo is updated to include the id property on locQualityIssue.
Â
Quoting David:
Â
JLIFF the id should be on the wrapper array
Â
This means we need an object that wraps the array. The object will contain the id property and an array property:
Â
  "its_locQualityIssues": {
   "description": "A standoff wrapper element to group any number of single issue elements related to the same span of source or target content",
   "type": "object",
   "properties": {
    "id": { "$ref": "#/definitions/NMTOKEN" },
    "items": {
     "type": "array",
     "items": { "$ref": "#/definitions/its_locQualityIssue" },
     "minItems": 1
    }
   },
   "additionalProperties": false,
   "required": [ "items" ]
  },
Â
The property name for the the array âitemsâ is somewhat arbitrary. Any ideas for a better name?
Â
- Robert
Â
 Dr. Robert van Engelen, CEO/CTOÂGenivia Inc.
 voice: (850) 270 6179 ext 104
 fax: (850) 270 6179
 mobile: (850) 264 2676
Â
On Nov 5, 2018, at 12:46 PM, Phil Ritchie <phil.ritchie@vistatec.com> wrote:
Â

I think we need locQualityIssue to have an id property. Otherwise I see no way to reference an individual issue within an array of locQualityIssues when using standoff.
Â
PhilÂRitchieâ
ChiefÂTechnologyÂOfficer
Â|Â
Vistatec
VistatecÂHouse,Â700ÂSouthÂCircularÂRoad,
Kilmainham,ÂDublinÂ8,ÂIreland.
Tel:Â
Â|Â
Direct:Â
Email:Â
Â|Â
ISOÂ9001
Â|Â
ISOÂ13485
Â|Â
ISOÂ17100
Â|Â
ISOÂ27001
Vistatec
ThinkÂGlobal
Facebook
LinkedIn
Twitter
Google Plus
Vistatec Ltd. Registered in Ireland 268483. Registered Office, Vistatec House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s).Â
âThe unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden.Â
If you have received this message in error please notify the sender immediately.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]