Pursuant to Section 95488.9(b)(4) of the LCFS regulation, the Executive Officer may approve a new Temporary pathway for a fuel or feedstock-fuel combination not found in Table 8 of the LCFS regulation. Public comments on proposed new Temporary fuel pathways (posted below) will be accepted for 45 days prior to certification. If relevant comments received during this period require significant revisions of the originally published pathway, an updated pathway will be posted for additional public comment. Upon certification, this new Temporary pathway will be available for LRT-CBTS reporting for the quarter in which it is certified.
Prior to certification, the updated pathway CI values will be posted for 45 days for public comment. The Executive Officer will review and respond to relevant comments received during this period. Once certified, the updated pathway CI values are expected to be available for quarterly fuel reporting for the first quarter (Q1) of 2023.
Pursuant to Section 95488.7(d)(5) of the LCFS regulation, Tier 2 fuel pathway application packages are posted to this webpage for public comment after evaluation. Comments on each posted application package are accepted for ten (10) business days. Comments identifying potential factual or methodological errors in an application will be forwarded to the applicant. Upon receiving valid comments, applicants must either correct the errors identified and submit a revised application packet reflecting those corrections, or submit a detailed written response to the Executive Officer explaining why no revisions are necessary.
Tier 2 pathways that do not receive any comments or those for which applicant has provided responses deemed sufficient by the Executive Officer are certified and posted at Pathway Certified Carbon Intensities.
As of August 2021, the Committee has adopted seven general comments. The full list of adopted general comments are available in the database. Supporting documents on the most recent general comments and submissions received throughout the drafting processes are available below.
Java programs can have two kinds of comments: implementation comments and documentation comments. Implementation comments are those found in C++, which are delimited by /*...*/, and //. Documentation comments (known as \"doc comments\") are Java-only, and are delimited by /**...*/. Doc comments can be extracted to HTML files using the javadoc tool.
Implementation comments are meant for commenting out code or for comments about the particular implementation. Doc comments are meant to describe the specification of the code, from an implementation-free perspective. to be read by developers who might not necessarily have the source code at hand.
Discussion of nontrivial or nonobvious design decisions is appropriate, but avoid duplicating information that is present in (and clear from) the code. It is too easy for redundant comments to get out of date. In general, avoid any comments that are likely to get out of date as the code evolves.
Block comments are used to provide descriptions of files, methods, data structures and algorithms. Block comments may be used at the beginning of each file and before each method. They can also be used in other places, such as within methods. Block comments inside a function or method should be indented to the same level as the code they describe.
Short comments can appear on a single line indented to the level of the code that follows. If a comment can't be written in a single line, it should follow the block comment format (see section 5.1.1). A single-line comment should be preceded by a blank line. Here's an example of a single-line comment in Java code (also see \"Documentation Comments\" on page 9):
Very short comments can appear on the same line as the code they describe, but should be shifted far enough to separate them from the statements. If more than one short comment appears in a chunk of code, they should all be indented to the same tab setting.
The // comment delimiter can comment out a complete line or only a partial line. It shouldn't be used on consecutive multiple lines for text comments; however, it can be used in consecutive multiple lines for commenting out sections of code. Examples of all three styles follow:
Doc comments describe Java classes, interfaces, constructors, methods, and fields. Each doc comment is set inside the comment delimiters /**...*/, with one comment per class, interface, or member. This comment should appear just before the declaration:
Planning Note (9/19/2022): The due date for submitting comments has been extended to October 5, 2022 (it was originally September 21, 2022). Please see the Announcement section below for some specific feedback that NIST is seeking.
Another strategy to help the authors and editors interpret your comments is to carefully distinguish between your reflections and your requests. Reflections are nice, as they show the authors that you are deeply engaging with their work. But keep these reflections brief. We have seen reviews that run longer than the paper they are commenting on, which in turn require similarly lengthy responses back from the authors: this can put both authors and editors in a difficult position, especially if word limits are an issue. In the end, what matters are your suggestions for revision: actionable requests for more, less, or different material in certain parts of the paper. It may be helpful to demarcate these two sections clearly, so the authors know specifically what to respond to.
Submitted comments, including attachments and other supporting materials, will become part of the public record and are subject to public disclosure. Personally identifiable information and confidential business information should not be included (e.g., account numbers, Social Security numbers, names of other individuals). Comments that contain profanity, vulgarity, threats, or other inappropriate language will not be posted or considered.
The Eclipse Public License is similar to the Common Public License, and ourcomments on the CPL apply equally to the EPL. The only change is thatthe EPL removes the broader patent retaliation language regarding patentinfringement suits specifically against Contributors to the EPL'dprogram.
This license is identical to the Yahoo! PublicLicense 1.1, except that the license is provided by VMWare insteadof Yahoo!. Our comments there apply here as well; this is aGPL-incompatible, partial copyleft free software license.
(ii) If FDA receives comments on the guidance document, FDA will review those comments and revise the document when appropriate. If a version is revised, the new version will be placed on the Internet.
(5) You can comment on any guidance document at any time. Paragraph (h) of this section tells you how to submit your comments. FDA will revise guidance documents in response to your comments when appropriate.
(h) How should you submit comments on a guidance document (1) If you choose to submit comments on any guidance document under paragraph (g) of this section, you must send them to the Division of Dockets Management (HFA-305), 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.
Implicitly continued lines can carry comments. The indentation of thecontinuation lines is not important. Blank continuation lines are allowed.There is no NEWLINE token between implicit continuation lines. Implicitlycontinued lines can also occur within triple-quoted strings (see below); in thatcase they cannot carry comments.
Multiple adjacent string or bytes literals (delimited by whitespace), possiblyusing different quoting conventions, are allowed, and their meaning is the sameas their concatenation. Thus, \"hello\" 'world' is equivalent to\"helloworld\". This feature can be used to reduce the number of backslashesneeded, to split long strings conveniently across long lines, or even to addcomments to parts of strings, for example:
Expressions in formatted string literals are treated like regularPython expressions surrounded by parentheses, with a few exceptions.An empty expression is not allowed, and both lambda andassignment expressions := must be surrounded by explicit parentheses.Replacement expressions can contain line breaks (e.g. in triple-quotedstrings), but they cannot contain comments. Each expression is evaluatedin the context where the formatted string literal appears, in order fromleft to right.
C# provides a mechanism for programmers to document their code using a comment syntax that contains XML text. In source code files, comments having a certain form can be used to direct a tool to produce XML from those comments and the source code elements, which they precede. Comments using such syntax are called documentation comments. They must immediately precede a user-defined type (such as a class, delegate, or interface) or a member (such as a field, event, property, or method). The XML generation tool is called the documentation generator. (This generator could be, but need not be, the C# compiler itself.) The output produced by the documentation generator is called the documentation file. A documentation file is used as input to a documentation viewer; a tool intended to produce some sort of visual display of type information and its associated documentation.
This specification suggests a set of standard tags to be used in documentation comments, but use of these tags is not required, and other tags may be used if desired, as long as the rules of well-formed XML are followed. For C# implementations targeting the CLI, it also provides information about the documentation generator and the format of the documentation file. No information is provided about the documentation viewer.
Comments having a certain form can be used to direct a tool to produce XML from those comments and the source code elements that they precede. Such comments are Single-Line_Comments (6.3.3) that start with three slashes (///), or Delimited_Comments (6.3.3) that start with a slash and two asterisks (/**). They must immediately precede a user-defined type or a member that they annotate. Attribute sections (21.3) are considered part of declarations, so documentation comments must precede attributes applied to a type or member. 59ce067264