{"title":"2. Introduction","authors":"","doi":"10.1515/9783110687675-002","DOIUrl":null,"url":null,"abstract":"1. Revisions 1) Incorporated feedback from SSC Working Group. Complete rewrite. 2) Reworked to meet comments from Sept 2006 SSC-3 WG. Move to a new log page that will have multiple pieces of information. The intent is that each of these log pages can be expanded with information specific to the TapeAlert (or error). In doing this, I thought it prudent to use a common structure for all specific flags. 3) Corrected math in Degredation Indicator 4) Incorporated changes suggested in the January working group. I have completed scrubbing the device information fields. I have not completed scrubbing the medium information fields, but there has been significant work done so I wanted to get this out to let other eyes have time to look at it. Since the work has been so extensive I have not carried foward markings for all the strikeouts and additions. 5) Mar SSC-3 WG covered through Device information and only the medium identifier (i.e. barcode's). 6) 06-138r4: Incorporated suggestions from Mar WG and did additional work. 7) 06-138r5: Incorporated suggestions from the July WG and did additional work. In response to the ISV Feedback this is a proposal for how to modify the TapeAlerts and specify which are hardware, which are media, and which are firmware. Additionally since this is being approached there have been many suggestions for how to greatly improve the useability and usefulness of this information. I have attempted to incorporate many of these suggestions. Red text are notes to the editor Red strikethrough is text deleted from existing standard Blue text is text added to existing standard Green text signifies that I have completed incorporating notes or suggestions. I suggest they be looked at to ensure I incorporated them as desired.","PeriodicalId":269949,"journal":{"name":"›Prometheus Bound‹ – A Separate Authorial Trace in the Aeschylean Corpus","volume":"34 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"›Prometheus Bound‹ – A Separate Authorial Trace in the Aeschylean Corpus","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1515/9783110687675-002","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
1. Revisions 1) Incorporated feedback from SSC Working Group. Complete rewrite. 2) Reworked to meet comments from Sept 2006 SSC-3 WG. Move to a new log page that will have multiple pieces of information. The intent is that each of these log pages can be expanded with information specific to the TapeAlert (or error). In doing this, I thought it prudent to use a common structure for all specific flags. 3) Corrected math in Degredation Indicator 4) Incorporated changes suggested in the January working group. I have completed scrubbing the device information fields. I have not completed scrubbing the medium information fields, but there has been significant work done so I wanted to get this out to let other eyes have time to look at it. Since the work has been so extensive I have not carried foward markings for all the strikeouts and additions. 5) Mar SSC-3 WG covered through Device information and only the medium identifier (i.e. barcode's). 6) 06-138r4: Incorporated suggestions from Mar WG and did additional work. 7) 06-138r5: Incorporated suggestions from the July WG and did additional work. In response to the ISV Feedback this is a proposal for how to modify the TapeAlerts and specify which are hardware, which are media, and which are firmware. Additionally since this is being approached there have been many suggestions for how to greatly improve the useability and usefulness of this information. I have attempted to incorporate many of these suggestions. Red text are notes to the editor Red strikethrough is text deleted from existing standard Blue text is text added to existing standard Green text signifies that I have completed incorporating notes or suggestions. I suggest they be looked at to ensure I incorporated them as desired.