This is W3C's home page for HTML. Here you will find pointers to our specifications for HTML@` guidelines on how to use HTML to the best effect@` and pointers to related work at W3C. When W3C decides to become involved in an area of Web technology or policy@` it initiates an activity in that area. HTML is one of many Activities currently being pursued. You can learn more about the HTML activity from the HTML Activity Statement.
ここは W3C の HTML の ホームページ だよ。 ここでは、次のようなことについて、ヒントを 書いているよ。 例えば、僕たちがやっている HTML についての詳しい説明とか、HTML を サイコーに使いこなすための ガイドライン とか、それから、W3C のいろんな活動について 書いているよ。 W3C がなんらかの Web テクノロジー とか、 Web の ポリシー について、積極的に かかわっていくべきだ、と決断したら、 そこから、だんだん話しが進んでいくんだ。 HTML っていうのは、今いろいろ取り組んでいる 仕事のうちの一つなんだ。 もっと詳しい情報を知りたいキミは、 HTML 活動宣言を読んでね。続きが読みたい人は、 「続きの訳をキボーン」 とカキコしてください。 要望が少ない場合は自滅します。
NEWS 8 November 2000: Updated HTML Working Group Roadmap is available now. This describes the timeline for deliverables of the HTML Working Group. It used to be a W3C NOTE but has now been moved to the MarkUp area for easier maintenance@` and it will be updated more frequently.
3 November 2000: W3C is pleased to announce advancement of XHTML Basic to Proposed Recommendation. XHTML Basic provides an extensible XHTML document type that is rich enough for simple content authoring that can be shared across devices from desktop computers to TVs@` PDAs@` pagers@` and mobile phones. Please send comments to the addresses given in the Status of this Document section by 3 December.
21 October 2000: W3C is pleased to announce that Modularization of XHTML has become a Candidate Recommendation. This period is a call for implementation@` testimonials@` and review by W3C Members and the public@` and lasts through 17 November. The specification subsets XHTML and extends XHTML's reach onto emerging platforms like mobile devices@` television@` and appliances.
28 August 2000: The second draft for the XHTML Events spec.
This specification defines the XHTML Event Module@` a module that provides XHTML host languages with the ability to uniformly integrate behaviors with Document Object Model (DOM) Level 2 event interfaces.
This specification also defines the XHTML Basic Event Module@` a module which subsets the XHTML Event Module for simpler applications and simpler client devices@` and the XHTML Event Types Module@` a module defining XHTML language event types.
2000年8月28日: XHTML の イベント の詳しい内容について、 2番目の試案ができたよ。
この説明書では、次のようなことについて述べているよ。
まず、XHTML のイベントモジュールについて。
このモジュールを使うと、XHTML のホスト言語たちに、 次の能力を与えることができる。
具体的には、Document Object Model (DOM) Level 2 event interfaces. というものを使って、 ふるまいをみんな同じようにに統合できるようになるんだ。
HTML is the lingua franca for publishing hypertext on the World Wide Web.
It is a non-proprietary format based upon SGML@` and can be created and processed by a wide range of tools@` from simple plain text editors - you type it in from scratch- to sophisticated WYSIWYG authoring tools.
HTML uses tags such as <h1> and </h1> to structure text into headings@` paragraphs@` lists@` hypertext links etc.
Here is a 10-minute guide for newcomers to HTML.
W3C's statement of direction for HTML is given on the HTML Activity Page.
See also the page on our work on the next generation of Web forms@` and the section on Web history.
To develop the next generation of HTML as a suite of XML tag sets with a clean migration path from HTML 4.0.
Some of the expected benefits include: reduced authoring costs@` an improved match to database & workflow applications@` a modular solution to the increasingly disparate capabilities of browsers@` and the ability to cleanly integrate HTML with other XML applications. For further information@` see the Charter for the HTML Working Group.
Myth one Myth: "A normal link is an incitement to copy the linked document in a way which infringes copyright". This is a serious misunderstanding. The ability to refer to a document (or a person or any thing else) is in general a fundamental right of free speech to the same extent that speech is free. Making the reference with a hypertext link is more efficient but changes nothing else.
When the "speech" itself is illegal@` whether or not it contains hypertext links@` then its illegality should not be affected by the fact that it is in electronic form. ハイパリンクを含むと含まざるとにかかわらず「言論」そのものが違法であるとき,その違法性は,それが電気的であるかどうかに関係ありません。
Users and information providers and lawyers have to share this convention. If they do not@` people will be frightened to make links for fear of legal implications. I received a mail message asking for "permission" to link to our site. I refused as I insisted that permission was not needed. ユーザと情報発信者と法律家は,この慣行を共有しなければなりません。さもなくば,人々は,リンクを張るとき,「違法なのではないのだろうか」と恐れてしまいます。私は,私たちへのサイトへのリンクの「許可」を求めるメールをもらったことがあります。私はこのメールを断りました。私は「許可は不要だ」と主張しているからです。
There is no reason to have to ask before making a link to another site 他のサイトにリンクを張るとき,その前に許可を取らなければならない理由はありません。
But by the same token@` You are responsible for what you say about other people@` and their sites@` etc.@` on the web as anywhere しかし,あなたが,他の人やそのサイト等々について発言をするときは,あなたは責任を持たなければなりません。
Myth Two Myth: Making a link to a document makes your document more valuable and therefore is a right you should pay". 迷信その2 迷信: 「他の文書にリンクを張ることは,あなたの文書を価値あるものにするので,従ってあなたはそれに対して対価を支払わなければならない」
This is another dangerous one. It is of course true that your document is made more valuable by links to high quality relevant other documents. A review in a consumer magazine has added value because of the quality of the products to which it refers the reader. I may be more valuable to you as a person if I refer you to other people by name@` phone number or URL. This doesn't mean I owe those people something. これも危険な誤解です。他の適切な文書にリンクを張ることにより,あなたの文書に価値が出ることはもちろん事実です。消費者雑誌のレビューは,読者のがそれを買うように,製品に価値を与えます。もし,私が名前や電話番号やURLによってあなたを他の人に紹介したら,私はあなたにとってより価値のある人間になるかもしれません。(しかし,)これは,あなたを紹介した人たちに私が何か借りをつくったということを意味しません。
We cannot regard anyone as having the "right not to be referred to" without completely pulling the rug out from under free speech. 私たちが「紹介されない権利」を主張する人を尊重することしたら,それは言論の自由を完全に否定することと同じです。
W3C produces what are known as "Recommendations" for HTML. These are specifications@` developed by W3C working groups@` and then voted in by Members of the Consortium. A W3C Recommendation indicates that consensus has been reached among the Consortium Members that a specification is appropriate for widespread use. XHTML 1.0 が今のところ、W3C のオスス メだな
XHTML 1.0 is W3C's recommendation for the latest version of HTML@` following on from earlier work on HTML 4.01@` HTML 4.0@` HTML 3.2 and HTML 2.0. With a wealth of features@` XHTML 1.0 is a reformulation of HTML 4.01 in XML@` and combines the strength of HTML4 with the power of XML.
XHTML 1.0 は W3C のオススメだ。でもって、これは、 HTML のもっとも新しいバージョンでもある。 過去を振り返れば、こ の前に HTML 4.01 があって、その前に HTML 4.0 があって、 その前に HTML 3.2 があって、さらにその前に HTML 2.0 が あったとゆーわけさ。いろんな機能がテンコモリだからさ、 XHTML 1.0 つーのは HTML 4.01 を XML の考え方で作り直 したものだし、HTML4 の強さと XML のパワーを合体させた ものなんだ。
XHTML 1.0 is specified in three "flavors". You specify which of these variants you are using by inserting a line at the beginning of the document. For example@` the HTML for this document starts with a line which says that is it using XHTML Transitional. Thus@` if you want to validate the document@` the tool used knows which variant you are using. Each variant has its own DTD - Document Type Definition - which sets out the rules and regulations for using HTML in a succinct and definitive manner. XHTML の3つの味付け
XHTML Transitional - Most people writing Web pages for the general public to access will want to use this flavor of HTML 4. The idea is to take advantage of XHTML features including style sheets but nonetheless to make small adjustments to your mark-up for the benefit of those viewing your pages with older browsers which can't understand style sheets. These include using BODY with bgcolor@` text and link attributes.
XHTML 移行バージョン - 一般の人達がアクセスする ことを想定してWebページズを書いている人達のうちほ とんどは、この HTML 4 の味付けを使いたがると思う よ。この考え方ちゅーのはさー。XHTML の良いところ だけ使っちゃってさ。例えば、スタイルシートとかさ。そ れでいて、いろんなマークアップも少しはいじりたい、っ てゆーわがままな要求に答えられるわけよ。なんでそ ーゆーことが必要か、つーと、いまだにスタイルシート を知らない古いブラウザーを使ってうちらのページを見 に来る人がいるわけじゃん。 こーしとくとさ、bgcolor や text や link attributes を BODY で使えるよーになるの さ。
XHTML Strict - Use this when you want really clean structural mark-up@` free of any tags associated with layout. Use this together with W3C's Cascading Style Sheet language (CSS) to get the font@` color@` and layout effects you want.
The complete XHTML 1.0 specification is available in English in several formats@` including HTML@` plain text Postscript@` and PDF. See also the list of translations produced by volunteers.
XHTML 1.0 is the first major change to HTML since HTML 4.0 was released in 1997. It brings the rigor of XML to Web pages and is the keystone in W3C's work to create standards that provide richer Web pages on an ever increasing range of browser platforms including cell phones@` televisions@` cars@` wallet sized wireless communicators@` kiosks@` and desktops.
XHTML is modular making it easy to combine with markup tags for things like vector graphics@` multimedia@` math@` electronic commerce and more. Content providers will find it easier to produce content for a wide range of platforms@` with better assurances as to how the content is rendered.
The modular design reflects the realization that a one-size-fits-all approach will no longer work in a world where browsers vary enormously in their capabilities. A browser in a cellphone can't offer the same experience as a top of the range multimedia desktop machine. The cellphone doesn't even have the memory to load the page designed for the desktop browser.
XHTML 1.0 is the first step and the HTML working group is busy on the next. XHTML 1.0 reformulates HTML as an XML application. This makes it easier to process and easier to maintain. XHTML 1.0 borrows the tags from W3C's earlier work on HTML 4@` and can be interpreted by existing browsers@` by following a few simple guidelines. This allows you to start using XHTML now!
You can roll over your old HTML documents into XHTML using W3C's Open Source HTML Tidy utility. This tool also cleans up markup errors@` removes clutter and prettifies the markup making it easier to maintain.
HTML 4.01 is a revision of the HTML 4.0 Recommendation first released on 18th December 1997. The revision fixes minor errors that have been found since then. The XHTML 1.0 spec relies on HTML 4.01 for the meanings of HTML tags. This allowed us to reduce the size of the XHTML 1.0 spec very considerably.
The first step was to reformulate HTML4 in XML@` resulting in XHTML 1.0. The next modularized the elements and attributes into convenient collections for use in documents that combine HTML with other tag sets. The modules are defined in XHTML Modularization. XHTML Basic is an example of fairly minimal build of these modules and is targeted at mobile applications. XHTML 1.1 is an example of a larger build of the modules@` avoiding many of the presentation features.
Other Public Drafts他の公式な試案 HTML Working Group RoadmapHTML ワーキング グループ の ロードマップ This describes the timeline for deliverables of the HTML working group. It used to be a W3C NOTE but has now been moved to the MarkUp area for easier maintenance. これは何かっつーとだなー。HTML working group の タイムラ イン を公開してんだな。今までは W3C NOTE だったけど、 MarkUp の方に移されてきたわけよ。これで、もちっとメインテ ナンスがカンタンになるな。
This Candidate Recommendation specifies a modularization of XHTML 1.0. There are two aspects to the proposed modularization: modularization into semantic modules@` and implementation of these semantic modules through a document type definition (DTD). Semantic modules provide a means for subsetting and extending XHTML@` a feature desired for extending XHTML's reach onto emerging platforms. Modularization at the DTD level improves the ability to create new complete DTDs from XHTML and other DTD modules.
This specification defines the XHTML Event Module@` an XHTML module that provides XML languages with the ability to represent in syntax the semantics of the Document Object Model (DOM) Level 2 event interfaces. これは何かっつーとだな。XHTML の イベントモジュール ス について詳しく説明してんのよ。もっとまじめに説明す っと、ある XHTML のモジュールでさ。XML 言語を提供す んのよ。こいつには、次の能力がある。どういう能力かっ つーと、Document Object Model (DOM) Level 2 event interfaces の 考え方を反映した構文ルールで表現でき るってわけさ。
The XHTML Basic document type includes the minimal set of modules required to be an XHTML Host Language document type@` and in addition it includes images@` forms@` basic tables@` and object support. It is designed for Web clients that do not support the full set of XHTML features; for example@` Web clients such as mobile phones@` PDAs@` pagers@` and settop boxes. The document type is rich enough for content authoring. XHTML Basic document type は最低限必要とされる モ ジュールス だけで構成されている。もちっと詳しく言うと、 XHTML Host Language document type として成り立つの に必要な モジュールス だけで構成されている。そんで、 それに付け加えて、イメージズ と フォームス と 基本的な テーブル とそして オブジェクト サポート も入ってる。これ はなんのためにできたかっつーと、次のような Web クライ アンツ のために作ったんだな。具体的に言うと、XHTML の全部の機能を サポート していない クライアンツ だな。 例えば、携帯電話とか PDAs とか ポケベル とか そして Web-TV みたいな セットトップ ボックシーズ とかね。ドキ ュメント タイプ は、コンテント を作るにはきちんと間に合う ように十分なものになってる。
XHTML Basic is designed as a common base that may be extended. For example@` an event module that is more generic than the traditional HTML 4 event system could be added or it could be extended by additional modules from XHTML Modularization such as the Script Module. The point is that XHTML Basic always is the common language that user agents support.XHTML Basic の設計思想はなー。拡張もできる共通基盤 なわけよ。たっとえばさぁー。こんな イベント モジュール ができる。古くさい HTML 4 のイベント システム よりもっ と使いまわしのできる イベント モジュール ができる。こう いったものが追加できるし、または、拡張もできる。んで、 それは、追加 モジュールス という形態になるわけだ。そ んで、それは、XHTML モジュラーライゼイション で可能に なるわけよ。例えば、スクリプト モジュールみたいなね。 よーするにだ。XHTML Basic は、すべてのユーザー エー ジェンツ が サポート する共通言語なわけよ。
The document type definition is implemented using XHTML modules as defined in "Modularization of XHTML". document type definition は、XHTML の モジュールス を 使って実装される。で、その詳しい定義は、 "Modularization of XHTML" でされてる。
This working draft defines a new XHTML document type that is based solely upon the module framework defined in Building XHTML Modules and the modules defined in Modularization of XHTML. The purpose of this document type is to serve as the basis for future extended XHTML family document types@` and to provide a consistent@` forward looking document type cleanly separated from the deprecated@` legacy function of HTML 4.0 that was brought forward into XHTML 1.0 document types. Note that the materials in this document were formerly part of the Modularization of XHTML document@` but have been separated out for editorial purposes.
The increasing disparities between the capabilities of different kinds of Web browsers present challenges to Web content developers wishing to reach a wide audience. A promising approach is to formally describe profiles for documents intended for broad groups of browsers@` for instance@` separate document profiles for browsers running on desktops@` television@` handhelds@` cellphones and voice browsers. Document profiles provide a basis for interoperability guarantees. If an author develops content for a given profile and a browser supports the profile then the author may be confident that the document will be rendered as expected. The requirements for document profiles are analyzed.
We would like to hear from you via email. Please send your comments to: [email protected] (archive). Don't forget to include XHTML in the subject line. キミの意見をぜひ email で聞かせてほしいな。キミのコメンツはこちらに 送ってくれ。 [email protected] (アーカイブもあるぜよ).その際には、必 ず、XHTML とサブジェクトに入れてくれよな。
Here are some rough guidelines for HTML authors. If you use these@` you are more likely to end up with pages that are easy to maintain@` look acceptable to users regardless of the browser they are using@` and can be accessed by the many Web users with disabilities. Meanwhile W3C have produced some more formal guidelines for authors. Have a look at the detailed Web Content Accessibility Guidelines. . .
A question of style sheets. For most people the look of a document - the color@` the font@` the margins - are as important as the textual content of the document itself. But make no mistake! HTML is not designed to be used to control these aspects of document layout. What you should do is to use HTML to mark up headings@` paragraphs@` lists@` hypertext links@` and other structural parts of your document@` and then add a style sheet to specify layout separately@` just as you might do in a conventional Desk Top Publishing Package. That way@` not only is there a better chance of all browsers displaying your document properly@` but also@` if you want to change such things as the font or color@` it's really simple to do so. See the Touch of style.