Thanks Paul, I’m probably remembering wrong, then. I’ll go ahead and make this change. Larry From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org> On Behalf Of Paul Anderson Sent: Monday, March 26, 2018 6:13 AM To: Larry Golding (Comcast) <
larrygolding@comcast.net>;
sarif@lists.oasis-open.org Cc: 'Michael Fanning' <
Michael.Fanning@microsoft.com>; 'James A. Kupsch' <
kupsch@cs.wisc.edu> Subject: Re: [sarif] RE: stdin/stderr/stdout/stdoutStderr: fileLocation or physicalLocation Larry: On 3/23/2018 5:36 PM, Larry Golding (Comcast) wrote: PS Michael and I were trying to remember if anybody had a realistic scenario for extracting one of these standard streams from a portion of a file (rather than it occupying the entire file). We thought it might have been Paul. Paul, did you mention a scenario for this at the Face to Face meeting? I have no memory of doing so, but I confess I don't remember that conversation very well. I'll keep racking my brain. -Paul Thanks, Larry From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Comcast) Sent: Friday, March 23, 2018 2:19 PM To:
sarif@lists.oasis-open.org Cc: 'Michael Fanning' <
Michael.Fanning@microsoft.com> ; 'James A. Kupsch' <
kupsch@cs.wisc.edu> Subject: [sarif] RE: stdin/stderr/stdout/stdoutStderr: fileLocation or physicalLocation I filed Issue #133 , "Make stdin/stdout/stderr/stdoutStderr fileLocation instead of physicalLocation." I uploaded a change draft: Documents/ChangeDrafts/Active/sarif-v2.0-issue-133-stream-files-as-fileLocations.docx I’ll move to adopt it at the next TC meeting. Thanks, Larry
Original Message----- From: Larry Golding (Comcast) < larrygolding@comcast.net > Sent: Friday, March 23, 2018 11:34 AM To: 'James A. Kupsch' < kupsch@cs.wisc.edu >; ' sarif@lists.oasis-open.org ' < sarif@lists.oasis-open.org > Cc: 'Michael Fanning' < Michael.Fanning@microsoft.com > Subject: RE: stdin/stderr/stdout/stdoutStderr: fileLocation or physicalLocation Michael agrees. I'll file the issue and push a change draft. This one is in the gray area between "bug -- obviously subject to editorial discretion" and "substantive change". I suggest we put this one to the TC for approval. Larry
Original Message----- From: James A. Kupsch < kupsch@cs.wisc.edu > Sent: Friday, March 23, 2018 7:40 AM To: Larry Golding (Comcast) < larrygolding@comcast.net >; sarif@lists.oasis-open.org Cc: 'Michael Fanning' < Michael.Fanning@microsoft.com > Subject: Re: stdin/stderr/stdout/stdoutStderr: fileLocation or physicalLocation 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 > -- Paul Anderson, VP of Engineering, GrammaTech, Inc. 531 Esty St., Ithaca, NY 14850 Tel: +1 607 273-7340 x118; http://www.grammatech.com