① 電子商務對外貿公司的影響英文參考文獻
去知網找啊
② 求：英文參考文獻 關於電子商務,外貿,英語對外貿影響等相關的英文文獻.要英文的哦
YanGuoBin .《discussed shallowly new economy accounting personnel》 quality modern accounting" 2009 (2).
LuoHong ZhuKaiXi ．"do not do false account" ecation "with accounting quality accounting friends of 2008(1).
③ 中英文參考文獻，有關電子商務方面，最好和edm有關
EDM是神馬。。。
④ 電子商務參考文獻
1 對話下半場:建立健全電子商務領域金融秩序 電子商務 2007/01
2 攜程電子商務模式組成要素分析 電子商務 2007/01
3 電子商務經營模式給企業帶來了什麼 電子商務 2007/01
4 服務中小企業的第三方電子商務模式研究 電子商務 2007/01
5 電子商務中《消費者權益保護法》適格主體研究 電子商務 2007/01
6 談新就業形勢下的職業院校電子商務專業建設 電子商務 2007/01
7 淺談物資采購的電子商務化 電子科技 2007/01
8 中國電信新一代B2B電子商務網站商集網上線運營 互聯網周刊 2007/02
9 Web數據挖掘在零售業電子商務中的應用 經濟師 2007/01
10 電子商務環境下的稅收 經濟師 2007/01
11 試論電子商務物流隱性成本控制 經濟師 2007/01
12 破除制約我國電子商務發展的四大瓶頸 通信世界 2007/02
13 電子商務代表網站及業務模式分析 通信世界 2007/02
14 組建基於企業服務匯流排的電子商務集成系統研究 計算機應用與軟體 2007/01
15 基於SOAP的即時消息在B2C電子商務系統中的應用 計算機應用與軟體 2007/01
16 電子商務對會計的影響及電子商務會計的發展 會計之友(中) 2007/01
17 電子商務中數據挖掘技術的使用 內蒙古電大學刊 2007/02
18 電子商務專業畢業生就業率低的原因及其對策 內蒙古電大學刊 2007/02
19 淺談煙草行業電子商務 華北、東北地區2007年度煙草學術交流研討會論文集 2007
20 B2C電子商務模式下物流配送路徑優化問題研究 北京交通大學 2007
21 電子商務環境下傳統企業流程變革研究 同濟大學 2007
22 淺析電子商務誠信體系的構建與實現 商場現代化 2007/01
23 基於電子商務的供應鏈管理研究 商場現代化 2007/01
24 電子商務體系結構與電子支付技術 商場現代化 2007/01
25 論新農村建設中農業電子商務的發展戰略 商場現代化 2007/01
26 旅遊電子商務網站的構建 商場現代化 2007/01
27 分銷商網路團購營銷的電子商務模型研究 商場現代化 2007/01
28 電子商務及其安全技術 商場現代化 2007/01
29 淺析電子商務的安全 商場現代化 2007/01
30 Web 2.0技術在電子商務中的應用 商場現代化 2007/01
⑤ 電子商務專業論文之參考文獻謝謝了，大神幫忙啊
[1] 莫佳. 數字簽名在電子商務中的實現[J]. 福建電腦, 2008,(02) . [2] 張述平,楊國明. 第三方支付競爭策略創新[J]. 電腦知識與技術(學術交流), 2006,(17) . [3] 任莉莉. 基於信息不對稱的網上支付風險探討[J]. 池州學院學報, 2008,(01) . [4] 楊國明. 移動支付商業模式分析[J]. 電腦知識與技術(學術交流), 2006,(20) . [5] 吳凌嬌. 網上購物安全問題探討[J]. 江蘇技術師范學院學報, 2006,(04) . [6] 王鳳滿. 數字圖書館與電子商務服務[J]. 閩江學院學報, 2008,(06) . [7] 趙鳳彩,黎超. 航空電子客票的移動支付[J]. 電子商務, 2008,(08) . [8] 徐勇剛,梅耀輝. 淺談我國電子支付系統的應用現狀及發展策略[J]. 當代經理人(中旬刊), 2006,(21) . [9] 宋磊. 電子商務的安全隱患及其防範[J]. 福建行政學院福建經濟管理幹部學院學報, 2008,(02) . [10] 彭銀香,白貞武. 電子商務安全問題及措施研究[J]. 大眾科技, 2005,(11) . [1] 林黎明,李新春. 電子商務安全風險管理研究[J]. 計算機與信息技術, 2006,(03) . [2] 宋苑. 影響電子商務發展的網路安全事件分析與對策[J]. 計算機與信息技術, 2006,(Z1) . [3] 付靈麗,朱輝. 基於電子商務的身份認證攻擊研究[J]. 電腦應用技術, 2007,(02) . [4] 楊二龍,劉建時. 對電子商務風險的幾點思考[J]. 警官文苑, 2007,(01) . [5] 闞曉初. 淺談電子商務安全策略與技術[J]. 商場現代化, 2007,(01) . [6] 楊晉. 現代電子商務安全技術研究[J]. 網路安全技術與應用, 2007,(01) . [7] 朱虹. 電子商務管理發展研究[J]. 高校圖書情報論壇, 2006,(02) . [8] 劉宗梅,李智宇. 電子商務法律環境的構建[J]. 法學與實踐, 2007,(01) . [9] 徐效美,林冬梅. 淺析電子商務的安全[J]. 商場現代化, 2007,(01) . [10] 姚樹琪. 關於我國電子商務物流發展對策的探討[J]. 石家莊聯合技術職業學院學術研究, 2006,(02) .
⑥ 電子商務專業論文之參考文獻
[1] 莫佳. 數字簽名在電子商務中的實現[J]. 福建電腦, 2008,(02) .
[2] 張述平,楊國明. 第三方支付競爭策略創新[J]. 電腦知識與技術(學術交流), 2006,(17) .
[3] 任莉莉. 基於信息不對稱的網上支付風險探討[J]. 池州學院學報, 2008,(01) .
[4] 楊國明. 移動支付商業模式分析[J]. 電腦知識與技術(學術交流), 2006,(20) .
[5] 吳凌嬌. 網上購物安全問題探討[J]. 江蘇技術師范學院學報, 2006,(04) .
[6] 王鳳滿. 數字圖書館與電子商務服務[J]. 閩江學院學報, 2008,(06) .
[7] 趙鳳彩,黎超. 航空電子客票的移動支付[J]. 電子商務, 2008,(08) .
[8] 徐勇剛,梅耀輝. 淺談我國電子支付系統的應用現狀及發展策略[J]. 當代經理人(中旬刊), 2006,(21) .
[9] 宋磊. 電子商務的安全隱患及其防範[J]. 福建行政學院福建經濟管理幹部學院學報, 2008,(02) .
[10] 彭銀香,白貞武. 電子商務安全問題及措施研究[J]. 大眾科技, 2005,(11) .
[1] 林黎明,李新春. 電子商務安全風險管理研究[J]. 計算機與信息技術, 2006,(03) .
[2] 宋苑. 影響電子商務發展的網路安全事件分析與對策[J]. 計算機與信息技術, 2006,(Z1) .
[3] 付靈麗,朱輝. 基於電子商務的身份認證攻擊研究[J]. 電腦應用技術, 2007,(02) .
[4] 楊二龍,劉建時. 對電子商務風險的幾點思考[J]. 警官文苑, 2007,(01) .
[5] 闞曉初. 淺談電子商務安全策略與技術[J]. 商場現代化, 2007,(01) .
[6] 楊晉. 現代電子商務安全技術研究[J]. 網路安全技術與應用, 2007,(01) .
[7] 朱虹. 電子商務管理發展研究[J]. 高校圖書情報論壇, 2006,(02) .
[8] 劉宗梅,李智宇. 電子商務法律環境的構建[J]. 法學與實踐, 2007,(01) .
[9] 徐效美,林冬梅. 淺析電子商務的安全[J]. 商場現代化, 2007,(01) .
[10] 姚樹琪. 關於我國電子商務物流發展對策的探討[J]. 石家莊聯合技術職業學院學術研究, 2006,(02) .
⑦ 求電子商務方面的英文文獻或論文，翻譯成漢字大約3000字。要有明確正規出處
Ecommerce Security Issues
Customer Security: Basic Principles
Most ecommerce merchants leave the mechanics to their hosting company or IT staff, but it helps to understand the basic principles. Any system has to meet four requirements:
privacy: information must be kept from unauthorized parties.
integrity: message must not be altered or tampered with.
authentication: sender and recipient must prove their identities to each other.
non-repudiation: proof is needed that the message was indeed received.
Privacy is handled by encryption. In PKI (public key infrastructure) a message is encrypted by a public key, and decrypted by a private key. The public key is widely distributed, but only the recipient has the private key. For authentication (proving the identity of the sender, since only the sender has the particular key) the encrypted message is encrypted again, but this time with a private key. Such proceres form the basis of RSA (used by banks and governments) and PGP (Pretty Good Privacy, used to encrypt emails).
Unfortunately, PKI is not an efficient way of sending large amounts of information, and is often used only as a first step — to allow two parties to agree upon a key for symmetric secret key encryption. Here sender and recipient use keys that are generated for the particular message by a third body: a key distribution center. The keys are not identical, but each is shared with the key distribution center, which allows the message to be read. Then the symmetric keys are encrypted in the RSA manner, and rules set under various protocols. Naturally, the private keys have to be kept secret, and most security lapses indeed arise here.
:Digital Signatures and Certificates
Digital signatures meet the need for authentication and integrity. To vastly simplify matters (as throughout this page), a plain text message is run through a hash function and so given a value: the message digest. This digest, the hash function and the plain text encrypted with the recipient's public key is sent to the recipient. The recipient decodes the message with their private key, and runs the message through the supplied hash function to that the message digest value remains unchanged (message has not been tampered with). Very often, the message is also timestamped by a third party agency, which provides non-repudiation.
What about authentication? How does a customer know that the website receiving sensitive information is not set up by some other party posing as the e-merchant? They check the digital certificate. This is a digital document issued by the CA (certification authority: Verisign, Thawte, etc.) that uniquely identifies the merchant. Digital certificates are sold for emails, e-merchants and web-servers.
:Secure Socket Layers
Information sent over the Internet commonly uses the set of rules called TCP/IP (Transmission Control Protocol / Internet Protocol). The information is broken into packets, numbered sequentially, and an error control attached. Indivial packets are sent by different routes. TCP/IP reassembles them in order and resubmits any packet showing errors. SSL uses PKI and digital certificates to ensure privacy and authentication. The procere is something like this: the client sends a message to the server, which replies with a digital certificate. Using PKI, server and client negotiate to create session keys, which are symmetrical secret keys specially created for that particular transmission. Once the session keys are agreed, communication continues with these session keys and the digital certificates.
:PCI, SET, Firewalls and Kerberos
Credit card details can be safely sent with SSL, but once stored on the server they are vulnerable to outsiders hacking into the server and accompanying network. A PCI (peripheral component interconnect: hardware) card is often added for protection, therefore, or another approach altogether is adopted: SET (Secure Electronic Transaction). Developed by Visa and Mastercard, SET uses PKI for privacy, and digital certificates to authenticate the three parties: merchant, customer and bank. More importantly, sensitive information is not seen by the merchant, and is not kept on the merchant's server.
Firewalls (software or hardware) protect a server, a network and an indivial PC from attack by viruses and hackers. Equally important is protection from malice or carelessness within the system, and many companies use the Kerberos protocol, which uses symmetric secret key cryptography to restrict access to authorized employees.
Transactions
Sensitive information has to be protected through at least three transactions:
credit card details supplied by the customer, either to the merchant or payment gateway. Handled by the server's SSL and the merchant/server's digital certificates.
credit card details passed to the bank for processing. Handled by the complex security measures of the payment gateway.
order and customer details supplied to the merchant, either directly or from the payment gateway/credit card processing company. Handled by SSL, server security, digital certificates (and payment gateway sometimes).
Practical Consequences
1. The merchant is always responsible for security of the Internet-connected PC where customer details are handled. Virus protection and a firewall are the minimum requirement. To be absolutely safe, store sensitive information and customer details on zip-disks, a physically separate PC or with a commercial file storage service. Always keep multiple back-ups of essential information, and ensure they are stored safely off-site.
2. Where customers order by email, information should be encrypted with PGP or similar software. Or payment should be made by specially encrypted checks and ordering software.
3. Where credit cards are taken online and processed later, it's the merchant's responsibility to check the security of the hosting company's webserver. Use a reputable company and demand detailed replies to your queries.
4. Where credit cards are taken online and processed in real time, four situations arise:
You use a service bureau. Sensitive information is handled entirely by the service bureau, which is responsible for its security. Other customer and order details are your responsibility as in 3. above.
You possess an ecommerce merchant account but use the digital certificate supplied by the hosting company. A cheap option acceptable for smallish transactions with SMEs. Check out the hosting company, and the terms and conditions applying to the digital certificate.
You possess an ecommerce merchant account and obtain your own digital certificate (costing some hundreds of dollars). Check out the hosting company, and enter into a dialogue with the certification authority: they will certainly probe your credentials.
You possess a merchant account, and run the business from your own server. You need trained IT staff to maintain all aspects of security — firewalls, Kerberos, SSL, and a digital certificate for the server (costing thousands or tens of thousands of dollars).
Security is a vexing, costly and complicated business, but a single lapse can be expensive in lost funds, records and reputation. Don't wait for disaster to strike, but stay proactive, employing a security expert where necessary.
Sites on our resources page supplies details.