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

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: +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
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.

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