You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
336 lines
12 KiB
336 lines
12 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
|
<style type="text/css">
|
|
BODY {
|
|
margin: 2em 1em 2em 70px;
|
|
font-family: sans-serif;
|
|
color: black;
|
|
background-color: #FFFFE8;
|
|
background-position: top left;
|
|
background-attachment: fixed;
|
|
background-repeat: no-repeat;
|
|
}
|
|
|
|
TH, TD { /* ns 4 */
|
|
font-family: sans-serif;
|
|
}
|
|
|
|
H1, H2, H3 {
|
|
text-align: left;
|
|
font-family: sans-serif;
|
|
font-weight: normal;
|
|
color: #0050B2;
|
|
}
|
|
|
|
.hide { display: none }
|
|
|
|
DIV.head { margin-bottom: 1em }
|
|
DIV.head H1 { margin-top: 2em; clear: both }
|
|
DIV.head TABLE { margin-left: 2em; margin-top: 2em }
|
|
DIV.head IMG { color: white; border: none } /* remove border from top image */
|
|
|
|
P.copyright { font-size: smaller }
|
|
|
|
@media screen { /* hide from IE3 */
|
|
A:hover { background: #FFA }
|
|
}
|
|
|
|
PRE { margin-left: 2em }
|
|
/*
|
|
P {
|
|
margin-top: 0.6em;
|
|
margin-bottom: 0.6em;
|
|
}
|
|
*/
|
|
DT, DD { margin-top: 0; margin-bottom: 0 } /* opera 3.50 */
|
|
DT { font-weight: bold }
|
|
|
|
PRE { font-family: monospace } /* navigator 4 requires this */
|
|
|
|
UL.toc {
|
|
list-style: disc; /* Mac NS has problem with 'none' */
|
|
list-style: none;
|
|
}
|
|
|
|
@media aural {
|
|
H1, H2, H3 { stress: 20; richness: 90 }
|
|
.hide { speak: none }
|
|
P.copyright { volume: x-soft; speech-rate: x-fast }
|
|
DT { pause-before: 20% }
|
|
PRE { speak-punctuation: code }
|
|
}
|
|
code {
|
|
font-family: monospace;
|
|
}
|
|
</style>
|
|
<title>W3C Web Editing Tools</title>
|
|
</head>
|
|
|
|
<body lang="en">
|
|
<p><a href="http://www.w3.org/"><img
|
|
src="http://www.w3.org/AudioVideo/Group/w3c_home" alt="W3C" border="0"> </a><!-- context info
|
|
--></p>
|
|
|
|
<h1>W3C Web Editing Tools for Media Annotations WG.</h1>
|
|
|
|
<p></p>
|
|
<hr>
|
|
|
|
<h2>Tools and Guidelines for editing specification in WG space</h2>
|
|
|
|
<h2></h2>
|
|
|
|
<p>These tools allow editing any document in the Working Group space
|
|
(http://www.w3.org/2008/WebVideo/Annotations/)</p>
|
|
<ol>
|
|
<li>Editors SHOULD use <a href="#Jigedit">Jigedit</a> to publish on w3C web
|
|
site.</li>
|
|
<li>Editors should use an <a href="#HTML">HTML authoring tool </a>that allows
|
|
to publish on our web site using a PUT, else you should use our internal <a
|
|
href="#an">PUT tools</a>, or <a href="#W">WebDav</a> or <a
|
|
href="#C-Use">CVS</a>.</li>
|
|
<li>Editors MUST use <a href="#Validation">Validation Tools</a></li>
|
|
</ol>
|
|
|
|
<h4><a name="an" id="an">A- Use an</a> <a href="#HTML" name="HTML"
|
|
id="HTML">HTML authoring tool </a>that allows to publish on our web site using
|
|
a PUT.<br>
|
|
</h4>
|
|
<ul>
|
|
<li><a href="http://www.w3.org/Amaya/">Amaya</a> is the W3C's
|
|
browser/authoring tool and is used to demonstrate and test many of the new
|
|
developments in Web protocols and data formats. It is available on both
|
|
Unix and Windows '95/NT platforms. <br>
|
|
It supports most advanced features of HTTP 1.1 , such as content
|
|
negotiation to retrieve the most appropriate picture format, keep alive
|
|
connections to save bandwidth and authentication to allow secure remote
|
|
publishing.</li>
|
|
</ul>
|
|
|
|
<p>If your Web authoring tool does not support PUT, you should use our internal
|
|
<a name="PUT">internal PUT tools,</a>:</p>
|
|
<ul>
|
|
<li><a href="http://jigsaw.w3.org/Benoit/Public/Winie/">Winie</a> is a Java
|
|
network utility to put (delete and get) files on the World Wide Web using
|
|
HTTP/1.1. <br>
|
|
A highly recommended tool allowing, version conflict detection, retries
|
|
when connection closed, upload all files located in a directory
|
|
(recursively or not), support for proxies and metadata configuration
|
|
(language, charset).<br>
|
|
Winie needs jdk1.2.2</li>
|
|
<li><a href="http://www.w3.org/WinCom/">Web Commander</a> is a Win32
|
|
application to put (delete and get) documents remotely using HTTP/1.1. <br>
|
|
It allows the user to explicitly control the metadata describing the
|
|
document to save including the language, type, charset, etc. <a
|
|
href="http://www.w3.org/AudioVideo/tools/Libwww_V5_2_8.exe">Download Web
|
|
Commander</a>.</li>
|
|
</ul>
|
|
|
|
<h4><a name="W" id="W">B- Use W</a>ebDav</h4>
|
|
|
|
<p><a href="http://www.w3.org/Guide/Jigedit/Webdav">WebDAV</a> is an HTTP-based
|
|
protocol that allows accessing the content of an HTTP server as a networked
|
|
filesystems; to put it simply, it allows to edit directly a Web site as if it
|
|
were an additional disk on your computer. JigEdit accounts are configured to
|
|
allow users to use the WebDAV protocol. </p>
|
|
|
|
<h4><a name="C-Use" id="C-Use">C- Use CVS</a></h4>
|
|
|
|
<p>CVS accounts are available for web account holders at member and public
|
|
level access. They are described as follows:</p>
|
|
<ul>
|
|
<li>cvs.w3.org (Member) CVS access denotes that the holder of the account has
|
|
carefully circumscribed access to the W3C site. The requested work area
|
|
must be included in the original account request (see below). These
|
|
accounts access spaces under cvs.w3.org:/w3ccvs.</li>
|
|
<li>dev.w3.org (Public) CVS access denotes that the holder has read/write
|
|
access to the public areas of the W3C site. These accounts are provided to
|
|
those Collaborators and Invited Experts that are performing collaborative
|
|
functions on code or documents maintained under spaces in
|
|
dev.w3.org:/sources/public or elsewhere on the public server.</li>
|
|
</ul>
|
|
|
|
<p>Nota bene: In order to process requests for either of the above types of CVS
|
|
account, the request MUST include a SSH public key (the id_{dsa,rsa}.pub file)
|
|
in OpenSSH format from the end user. </p>
|
|
|
|
<p>Note: CVS is only recommended for expert users. If you would prefer to use a
|
|
simpler interface to edit pages on the Web site, consider WebDAV. Refer to the
|
|
guidebook <a href="http://www.w3.org/Project/CVSdoc/">Use of CVS in W3C</a></p>
|
|
|
|
<p>Send your request to Thierry Michel , (<a
|
|
href="mailto:tmichel@w3.org">tmichel@w3.org</a>) for a CVS account if you need
|
|
one.</p>
|
|
|
|
<h3><a name="Validation">Validation Tools</a></h3>
|
|
|
|
<p>Append one of these magic words to the end of any URI on www.w3.org for
|
|
quick access to the tool (it does not work in DEV space (http://dev.w3.org).</p>
|
|
<ul>
|
|
<li><strong>,checklink</strong> or <strong>,checklinks: </strong>runs Link
|
|
Checker. Works on non-public pages too !</li>
|
|
<li><strong>,validate: </strong>runs Validator on the URL. Works on
|
|
non-public pages too !</li>
|
|
<li><strong>,cssvalidate</strong>: runs CSS Validator on the URL.</li>
|
|
<li><strong>,text: </strong>outputs a text only version of the page. Very
|
|
handy to paste pages into a mail. Does not work on non-public pages yet
|
|
:-(</li>
|
|
</ul>
|
|
|
|
<p><strong></strong></p>
|
|
|
|
<h3><a name="Editors">Editors</a> must conform to W3C Publication
|
|
Guidelines</h3>
|
|
|
|
<p><strong>Note</strong>. It is not the role of the Team Contact or of the W3C
|
|
Communications or Web Teams to ensure that documents are valid; it is the
|
|
Editor's responsibility. The Editor should ensure validity before requesting
|
|
publication. The W3C makes available validation services to assist Editors.</p>
|
|
|
|
<p>Please follow these steps to ensure that your documents are valid once in TR
|
|
space:</p>
|
|
<ul>
|
|
<li>Check your spelling.</li>
|
|
<li>Make sure there are no broken links in your documents at the time of
|
|
publication. Some services on the Web may help you with this, including
|
|
W3C's link checking service (append ",checklink" to the URL).</li>
|
|
<li>Make sure your Technical Report validates in the HTML Validation Service
|
|
(using the HTML 4.0, 3.2, or 2.0 DTDs). You may append ",validate" to a W3C
|
|
URI to invoke the HTML validator for the resource. Please make sure any
|
|
HTML examples in your document validate as well.</li>
|
|
<li>Make sure your Technical Report validates in the CSS Validation Service.
|
|
You may append ",cssvalidate" to a W3C URI to invoke the CSS validator for
|
|
the resource. Please make sure any CSS examples in your document validate
|
|
as well.</li>
|
|
<li>Make sure your document is accessible: Follow the Web Content
|
|
Accessibility Guidelines. Use an automated tool such as Bobby. </li>
|
|
</ul>
|
|
|
|
<p></p>
|
|
|
|
<h3><a name="Jigedit">Jigedit</a></h3>
|
|
|
|
<p>Here are some hints about Jigedit, our publishing tool.</p>
|
|
|
|
<p>You MUST have a Jigedit account to publish on w3C web site. Send your
|
|
request to Thierry Michel , (<a
|
|
href="mailto:tmichel@w3.org">tmichel@w3.org</a>) for a jigedit account if you
|
|
need one.</p>
|
|
|
|
<p>Jigedit is our PUT server that allows users to easily upload documents on
|
|
our web site, and to concurrently edit the same documents. It is based on
|
|
jigsaw, the W3C HTTP server, and CVS, the Concurrent Versioning System.<br>
|
|
There is documentation in the <a
|
|
href="http://www.w3.org/Guide/Jigedit/">Jigedit Guide</a> on how to use
|
|
Jigedit. The documentation needs work, but it would get you started. <br>
|
|
<br>
|
|
You can browse your area in jigedit: <em>http
|
|
://jigedit.w3.org/your-jigedit-account/</em><br>
|
|
It looks like a file system. The Root of the W3C Web site is at <em>http
|
|
://jigedit.w3.org/your-jigedit-account/WWW/</em></p>
|
|
|
|
<p>You can select any html file, and then edit it using one of the <a
|
|
href="#HTML">PUT-capable HTML editors</a>, and then save it: it will be
|
|
uploaded on our web site, and immediately browsable using the regular
|
|
www.w3.org URL. The recommended way to PUT is using our <a href="#PUT">PUT
|
|
tool</a>. The other recommended tool is W3C's own browser/editor, <a
|
|
href="http://www.w3.org/Amaya/">Amaya</a></p>
|
|
|
|
<p>Access is limited to <em>http
|
|
://jigedit.w3.org/your-jigedit-account/WWW/2008/WebVideo/Annotations/</em>
|
|
only. You can't browse or PUT documents in other areas of our web site through
|
|
jigedit.<br>
|
|
What you see in <em>http
|
|
://jigedit.w3.org/your-jigedit-account/WWW/2008/WebVideo/Annotations/</em> is a
|
|
copy of the content of our web site in the SYMM Working Group area. When you
|
|
upload a new document, it will automatically be propagated to the 'live' copy
|
|
on the main web site. </p>
|
|
|
|
<p>For example if you need to publish a document to
|
|
<em>http://www.w3.org/2008/WebVideo/Annotations/foo.html</em><br>
|
|
Use jigedit and upload it to: <em>http
|
|
://jigedit.w3.org/your-jigedit-account/WWW/2008/WebVideo/Annotations/foo.html</em></p>
|
|
|
|
<p></p>
|
|
|
|
<p>In order to change your Jigedit Password use <em>http
|
|
://jigedit.w3.org/your-jigedit-account/ChangePassword</em></p>
|
|
|
|
<p>Questions and requests about jigedit should go to <a
|
|
href="mailto:webreq@w3.org">webreq@w3.org</a> . There is some information on
|
|
how jigedit works in the <a href="http://www.w3.org/Guide/Jigedit/">Jigedit
|
|
Guide</a>.</p>
|
|
|
|
<p></p>
|
|
|
|
<h2>Tools and Guidelines for editing specification in DEV space</h2>
|
|
|
|
<p>These tools allow editing any document in the Working Group space
|
|
(http://dev.w3.org/2008/video/mediaann/)</p>
|
|
<ol>
|
|
<li>Editors MUST use CVS and XML spec tool to publish on W3C DEV
|
|
webspace.</li>
|
|
</ol>
|
|
|
|
<h4>A-Use CVS</h4>
|
|
|
|
<p>CVS accounts are available for web account holders at member and public
|
|
level access. They are described as follows:</p>
|
|
<ul>
|
|
<li>cvs.w3.org (Member) CVS access denotes that the holder of the account has
|
|
carefully circumscribed access to the W3C site. The requested work area
|
|
must be included in the original account request (see below). These
|
|
accounts access spaces under cvs.w3.org:/w3ccvs.</li>
|
|
<li>dev.w3.org (Public) CVS access denotes that the holder has read/write
|
|
access to the public areas of the W3C site. These accounts are provided to
|
|
those Collaborators and Invited Experts that are performing collaborative
|
|
functions on code or documents maintained under spaces in
|
|
dev.w3.org:/sources/public or elsewhere on the public server. </li>
|
|
</ul>
|
|
|
|
<p>Nota bene: In order to process requests for either of the above types of CVS
|
|
account, the request MUST include a SSH public key (the id_{dsa,rsa}.pub file)
|
|
in OpenSSH format from the end user. </p>
|
|
|
|
<p></p>
|
|
|
|
<p>You MUST have a CVS account to publish on W3C DEV webspace. Send your
|
|
request to Thierry Michel , (<a
|
|
href="mailto:tmichel@w3.org">tmichel@w3.org</a>) for a CVS account if you need
|
|
one.</p>
|
|
|
|
<p>Refer to the guidebook <a href="http://www.w3.org/Project/CVSdoc/">Use of
|
|
CVS in W3C</a></p>
|
|
|
|
<p></p>
|
|
|
|
<h4>B-Use of XMLSpec</h4>
|
|
|
|
<p>You need CVS read and write access to the W3C Public CVS Repository. After
|
|
getting the access, checkout the <a
|
|
href="http://dev.w3.org/cvsweb/2008/video/mediaann/">complete Media
|
|
Annotations</a> directory</p>
|
|
|
|
<p>Refer to the XMLSPEC info page</p>
|
|
|
|
<p><a
|
|
href="editors.html#xmlspec">http://www.w3.org/2008/WebVideo/Annotations/editors.html#xmlspec</a></p>
|
|
|
|
<p></p>
|
|
<hr>
|
|
|
|
<p>Thierry Michel , (<a href="mailto:tmichel@w3.org">tmichel@w3.org</a>), W3C
|
|
staff contact.</p>
|
|
|
|
<p>last revised $Date: 2009/12/08 21:45:18 $ by $Author: tmichel $</p>
|
|
|
|
<p></p>
|
|
|
|
<p></p>
|
|
|
|
<p></p>
|
|
</body>
|
|
</html>
|