I think these could be fileLocations, and I would not object to the change. There are scenarios where having a region might be useful, but I do not think they would occur in practice. For instance, process 1 writes stdout to a log file, then process 2 appends output to the same log file. Jim On 03/22/2018 07:18 PM, Larry Golding (Comcast) wrote: The spec defines each of these properties as a physicalLocations = { fileLocation + region }. James, remind me please why it’s not just a fileLocation. Is there a scenario where one of these streams occupies just a portion of a file? Do some tools embed the contents of these streams in their native log file format? Larry