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:
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:]
Sent: Thursday 12 October 2017 14:28
To: Phil Ritchie <>
Cc: XLIFF OMOS TC <>; Robert van Engelen <>
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" <> 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:
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.
