In chemical nomenclature, a preferred IUPAC name (PIN) is a unique name, assigned to a chemical substance and preferred among the possible names generated by IUPAC nomenclature. The "preferred IUPAC nomenclature" provides a set of rules for choosing between multiple possibilities in situations where it is important to decide on a unique name. It is intended for use in legal and regulatory situations.[1]
Preferred IUPAC names are applicable only for organic compounds, to which the IUPAC has the definition as compounds which contain at least a single carbon atom but no alkali, alkaline earth or transition metals and can be named by the nomenclature of organic compounds[2] (see below). Rules for the remaining organic and inorganic compounds are still under development.[3] The concept of PINs is defined in the introductory chapter (freely accessible) and chapter 5 of the "Nomenclature of Organic Chemistry: IUPAC Recommendations and Preferred Names 2013",[4] which replace two former publications: the "Nomenclature of Organic Chemistry", 1979 (the Blue Book) and "A Guide to IUPAC Nomenclature of Organic Compounds, Recommendations 1993". The full draft version of the PIN recommendations ("Preferred names in the nomenclature of organic compounds", Draft of 7 October 2004) is also available.[5][6]
Definitions
A preferred IUPAC name or PIN is a name that is preferred among two or more IUPAC names. An IUPAC name is a systematic name that meets the recommended IUPAC rules. IUPAC names include retained names. A general IUPAC name is any IUPAC name that is not a "preferred IUPAC name". A retained name is a traditional or otherwise often used name, usually a trivial name, that may be used in IUPAC nomenclature.[7]
Since systematic names often are not human-readable a PIN may be a retained name. Both "PINs" and "retained names" have to be chosen (and established by IUPAC) explicitly, unlike other IUPAC names, which automatically arise from IUPAC nomenclatural rules. Thus, the PIN is sometimes the retained name (e.g., phenol and acetic acid, instead of benzenol and ethanoic acid), while in other cases, the systematic name was chosen over a very common retained name (e.g., propan-2-one, instead of acetone).
A preselected name is a preferred name chosen among two or more names for parent hydrides or other parent structures that do not contain carbon (inorganic parents). "Preselected names" are used in the nomenclature of organic compounds as the basis for PINs for organic derivatives. They are needed for derivatives of organic compounds that do not contain carbon themselves.[7] A preselected name is not necessarily a PIN in inorganic chemical nomenclature.
Basic principles
The systems of chemical nomenclature developed by the International Union of Pure and Applied Chemistry (IUPAC) have traditionally concentrated on ensuring that chemical names are unambiguous, that is that a name can only refer to one substance. However, a single substance can have more than one acceptable name, like toluene, which may also be correctly named as "methylbenzene" or "phenylmethane". Some alternative names remain available as "retained names" for more general contexts. For example, tetrahydrofuran remains an unambiguous and acceptable name for the common organic solvent, even if the preferred IUPAC name is "oxolane".[8]
Substitutive nomenclature (replacement of hydrogen atoms in the parent structure) is used most extensively, for example "ethoxyethane" instead of diethyl ether and "tetrachloromethane" instead of carbon tetrachloride. Functional class nomenclature (also known as radicofunctional nomenclature) is used for acid anhydrides, esters, acyl halides and pseudohalides and salts. Also skeletal replacement operations, additive and subtractive operations and conjunctive operations are applied.[9]
Retained IUPAC names
The number of retained non-systematic, trivial names of simple organic compounds (for example formic acid and acetic acid) has been reduced considerably for preferred IUPAC names, although a larger set of retained names is available for general nomenclature. The traditional names of simple monosaccharides, α-amino acids and many natural products have been retained as preferred IUPAC names; in these cases the systematic names may be very complicated and virtually never used. The name for water itself is a retained IUPAC name.
Scope of the nomenclature for organic compounds
In IUPAC nomenclature, all compounds containing carbon atoms are considered organic compounds. Organic nomenclature only applies to organic compounds containing elements from the Groups 13 through 17. Organometallic compounds of the Groups 1 through 12 are not covered by organic nomenclature.[7][10]
Notes and references
- ^ Preferred names in the nomenclature of organic compounds, International Union of Pure and Applied Chemistry, retrieved 2017-08-12.
- ^ Nomenclature of Organic Chemistry : IUPAC Recommendations and Preferred Names 2013 (Blue Book). Cambridge: The Royal Society of Chemistry. 2014. doi:10.1039/9781849733069-FP001. ISBN 978-0-85404-182-4.
- ^ Hartshorn, R. M.; Hellwich, K.-H.; Yerin, A.; Damhus, T.; Hutton, A. T. (2015). "Brief Guide to the Nomenclature of Inorganic Chemistry" (PDF). Pure and Applied Chemistry. 87 (9–10): 1039–1049. doi:10.1515/pac-2014-0718. hdl:10092/12053. S2CID 100897636. Retrieved 20 February 2019.
- ^ Favre, Henri A.; Powell, Warren H. (2014). Nomenclature of Organic Chemistry: IUPAC Recommendations and Preferred Names 2013. The Royal Society of Chemistry. doi:10.1039/9781849733069. ISBN 978-1-84973-306-9.
- ^ IUPAC Provisional Recommendations 2004 CONTENTS
- ^ IUPAC Provisional Recommendations 2004 Complete draft version
- ^ a b c IUPAC Provisional Recommendations 2004, par. 10-12, Chapter 1
- ^ IUPAC Provisional Recommendations 2004, Rule P-53.2.2, Chapter5
- ^ IUPAC Provisional Recommendations 2004, P-12.1, Chapter 1
- ^ IUPAC Provisional Recommendations 2004, P-69.0 Organometallic compounds
https://en.wikipedia.org/w/api.php?action=feedcontributions&user=174.250.210.174&feedformat=atom Request a user's GitHub identity GET https://github.com/login/oauth/authorize When your GitHub App specifies a login parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
Parameters Name Type Description client_id string Required. The client ID you received from GitHub when you registered. redirect_uri string The URL in your application where users will be sent after authorization. See details below about redirect urls. login string Suggests a specific account to use for signing in and authorizing the app. scope string A space-delimited list of scopes. If not provided, scope defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with user scope and another token with repo scope, a third web flow that does not provide a scope will receive a token with user and repo scope. state string An unguessable random string. It is used to protect against cross-site request forgery attacks. allow_signup string Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is true. Use false when a policy prohibits signups. 2. Users are redirected back to your site by GitHub If the user accepts your request, GitHub redirects back to your site with a temporary code in a code parameter as well as the state you provided in the previous step in a state parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process.
Exchange this code for an access token:
POST https://github.com/login/oauth/access_token Parameters Name Type Description client_id string Required. The client ID you received from GitHub for your OAuth App. client_secret string Required. The client secret you received from GitHub for your OAuth App. code string Required. The code you received as a response to Step 1. redirect_uri string The URL in your application where users are sent after authorization. Response By default, the response takes the following form:
access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&scope=repo%2Cgist&token_type=bearer You can also receive the response in different formats if you provide the format in the Accept header. For example, Accept: application/json or Accept: application/xml:
Accept: application/json {
"access_token":"gho_16C7e42F292c6912E7710c838347Ae178B4a", "scope":"repo,gist", "token_type":"bearer"
} Accept: application/xml <OAuth>
<token_type>bearer</token_type> <scope>repo,gist</scope> <access_token>gho_16C7e42F292c6912E7710c838347Ae178B4a</access_token>
</OAuth> 3. Use the access token to access the API The access token allows you to make requests to the API on a behalf of a user.
Authorization: Bearer OAUTH-TOKEN GET https://api.github.com/user For example, in curl you can set the Authorization header like this:
curl -H "Authorization: Bearer OAUTH-TOKEN" https://api.github.com/user Device flow Note: The device flow is in public beta and subject to change.
The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "Modifying an OAuth App" for OAuth Apps and "Modifying a GitHub App" for GitHub Apps.
Overview of the device flow Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. The app prompts the user to enter a user verification code at https://github.com/login/device.https://en.m.wikipedia.org/wiki/Category:Wikipedia_administrators_willing_to_handle_RevisionDelete_requests