OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC

Robert   Before you add a new “type” property to the top of the jliff schema I am just checking my serialization code as I believe it works using the “type” property of the object we would store in “content”.   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 Think Global 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.  

Phil, Robert,  Just an orthogonal issue..  I believe we agreed to use "root" rather than "content"?  @Phil, did you send me the minutes?  Cheers and thanks dF  On Oct 12, 2017 15:17, "Phil Ritchie" < phil.ritchie@vistatec.com > wrote: Robert   Before you add a new “type” property to the top of the jliff schema I am just checking my serialization code as I believe it works using the “type” property of the object we would store in “content”.   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 Think Global 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.  

David   Chase was less enthusiastic about ‘root’. How about ‘contentType’, ‘body’, ‘subDocument’, ‘extract’, ‘data’…   My favourite is still ‘content’.   I’ll send the minutes on now…   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 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: David Filip [mailto:david.filip@adaptcentre.ie] Sent: Thursday 12 October 2017 14:28 To: Phil Ritchie <phil.ritchie@vistatec.com> Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org>; Robert van Engelen <engelen@genivia.com> Subject: Re: [xliff-omos] Schema changes   Phil, Robert,  Just an orthogonal issue..  I believe we agreed to use "root" rather than "content"?  @Phil, did you send me the minutes?    Cheers and thanks dF    On Oct 12, 2017 15:17, "Phil Ritchie" < phil.ritchie@vistatec.com > wrote:   Robert   Before you add a new “type” property to the top of the jliff schema I am just checking my serialization code as I believe it works using the “type” property of the object we would store in “content”.   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 Think Global 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.    

Checking the schema actually Files/Fragment, Group/MetaGroup don’t have a ‘type’ property. Then ‘subunit’ does have type because it can be ‘segment’ or ‘ignorable’. Serialization-wise the * objects contained * in ‘content’ (or whatever) should have a ‘type’ so the right concrete object can be de-serialized.   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 Think Global 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: xliff-omos@lists.oasis-open.org [mailto:xliff-omos@lists.oasis-open.org] On Behalf Of Phil Ritchie Sent: Thursday 12 October 2017 14:17 To: Robert van Engelen <engelen@genivia.com> Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org> Subject: [xliff-omos] Schema changes     Robert   Before you add a new “type” property to the top of the jliff schema I am just checking my serialization code as I believe it works using the “type” property of the object we would store in “content”.   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 Think Global 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.    

Robert   Please don’t go to the effort of changing the schema. I hit a road-block and not sure it’s the right way to go after all.   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 Think Global 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: Phil Ritchie Sent: Thursday 12 October 2017 15:17 To: Phil Ritchie <phil.ritchie@vistatec.com>; Robert van Engelen <engelen@genivia.com> Cc: XLIFF OMOS TC <xliff-omos@lists.oasis-open.org> Subject: RE: Schema changes   Checking the schema actually Files/Fragment, Group/MetaGroup don’t have a ‘type’ property. Then ‘subunit’ does have type because it can be ‘segment’ or ‘ignorable’. Serialization-wise the * objects contained * in ‘content’ (or whatever) should have a ‘type’ so the right concrete object can be de-serialized.   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 Think Global 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: xliff-omos@lists.oasis-open.org [ mailto:xliff-omos@lists.oasis-open.org ] On Behalf Of Phil Ritchie Sent: Thursday 12 October 2017 14:17 To: Robert van Engelen < engelen@genivia.com > Cc: XLIFF OMOS TC < xliff-omos@lists.oasis-open.org > Subject: [xliff-omos] Schema changes     Robert   Before you add a new “type” property to the top of the jliff schema I am just checking my serialization code as I believe it works using the “type” property of the object we would store in “content”.   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 Think Global 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.