=================================
「Would」の活用法(総まとめ)
=================================
これまで私が生徒さんから最もよくされた質問の一つが「would」の使い方でしょう。wouldを用いた表現は本当に沢山あり、それら全てを説明するのは容易ではありません。そこで今回、過去の記事でも紹介した用法を含め、日常会話において基本となるwouldの用法を、4つの状況毎になるべく分かりやすくまとめてみました。長くなりますが、どうぞ最後まで読んでみて下さい。
~過去の話をする時~
--------------------------------------------------
1) I thought it would rain.
→「雨が降ると思っていました」
--------------------------------------------------
過去のある時点で、その先に起こることを予め予測や推測をしていたことを示す言い方です。例えば、「I thought it would rain so I brought an umbrella.(雨が降ると思っていたので、傘を持ってきました)」や「Since I was a kid, I knew I would become a teacher.(私は子供の時から先生になると分かっていました)」のように表現できます。
また、「He said he would _____.(彼が〜すると言っていました)」のように誰かが(過去に)言ったことを他の誰かに伝える状況でも使われます。ポイントは、誰かが何かをすると約束したり、何かをすると意思を述べたことを、他の誰かに伝える状況で用いるのが一般的です。例えば、「He said he would buy coffee for us.(彼は私たちにコーヒーを買うと言っていました。)」や「She said she would talk to him about that issue.(その問題について、彼女は彼に話すと言っていました)」という具合に使われます。
✔Wouldの後は動詞の原形がフォロー。
<例文>
When I met my wife 5 years ago, I knew I would marry her one day.
(5年前に妻と出会った当初から、私たちは結婚すると思っていました。)
I never thought this proposal would go through.
(この提案が通らないことは最初から分かっていました。)
She said she would come to the party.
(彼女はパーティーに来ると言っていました。)
--------------------------------------------------
2) She would not help me.
→「彼女は手伝ってくれようとしませんでした」
--------------------------------------------------
Wouldの後にnotを付け、否定文(Would not)にすることで「〜しようとしなかった」という意味になります。基本的に何かしらの依頼や申し出に対し、乗り気じゃない、協力的じゃない、積極的に応える意欲がない、などのニュアンスで断ったことを表します。例えば、親に何度も仕送りをして欲しいと頼んでるが、いっこうにしてくれない状況では「My parents would not send me money.(私の両親は、仕送りをしようとしてくれない)」と言うことができます。
また、人に限らずテレビやパソコン、車などの機能に対してもwould notを使うことができます。例えば、「今朝、車のエンジンがかかりませんでした」は「My car would not start this morning.」となります。
✔肯定文にしても「〜してくれた」とはならず、意味が変わってしまうので注意。「My parents would send me money」と言うと「両親が仕送りをしてくれた」とはならずに、「両親が(何度も)送金した」を意味する。詳しくは下記の3)の解説を参照。
<例文>
I asked him many times but he would not tell me what happened.
(彼に何回も聞きましたが、何が起こったのか教えてくれませんでした。)
My girlfriend is really upset with me. She would not talk to me.
(彼女は私に怒っていて口をきいてくれませんでした。)
I charged my phone but it would not turn on.
(携帯を充電したけど電源が入らなかった。)
--------------------------------------------------
3) In the summer, I would go camping with my friends.
→「夏によく友達とキャンピングに行っていました」
--------------------------------------------------
過去によくやっていた行動パターンや習慣を表す際にもwouldが使われ、used to(よく~したものだ)と似たような役割を果たします。しかし、used toの場合は、習慣となっている行動がより高頻度なもので、且つ“今はもうしていない”ということを強調するニュアンスがあるのに対し、wouldの場合は、習慣となっていた行動頻度が週1回であろうと年1回であろうと、その頻度には関係なく「よく〜した」ということが話の趣旨となります。例えば、「When I was a kid, my grandmother would bake cookies.(子供の頃、私の祖母はよくクッキーを焼いてくれていました)」と言うと、クッキーを作る頻度ではなく、祖母がクッキーを作ってくれていたことが要点になります。それに対し、「私は高校生の頃、毎日サッカーの練習をしていました」と言いたいのであれば、used toを使って、「I used to practice soccer every day in high school.」と言うのが適切です。“毎日練習していた”ことが強調され、且つ“今はもう練習をしていない”ことが相手に伝わります。
✔過去の“状態”を表す場合はwouldではなくused toを使う。例えば「過去にオートバイを持っていました」は「I used to have a motorocycle.」と言い、「I would have a motorcycle」とは言わない。
<例文>
When I lived in Japan, I would go out drinking almost every week.
(日本に住んでいた頃、ほぼ毎週飲みに行っていました。)
Sometimes she would come over and cook Mexican food for us.
(時々、彼女はうちにきてメキシカン料理を作ってくれました。)
During the winter, I would get together with my friends and do a nabe party.
(冬に友達とよく鍋パーティーをしていました。)
~仮定の話をする時~
--------------------------------------------------
1) If I won the lottery I would buy a house.
→「もし宝くじが当たったら家を買います」
架空の話や実際には起こり得ない出来事について話す時にもwouldを使います。一般的に「If _____, I would _____.(〜だったら〜する)」の形式で表現します。例えば、「世界中のどこにでも住めるとしたら、ハワイに住みます」は「If I could live anywhere in the world, I would live in Hawaii.」と言います。
✔文末に「if I knew」に付け足してもOK。
<例文>
If you could date a celebrity, who would it be?
(もし、芸能人と付き合えるとしたら、誰と付き合う?)
I would tell you where she was if I knew.
(彼女がどこにいるか知っていたら教えているよ。)
If I found a hundred dollars on the ground, I would take it to the police station.
(もし100ドルを拾ったら交番に届けます。)
--------------------------------------------------
2) Would you try online dating?
→「あなただったら出会い系サイトを試してみますか?」
--------------------------------------------------
相手に“もしも”の質問を投げかける時は「Would you _____?」と表現するのが定番で「あなただったら〜しますか?」を意味します。相手の意見やアドバイスを尋ねる場合は「What would you _____?」と表現します。例えば、「あなただったらどうしますか?」と聞くなら「What would you do?」、販売員に「あなただったら何をお勧めしますか?」と尋ねるなら「What would you recommend?」となります。
<例文>
Would you date someone older than you?
(あなただったら年上の人とお付き合いしますか?)
What would you do? Would you apologize?
(あなただったらどうしますか?謝りますか?)
Would you be open to living abroad?
(あなただったら外国に住むのはありですか?)
--------------------------------------------------
3) If I were you I would apologize.
→「私だったら謝ります」
--------------------------------------------------
「私だったら〜する」と相手の立場になって何かしらのアドバイスや提案をする場合に使われる表現です。shouldを使った表現よりも控えめに助言したい場合にピッタリの言い回しです。例えば、東京で給料の良い仕事のオファーが入ったが、家族の不幸で地元に引っ越さないといけなくなってしまったと友達に相談され、「私だったら仕事のオファーを断るかな」と言うなら「If I were you I would turn down the offer.」となります。
✔日常会話では「If I were you」を省いて、「I would _____」と直接言うことも一般的。
✔「If I were in your shoes, I would ______.(私があなたの立場だったら、〜をします」という言い方もある。
<例文>
If I were you I wouldn't go.
(私だったら行かないね。)
This milk expired 5 days ago. I wouldn't drink that if I were you.
(この牛乳の消費期限、5日前じゃん。私だったら飲まないよ。)
I would call them and ask for a refund.
(私だったら電話して返金を求めるけど。)
~丁寧・控えめな発言をする時~
--------------------------------------------------
1) Would you turn down the volume?
→「音量を下げてくれますか?」
--------------------------------------------------
人に何かをリクエストや依頼をする際に「Can you _____?(〜してくれる?)」よりも丁寧にお願いする場合は「Would you _____?(〜してくれますか?)」と表現します。例えば、「この用紙に記入してくれますか?」と丁寧に言いたいなら「Would you fill out this form?」になります。
✔より丁寧な言い方が「Would you mind _____?(〜してくれますか?)」。相手に気を使ったとても優しい質問の仕方。
<例文>
Would you close that window?
(あの窓を閉めてもらえますか?)
Would you be able to help?
(手伝っていただけないでしょうか?)
Would you mind changing seats?
(席を変わっていただけませんか?)
--------------------------------------------------
2) Would you like a drink?
→「お飲物はいかがですか?」
--------------------------------------------------
相手に「〜はいかがですか?」と何かを丁寧にオファーする際にピッタリの表現が「Would you like _____?」です。顧客や年上の人、または面識のない人に対して何かオファーする場合は、この表現を使うのが最も無難でしょう。例えば、会社に訪れた顧客に「熱いお茶はいかがですか?」と聞く場合は「Would you like some hot tea?」と言います。
✔友達や家族など、仲の良い人に対してこの表現はちょっと丁寧過ぎる。親しい関係であれば「Do you want _____?」でOK。
<例文>
Would you like a refill?
(飲み物のお代わりはいかがですか?)
Would you like to join us?
(よかったら一緒にどうですか?)
Would you like me to drive?
(私が運転しましょうか?)
--------------------------------------------------
3) I would say _____.
→「〜だと思う」
--------------------------------------------------
この言い方は自分の意見を述べたり何かを推定する時に使われ「〜だと思う」や「恐らく〜だろう」「〜かな」などに相当する表現です。ハッキリと言い切る感じではなく、物腰柔らかく控えめに発言している印象があります。例えば、「彼女、何歳だと思いますか?」と聞かれた際、相手に失礼ないよう謙虚に意見を述べる場合、「I’d say early thirties. Maybe 32.(30代前半だと思う。32歳くらいかな)」という具合に使います。
✔日常会話では「I would say」を「I’d say」と省略して言うことが多い。
✔大抵の場合、「I think」の代わりに「I’d say」が使える。「I think」よりも控えめな響き。
✔必ず答えが求めらるような質問をされた際、決定的な発言や返答を和らげる言い方として「I would have to say _____(〜と言わざるを得ない)」がある。
<例文>
I'd say it's a four to five hour drive.
(車で4時間から5時間くらいかかるかな。)
I'd say this logo looks the best. I like the color and simplicity.
(私はこのロゴが一番だと思います。色とシンプルさがいいと思います。)
Both speeches were excellent but I would have to say Adam's speech was better.
(二人ともスピーチは素晴らしかったですが、私はアダムのスピーチの方が良かったと思います。)
~自分の願望を述べる時~
--------------------------------------------------
1) I would love to go.
→「是非行きたいです」
--------------------------------------------------
「I would love to」は「I want to」と似た意味で「〜を(が)したい」といった強い願望を伝える時に使われれます。「I want to」の気持ちをより強調した言い方です。例えば、同僚に食事を一緒にしないかと誘われた際、「I would love to join you guys for dinner.」と言います。
✔相手の誘いを快く受け入れるときに使われる定番フレーズが「I’d love to!(喜んで!)」
✔その他、相手の誘いを丁寧に断るときに使われる決まり文句でもあり、「I’d love to ____ but _____(〜したいのは山々なのですが、〜)」が定番フレーズになる。
<例文>
I would love to meet with you next week.
(是非、来週お会いしたいと思います。)
I'd love to! What time should I be there?
(喜んで!何時に行けばいいですか?)
I'd love to stay and chat some more but I have to get going.
(残ってもっとお話をしたいのですが、そろそろ行かないといけません。)
--------------------------------------------------
2) I would like to think that ____.
→「〜であると考えたい」
--------------------------------------------------
この表現は「真相はわからないけど、そうであって欲しい・・・」のようなニュアンスとして使われます。例えば、Facebookの個人情報の取り扱いに対し、多少の疑いはあるものの情報はしっかり保護されていると信じたいといった気持ちを表す場合は「I would like to think that Facebook protects our personal information.」となります。また、自分の発言や意見を物腰柔らかく控えめなニュアンスにする役割もあります。例えば、「あなたは良い父親だと思いますか?」という質問に対し「I would like to think I’m a good father.」と答えると、「私は良い父親であると考えたいのですが・・・」といった具合に謙虚な響きになります。
✔日常会話では「I would」を「I'd」と短縮して言うことが多い。
✔「そうだと思いたい」は「I would like to think so.」
<例文>
I would like to think that hard work pays off.
(努力は報われると信じたいです。)
I would like to think professional athletes don't use drugs.
(プロスポーツ選手は、薬物を使用していないと信じたい。)
I would like to think my English is getting better.
(自分の英語力が上達してるって思いたいや〜ん。)
~~~~~~~~~~~~~~~~~~~
無料メルマガ『1日1フレーズ!生英語』配信中!
通勤・通学などのちょとした合間を利用して英語が学べるメルマガ『1日1フレーズ!生英語』を平日の毎朝6時に配信中!ただ単にフレーズを紹介しているだけではなく、音声を使った学習プロセスが組み込まれているので、メルマガを読むこと自体が学習方法!
https://hapaeikaiwa.com/mailmagazine/
~~~~~~~~~~~~~~~~~~~
同時也有1部Youtube影片,追蹤數超過11萬的網紅吉娜英文,也在其Youtube影片中提到,10個loo片語 #02 (第二支影片) https://youtu.be/MY0DbV6ZPeQ look out 小心 look down 向下看 look after 照顧 look around 四處看看 look forward to 期待 **********************...
「start over用法」的推薦目錄:
- 關於start over用法 在 Hapa Eikaiwa Facebook 的精選貼文
- 關於start over用法 在 Hapa Eikaiwa Facebook 的最佳貼文
- 關於start over用法 在 Eric's English Lounge Facebook 的最佳解答
- 關於start over用法 在 吉娜英文 Youtube 的最佳解答
- 關於start over用法 在 曼蒂英文- 你是喜新厭舊的人嗎?還是其實東西都捨不得換 ... 的評價
- 關於start over用法 在 Driver4vr github 的評價
- 關於start over用法 在 YouTube Data API Overview - Google for Developers 的評價
start over用法 在 Hapa Eikaiwa Facebook 的最佳貼文
=================================
「最初からやり直し」や「一から出直し」は英語で?
=================================
日常会話では、「もう一度やり直す」ことを英語で「Start over」と表現するのが一般的ですが、ビジネスシーンでは、ビジネスシーンならではの独特な表現があるのはご存知ですか?今回は、よく耳にする2つのイディオムをご紹介しようと思います。
--------------------------------------------------
1) Back to square one
→「一からやり直し / 振り出しに戻る / 一から出直す」
--------------------------------------------------
この表現は、ある程度進んでいた企画やプロジェクトが駄目になったり中止になったときに、振り出しに戻って最初からやり直す意味として、特にビジネスシーンでよく使われるイディオムです。「Square one」は、人生ゲームなどのボードゲームの最初のマス(Square)のことを指しています。まさにゲームの「振り出しに戻る」と同じように、出発点に戻って出直すことを表す状況で使われます。
✔「Go back to square one」または「Be back to square one」の組み合わせが一般的。
<例文>
We're back to square one.
(一からやり直しです。)
We have to go back to square one.
(振り出しに戻って、最初からやり直さないといけません。)
It's not working. Let's go back to square one.
(上手くいっていないので、一からやり直しましょう。)
〜会話例〜
A: The plan fell through.
(計画が不成立に終わりました。)
B: It looks like we have to go back to square one.
(振り出しに戻って、一からやり直すしかないですね。)
--------------------------------------------------
2) Back to the drawing board
→「最初からやり直す」
--------------------------------------------------
意味と用法は上記の「back to square one」と全く同じです。「Drawing board」は、ミーティングや会議などで使われるホワイトボードのことを指しおり、失敗した企画やプロジェクトを、一旦ホワイトボードに戻って、もう一度アイデアや計画を練り直すニュアンスになります。
✔「Go back to the drawing board」または「Get back to the drawing board」の組み合わせが一般的。
<例文>
Let's go back to the drawing board.
(最初からやり直しましょう。)
〜会話例〜
A: Our offer got rejected.
(我々のオファーは却下されました。)
B: Let's get back to the drawing board.
(一からやり直しましょうか。)
~~~~~~~~~~~~~~~~~~~
無料メルマガ『1日1フレーズ!生英語』配信中!
通勤・通学などのちょとした合間を利用して英語が学べるメルマガ『1日1フレーズ!生英語』を平日の毎朝6時に配信中!ただ単にフレーズを紹介しているだけではなく、音声を使った学習プロセスが組み込まれているので、メルマガを読むこと自体が学習方法!
https://hapaeikaiwa.com/mailmagazine/
~~~~~~~~~~~~~~~~~~~
start over用法 在 Eric's English Lounge Facebook 的最佳解答
[專頁公告] 英文學習「 生態系」
Hello, everyone! I hope you had a great start on the new year. I’ve been radio silent (銷聲匿跡) for a few days because I am currently setting up my Instagram to provide more English learning materials for you guys. Remember my new year goal of providing an "ecosystem" of learning materials?
大家好!希望各位在新年都有一個新的開始。近來我有些 「電波靜默」(銷聲匿跡),是因為我目前正在設置我的IG以提供給各位更多免費的教育資源。還記得我要提供學習資源生態圈的新年目標嗎?
以下是我們目前的資源:
★★★★★★★★★★★★
Fanpage 📣📣📣
專頁: https://www.facebook.com/ericsenglishlounge
On our main fan page, you can read about hot topic current events, editorials, posts on English education. We also provide free educational resources, hold book drawings, and perform charitable activities.
在我們主要的粉絲專頁中,你可以閱讀引起共鳴的熱門時事、社論與英文教育類文章。我們還提供免費的教育資源、贈書抽獎以及舉辦一些慈善活動。
專頁宗旨與目標: https://bit.ly/2BaENzJ
★★★★★★★★★★★★
FB groups and Google Meet 📣📣📣
關鍵思考英文學習團+Google Meet 時事討論
https://www.facebook.com/groups/ericsenglishlounge
In our critical thinking FB group, you can read in depth news stories and discuss these issues with me. We have periodic livestreams on news topics, providing analysis and discussions available to public think tanks. In our class groups, you'll get constant updates and extra information relating to our courses! Google meet is where we hold our live discussions.
在我們的關鍵思考學習社團,你可以更深入地閱讀新聞報導後和我討論相關議題。我們會有定期直播討論相關新聞主題,並提供從公開智庫找到的分析和討論。在我們的班群社團,你可以得到即時更新,並獲得與我們課程有關的資訊!Google Meet是我們舉行線上討論的地方。
★★★★★★★★★★★★
YouTube and Blog 📣📣📣
YouTube: http://bit.ly/2MhEt7h
部落格: http://bit.ly/2Ybp8L8
To be honest, I haven’t updated YouTube for awhile because of the high cost of producing a video (both money and time). However, you can still check out the channel for English learning videos, and I will update it whenever I can.
Our blog, which gets about 2000 visitors a day, is a compilation of all the free resources I published on all media. Thus, if you do not want to get on FB, feel free to check it out.
說實在的,因為做一部影片要成本過高,我已經一陣子沒有更新YouTube。 但是你還是能夠在頻道上觀看英文學習影片,如果有值得我們關注的議題就會有所更新。
我們的部落格每天有大約2000人來訪,匯集了所有我網路上免費資源;所以如果你不想上臉書,歡迎使用我們的部落格。
★★★★★★★★★★★★
Instagram 📣📣📣
IG: https://www.instagram.com/esenglishlounge/
I started working on Instagram a few months ago and so far I have three types of posts:
我幾個月前也開始投入IG!目前有三種貼文:
1. Word of the Day: I go over the pronunciation, collocations and provide example sentences. All these words are high frequency tier-2, cross-domain vocabulary words that appear in both academic texts and the news.
每日單字:我會針對發音、搭配詞、單字用法進行說明。所有的單字都來自高頻Tier 2跨領域學術詞彙,你會常在學術文章和新聞看到它們。
2. News English: I publish abridged, translated, and audio versions of news stories found in the NY Times, Reuters, the Guardian, and so on. These take a bit of time to do, so please use these resources as a part of your learning.
時事英文:我會發布來自紐約時報、路透社、衛報等網站的新聞,並且花了不少時間提供三合一服務(新聞摘要、翻譯、有聲版)。言下之意就是多使用這些資源吧!
3. Daily life English topics: Anything that I find interesting or useful to students
生活英文主題:只要是有趣或是實用的資訊都會出現~
So, if you need any of these resources, feel free to follow. Everything is free and I will do my best to keep it that way. Do follow me on Instagram if you need News English and want to expand your vocabulary!
如果你需要任何上述的資源,歡迎關注。我會盡力維持全部免費,如果你想要讀英文新聞並且增加單字量,追蹤我的IG吧!
📣 https://www.instagram.com/esenglishlounge/ 📣
★★★★★★★★★★★★
還有需要其他的資源可以在這邊找到:
英文學習資源大全: https://bit.ly/35HMkBy
找不到的話也歡迎來信詢問~
★★★★★★★★★★★★
Onwards to the new year!
邁向新的一年!
start over用法 在 吉娜英文 Youtube 的最佳解答
10個loo片語 #02 (第二支影片)
https://youtu.be/MY0DbV6ZPeQ
look out 小心
look down 向下看
look after 照顧
look around 四處看看
look forward to 期待
**************************
我的新頻道:歡迎加入
學習單字發音與用法,實用例句,延伸句,情境句
Say and learn words with Gina
https://www.youtube.com/channel/UCuzfZrVItqnsuYZlW5ubdtQ
加入吉娜英文FB 粉絲頁
學習更多道地美式口語英文
https://www.facebook.com/wordsgo/
**********************
吉娜提供教學服務:
KK音標課程
基礎英文從頭學起
學好英文諮詢
請寫信到
webmaster@wordsgo.com
**************************
look at 看著;查看
A: Look at that giraffe! It’s huge!
B: Yes, they can grow to be over sixteen feet tall.
A: 你看那隻長頸鹿。它好巨大。
B: 是啊,它們會長到超過十六英呎高。
A: What are you looking at?
B: Do you see those strange lights?
A: Yes, that’s an airplane!
你在看什麼?
你有看到那些奇怪的燈嗎?
是的,那是一架飛機。
I’m looking at running shoes right now. I’m going to buy a pair.
我現在正在看跑步鞋。我要買一雙。
A: Did you get the doctor to look at your knee?
B: Yes, I did. He said I have a muscle problem.
你有找醫生查看你的膝蓋了嗎?
是的,我有。他說我有肌肉的問題。
look for 尋找
A: What are you looking for?
B: I’m trying to find the library. Do you know where it is?
A: Yes, it’s on the next block.
A: 你正在找什麼?
B: 我正試著找圖書館。你知道在哪裡嗎?
A: 是的,它在下一個街區。
Jerry is looking for a job.
He’s been out of work for three months.
傑瑞正在找工作。他已經失業三個月了。
look into 調查;研究
The police are looking into her disappearance. They are talking to all her family, friends, and coworkers to find out what happened. (調查)
警方正在調查她失蹤的案子。他們找她的家人,朋友,和同事都談過,想要知道發生了甚麼事情。
I’m starting to do some gardening. I’m looking into the easiest plants to grow here.
我開始接觸園藝。我正在研究最容易在這裡種植的植物。
She’s looking into traveling to Korea. She wants to know the flight and hotel prices.
她正在研究到韓國玩的資料。她想要知道飛機和旅館的價錢。
look up 向上看;查找;景仰
Look up! There are some very pretty clouds in the sky.
看上面!天空有一些相當漂亮的雲。
I wanted to know how to make mashed potatoes, so I looked it up on Google.
我想要知道如何做馬鈴薯泥,所以我就查了Google。
A: I don’t know this word.
B: Here, look it up in the dictionary.
A: Ah! There it is!
A: 我不知道這個單字。
B: 這裡,查字典。
A: 啊!在這裡。
Doris looks up to her big brother. He is her hero.
桃樂絲崇拜她的哥哥。他是他的英雄。
look over 快速看過;簡略檢查
I looked over the book’s jacket and decided it would be interesting to read.
我看了看這本書,我認為應該是閱讀起來會很有趣。
A: I looked over your proposal, and I like your idea.
B: Really? Thank you.
A. I want you to start working on it right away.
我看了一下你的計畫書,我喜歡你的點子。
真的嗎?謝謝你。
我想要你馬上開始執行這個計畫。
He looked over my paper and corrected my spelling errors.
他看了我的報告,並且修正了我的拼字錯誤。
I asked her to look over my essay before I gave it to my teacher.
在我把作文交給老師之前,我請她幫忙看一下。
start over用法 在 Driver4vr github 的推薦與評價
Driver4Vr Free Gold Account Gold has actually been utilized as a kind of currency or shop of value since human civilization initial started over 4000 years ... ... <看更多>
start over用法 在 YouTube Data API Overview - Google for Developers 的推薦與評價
Introduction
This document is intended for developers who want to write applications that interact with YouTube. It explains basic concepts of YouTube and of the API itself. It also provides an overview of the different functions that the API supports.
Before you startYou need a Google Account to access the Google API Console, request an API key, and register your application.
Create a project in the Google Developers Console and obtain authorization credentials so your application can submit API requests.
After creating your project, make sure the YouTube Data API is one of the services that your application is registered to use:
Go to the API Console and select the project that you just registered.
Visit the Enabled APIs page.
In the list of APIs, make sure the status is ON for the YouTube Data API v3.
If your application will use any API methods that require user authorization, read the authentication guide to learn how to implement OAuth 2.0 authorization.
Select a client library to simplify your API implementation.
Familiarize yourself with the core concepts of the JSON (JavaScript Object Notation) data format. JSON is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see json.org.
Resources and resource types
A resource is an individual data entity with a unique identifier. The table below describes the different types of resources that you can interact with using the API.
Resources
activity
Contains information about an action that a particular user has taken on the YouTube site. User actions that are reported in activity feeds include rating a video, sharing a video, marking a video as a favorite, and posting a channel bulletin, among others.
channel
Contains information about a single YouTube channel.
channelBanner
Identifies the URL to use to set a newly uploaded image as the banner image for a channel.
channelSection
Contains information about a set of videos that a channel has chosen to feature. For example, a section could feature a channel's latest uploads, most popular uploads, or videos from one or more playlists.
guideCategory
Identifies a category that YouTube associates with channels based on their content or other indicators, such as popularity. Guide categories seek to organize channels in a way that makes it easier for YouTube users to find the content they're looking for. While channels could be associated with one or more guide categories, they are not guaranteed to be in any guide categories.
i18nLanguage
Identifies an application language that the YouTube website supports. The application language can also be referred to as a UI language.
i18nRegion
Identifies a geographic area that a YouTube user can select as the preferred content region. The content region can also be referred to as a content locale.
playlist
Represents a single YouTube playlist. A playlist is a collection of videos that can be viewed sequentially and shared with other users.
playlistItem
Identifies a resource, such as a video, that is part of a playlist. The playlistItem resource also contains details that explain how the included resource is used in the playlist.
search result
Contains information about a YouTube video, channel, or playlist that matches the search parameters specified in an API request. While a search result points to a uniquely identifiable resource, like a video, it does not have its own persistent data.
subscription
Contains information about a YouTube user subscription. A subscription notifies a user when new videos are added to a channel or when another user takes one of several actions on YouTube, such as uploading a video, rating a video, or commenting on a video.
thumbnail
Identifies thumbnail images associated with a resource.
video
Represents a single YouTube video.
videoCategory
Identifies a category that has been or could be associated with uploaded videos.
watermark
Identifies an image that displays during playbacks of a specified channel's videos. The channel owner can also specify a target channel to which the image links as well as timing details that determine when the watermark appears during video playbacks and then length of time it is visible.
Note that, in many cases, a resource contains references to other resources. For example, a playlistItem
resource's snippet.resourceId.videoId
property identifies a video resource that, in turn, contains complete information about the video. As another example, a search result contains either a videoId
, playlistId
, or channelId
property that identifies a particular video, playlist, or channel resource.
The following table shows the most common methods that the API supports. Some resources also support other methods that perform functions more specific to those resources. For example, the videos.rate
method associates a user rating with a video, and the thumbnails.set
method uploads a video thumbnail image to YouTube and associates it with a video.
Operations
list
Retrieves (
GET
) a list of zero or more resources.insert
Creates (
POST
) a new resource.update
Modifies (
PUT
) an existing resource to reflect data in your request.delete
Removes (
DELETE
) a specific resource.The API currently supports methods to list each of the supported resource types, and it supports write operations for many resources as well.
The table below identifies the operations that are supported for different types of resources. Operations that insert, update, or delete resources always require user authorization. In some cases, list
methods support both authorized and unauthorized requests, where unauthorized requests only retrieve public data while authorized requests can also retrieve information about or private to the currently authenticated user.
Supported Operations
list
insert
update
delete
activity
caption
channel
channelBanner
channelSection
comment
commentThread
guideCategory
i18nLanguage
i18nRegion
playlist
playlistItem
search result
subscription
thumbnail
video
videoCategory
watermark
Quota usage
The YouTube Data API uses a quota to ensure that developers use the service as intended and do not create applications that unfairly reduce service quality or limit access for others. All API requests, including invalid requests, incur at least a one-point quota cost. You can find the quota available to your application in the API Console.
Projects that enable the YouTube Data API have a default quota allocation of 10,000 units per day, an amount sufficient for the overwhelming majority of our API users. Default quota, which is subject to change, helps us optimize quota allocations and scale our infrastructure in a way that is more meaningful to our API users. You can see your quota usage on the Quotas page in the API Console.
Note: If you reach the quota limit, you can request additional quota by
completing the Quota extension
request form for YouTube API Services.
Google calculates your quota usage by assigning a cost to each request. Different types of
operations have different quota costs. For example:
A read operation that retrieves a list of resources -- channels, videos, playlists -- usually
costs 1 unit.
A write operation that creates, updates, or deletes a resource usually has costs
50
units.A search request costs
100
units.A video upload costs
1600
units.The Quota costs for API requests table shows the
quota cost of each API method. With these rules in mind, you can estimate the number of requests
that your application could send per day without exceeding your quota.
The API allows, and actually requires, the retrieval of partial resources so that applications avoid transferring, parsing, and storing unneeded data. This approach also ensures that the API uses network, CPU, and memory resources more efficiently.
The API supports two request parameters, which are explained in the following sections, that enable you to identify the resource properties that should be included in API responses.
The part
parameter identifies groups of properties that should be returned for a resource.
The fields
parameter filters the API response to only return specific properties within the requested resource parts.
part
parameterThe part
parameter is a required parameter for any API request that retrieves or returns a resource. The parameter identifies one or more top-level (non-nested) resource properties that should be included in an API response. For example, a video
resource has the following parts:
snippet
contentDetails
fileDetails
player
processingDetails
recordingDetails
statistics
status
suggestions
topicDetails
All of these parts are objects that contain nested properties, and you can think of these objects as groups of metadata fields that the API server might (or might not) retrieve. As such, the part
parameter requires you to select the resource components that your application actually uses. This requirement serves two key purposes:
It reduces latency by preventing the API server from spending time retrieving metadata fields that your application doesn't use.
It reduces bandwidth usage by reducing (or eliminating) the amount of unnecessary data that your application might retrieve.
Over time, as resources add more parts, these benefits will only increase since your application will not be requesting newly introduced properties that it doesn't support.
How to use thefields
parameterThe fields
parameter filters the API response, which only contains the resource parts identified in the part
parameter value, so that the response only includes a specific set of fields. The fields
parameter lets you remove nested properties from an API response and thereby further reduce your bandwidth usage. (The part
parameter cannot be used to filter nested properties from a response.)
The following rules explain the supported syntax for the fields
parameter value, which is loosely based on XPath syntax:
Use a comma-separated list (fields=a,b
) to select multiple fields.
Use an asterisk (fields=*
) as a wildcard to identify all fields.
Use parentheses (fields=a(b,c)
) to specify a group of nested properties that will be included in the API response.
Use a forward slash (fields=a/b
) to identify a nested property.
In practice, these rules often allow several different fields
parameter values to retrieve the same API response. For example, if you want to retrieve the playlist item ID, title, and position for every item in a playlist, you could use any of the following values:
fields=items/id,playlistItems/snippet/title,playlistItems/snippet/position
fields=items(id,snippet/title,snippet/position)
fields=items(id,snippet(title,position))
Note: As with all query parameter values, the fields
parameter value must be URL encoded. For better readability, the examples in this document omit the encoding.
The examples below demonstrate how you can use the part
and fields
parameters to ensure that API responses only include the data that your application uses:
Example 1 returns a video resource that includes four parts as well as
kind
and etag
properties.Example 2 returns a video resource that includes two parts as well as
kind
and etag
properties.Example 3 returns a video resource that includes two parts but excludes
kind
and etag
properties.Example 4 returns a video resource that includes two parts but excludes
kind
and etag
as well as some nested properties in the resource's snippet
object.Example 1
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,contentDetails,statistics,statusDescription: This example retrieves avideo
resource and identifies several
resource parts that should be included in the API response.API response:
{
"kind": "youtube#videoListResponse",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/sDAlsG9NGKfr6v5AlPZKSEZdtqA\"",
"videos": [
{
"id": "7lCDEYXw3mM",
"kind": "youtube#video",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/iYynQR8AtacsFUwWmrVaw4Smb_Q\"",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"contentDetails": {
"duration": "PT15M51S",
"aspectRatio": "RATIO_16_9"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
},
"status": {
"uploadStatus": "STATUS_PROCESSED",
"privacyStatus": "PRIVACY_PUBLIC"
}
}
]
}
Example 2
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,statisticsDescription: This example modifies thepart
parameter value so that the
contentDetails
andstatus
properties are not included
in the response.API response:
{
"kind": "youtube#videoListResponse",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/sDAlsG9NGKfr6v5AlPZKSEZdtqA\"",
"videos": [
{
"id": "7lCDEYXw3mM",
"kind": "youtube#video",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/iYynQR8AtacsFUwWmrVaw4Smb_Q\"",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Example 3
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,statistics&fields=items(id,snippet,statistics)Description: This example adds thefields
parameter to remove all
kind
andetag
properties from the API response.API response:
{
"videos": [
{
"id": "7lCDEYXw3mM",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Example 4
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&fields=items(id,snippet(channelId,title,categoryId),statistics)&part=snippet,statisticsDescription: This example modifies thefields
parameter from example 3
so that in the API response, each video resource'ssnippet
object only includes thechannelId
,title
,
andcategoryId
properties.API response:
{
"videos": [
{
"id": "7lCDEYXw3mM",
"snippet": {
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Optimizing performance
Using ETags
ETags, a standard part of the HTTP protocol, allow applications to refer to a specific version of a particular API resource. The resource could be an entire feed or an item in that feed. This functionality supports the following use cases:
Caching and conditional retrieval – Your application can cache API resources and their ETags. Then, when your application requests a stored resource again, it specifies the ETag associated with that resource. If the resource has changed, the API returns the modified resource and the ETag associated with that version of the resource. If the resource has not changed, the API returns an HTTP 304 response (Not Modified
), which indicates that the resource has not changed. Your application can reduce latency and bandwidth usage by serving cached resources in this manner.
The client libraries for Google APIs differ in their support of ETags. For example, the JavaScript client library supports ETags via a whitelist for allowed request headers that includes If-Match
and If-None-Match
. The whitelist allows normal browser caching to occur so that if a resource's ETag has not changed, the resource can be served from the browser cache. The Obj-C client, on the other hand, does not support ETags.
Protecting against inadvertent overwrites of changes – ETags help to ensure that multiple API clients don't inadvertently overwrite each other's changes. When updating or deleting a resource, your application can specify the resource's ETag. If the ETag doesn't match the most recent version of that resource, then the API request fails.
Using ETags in your application provides several benefits:
The API responds more quickly to requests for cached but unchanged resources, yielding lower latency and lower bandwidth usage.Your application will not inadvertently overwrite changes to a resource that were made from another API client.
The Google APIs Client Library for JavaScript supports If-Match
and If-None-Match
HTTP request headers, thereby enabling ETags to work within the context of normal browser caching.
Using gzip
You can also reduce the bandwidth needed for each API response by enabling gzip compression. While your application will need additional CPU time to uncompress API responses, the benefit of consuming fewer network resources usually outweighs that cost.
To receive a gzip-encoded response you must do two things:
Set the Accept-Encoding
HTTP request header to gzip
.
Modify your user agent to contain the string gzip
.
The sample HTTP headers below demonstrate these requirements for enabling gzip compression:
Accept-Encoding: gzip
User-Agent: my program (gzip)
... <看更多>
start over用法 在 曼蒂英文- 你是喜新厭舊的人嗎?還是其實東西都捨不得換 ... 的推薦與評價
再多加碼兩個跟turn有關的用法 turn over a new leaf 翻開新的一頁;改過自 ... ⚡️If you cannot think of a reason to continue, it's time to start over. ... <看更多>