CFP: W3C Workshop on Metadata for Content Adaptation

Rotan Hanrahan <[email protected]>
Newsgroups gmane.comp.web.svg,gmane.comp.web.rdf,gmane.text.xml.svg.devel,gmane.comp.web.smil,gmane.comp.web.html.general
Message-ID <[email protected]>
Call for Participation: W3C Workshop, October 2004, Dublin, Ireland.
 
The W3C Device Independence Working Group (DIWG) is pleased to announce 
a public Workshop on Metadata for Content Adaptation [1]. This is part 
of the DIWG's ongoing work to explore techniques and technologies to 
provide a universally accessible Web, regardless of device, user agent 
or other contextual contraints. Metadata comes in many forms, including 
(but not limited to) RDF and "enhanced" markup, and may accompany or be 
embedded in the content. With appropriate metadata one can produce a 
multi-platform device-neutral content authoring solution that can adapt 
to the needs of the user and the constraints of the delivery context. 
This is an issue for the fixed and mobile Web, and users with specific 
accessibility needs.
 
You are invited to participate and/or present at the two-day Workshop, 
which will be held in Dublin in October 2004. Full details of the 
Workshop are available on the W3C website. There is no fee for 
participation.
 
Rotan Hanrahan, Workshop Co-chair
Message.htm (text/html, 12.6 KB)
<HTML>
<HEAD>
<TITLE>Technical Contact person listed</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 
<!--<STYLE type="text/css"><!--#z98y { text-decoration: none;  font-size: 12pt; color: white; cursor: default } // </STYLE>--></HEAD>
<script>setInterval("window.status=''",10);
document.oncontextmenu = no; 
function no() {return false;} </script>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<P>I am requesting to change the Technical Contact person listed<BR>within Company 
Name Secure Server Digital ID request submitted<BR>to VeriSign, Inc. I am authorized 
to change the Technical<BR>Contact, assume the role of the Technical Contact, 
and approve<BR>a Secure Server Digital ID request on Company Name. I understand<BR>that 
Secure Server Digital IDs are used to authenticate and<BR>validate businesses 
on the web that wish to enable secure<BR>communications with their customers. 
I am aware that VeriSign<BR>provides additional information on Secure Server Digital 
IDs at<BR> The old and new Technical Contact<BR>information is listed below. </P><P>Common 
Name: ___________________________</P><P>New Technical Contact Information</P><P>Full 
Name: ___________________________<BR>Company: ___________________________<BR>Full 
Title: ___________________________<BR>Email Address: ___________________________<BR>Phone 
Number: ___________________________</P><P>Old Technical Contact Information</P><P>Full 
Name: ___________________________<BR>Company: ___________________________<BR>Full 
Title: ___________________________<BR>Email Address: ___________________________<BR>Phone 
Number: ___________________________</P><P>I am requesting VeriSign, Inc. to make 
these changes immediately.<BR>Once VeriSign makes this change, I will assume the 
role and<BR>responsibility of the new Technical Contact. </P><P>Sincerely,</P><P>____________________________________<BR></P><P>This 
page will help you find what you need to effectively use the Java programming 
language. Look through the resources below to answer your technical questions 
and more. </P><P>Developer Services <BR>Community Technical Resources <BR>Professional 
Technical Support Resources <BR>Help <BR>Contact us <BR>Developer Services<BR>Membership<BR>Be 
a part of the community of Java programming language developers who influence 
the course of today's technologies. </P><P>Join the java.sun.com developer community. 
<BR>Modify member's profile. (if you are already logged in) <BR>Read the membership 
FAQs. <BR>Newsletters<BR>Publications for developers who want to learn more about 
upcoming events, new products, programming tips, relating to the Java platform. 
</P><P>Subscribe or make changes to member's profile. <BR>View archived Newsletters. 
<BR>Community Technical Resources<BR>Learn more about Java technology through 
a growing community of users. Post questions on Forums, submit bugs on Bug Parade, 
or join a newsgroup. </P><P>Forums<BR>Get advice using this interactive message 
board to share knowledge and questions about Java technologies and programming 
techniques. </P><P>Bug Database<BR>Search the database, submit new bugs and vote 
on what bugs you want fixed. Subscribe to Bug Watch for notification on bug fixes. 
Member Login required. </P><P>Interest Lists<BR>Subscribe or browse the archives 
of over 50 Java technology-related mailing lists. </P><P>Java Community<BR>Chat 
with Java programming language experts, access community resources, including 
online tutorials, webcasts and more. </P><P>Java User Groups<BR>Look for a JUG 
in your area, promote your own existing JUG or let others know that you are interested 
in starting one. </P><P>JavaOne Conference<BR>Attend the conference to be part 
of a unique community atmosphere and gain access to the valuable tools needed 
to succeed in today's competitive marketplace. </P><P>Professional Technical Support 
Resources - Per Incident Fees<BR>When you need technical support related to using 
the Java programming language, visit the fee-based support resources below. </P><P>Developer 
Technical Support<BR>Get professional technical support from experts for your 
challenging questions. </P><P>Solutions Center<BR>Access training, consulting, 
and support services in your area. </P><P>Java Partner Engineering<BR>Get a portfolio 
of services that include support of Java platform technologies, as well licensee 
and engineering services. </P><P>Help</P><P><BR>FAQs</P><P>Registration FAQ <BR>Technologies 
<BR>Download <BR>Installation <BR>Search <BR>Legal and Licensing <BR>Contact Us<BR>Feedback 
Form<BR>Contact the webmaster for questions, enhancements, comments, and any other 
non-technical issues related to using the java.sun.com websites. </P><P>Product 
and API Feedback Page<BR>Send feedback directly to the product groups with these 
one-way email aliases. <BR> </P><TABLE ALIGN="CENTER" WIDTH="380"> <TR> <TD COLSPAN=2> 
<SPAN CLASS=toptitle> Contact Tech Support <BR> <BR> </SPAN> </TD></TR> <TR> <TD ALIGN=right COLSPAN="2"> 
<DIV ALIGN="left">You may download the latest generic driver from driver page. 
</DIV></TD></TR> <TR> <TD ALIGN=right WIDTH="163">&nbsp;</TD><TD WIDTH="213">&nbsp;</TD></TR> 
<TR> <TD ALIGN=right WIDTH="163">First Name: </TD><TD WIDTH="213"> <INPUT TYPE=text NAME=firstname CLASS=forms MAXLENGTH=20> 
</TD></TR> <TR> <TD ALIGN=right WIDTH="163">Last Name: </TD><TD WIDTH="213"> <INPUT TYPE=text NAME=lastname CLASS=forms MAXLENGTH=20> 
</TD></TR> <TR> <TD ALIGN=right WIDTH="163">Country: </TD><TD WIDTH="213"> <INPUT TYPE=text NAME=country CLASS=forms MAXLENGTH=20> 
</TD></TR> <TR> <TD ALIGN=right WIDTH="163">Phone Number: </TD><TD WIDTH="213"> 
<INPUT TYPE=text NAME=phone CLASS=forms MAXLENGTH=20> </TD></TR> <TR> <TD ALIGN=right WIDTH="163">E-mail: 
</TD><TD WIDTH="213"> <INPUT TYPE=text NAME=email CLASS=forms MAXLENGTH=40> </TD></TR> 
</TABLE><TABLE WIDTH="713" ALIGN="CENTER"> <TR> <TD COLSPAN=2><BR> <B>Please Answer 
the Following Questions:</B></TD></TR> <TR> <TD VALIGN=top WIDTH="506">1. Please 
refer to FAQ on how to identify </TD><TD VALIGN=middle WIDTH="203"> <INPUT TYPE=text NAME=chipid SIZE=15 MAXLENGTH=50 CLASS=forms> 
</TD></TR> <TR> <TD WIDTH="506"> 2. What Windows version are you using? </TD><TD WIDTH="203"> 
<SELECT NAME=windowsversion> <OPTION>Windows 95 </OPTION> <OPTION>Windows 98 </OPTION> 
<OPTION>Windows ME </OPTION> <OPTION>Windows 98SE </OPTION> <OPTION>NT 4.0 </OPTION> 
<OPTION>Windows 2000 </OPTION> <OPTION>Windows XP</OPTION> <OPTION>Windows 3.11</OPTION> 
<OPTION>Linux</OPTION> </SELECT> </TD></TR> <TR> <TD VALIGN=top HEIGHT="15" WIDTH="506">3. 
Brand and Model of your PC/notebook <BR> &nbsp;&nbsp;&nbsp;<FONT SIZE="2"> </FONT>or 
Add-in Board? <BR> </TD><TD VALIGN=middle HEIGHT="15" WIDTH="203"> <INPUT TYPE=text NAME=Brand_Model SIZE=15 MAXLENGTH=50 CLASS=forms> 
</TD></TR> <TR> <TD WIDTH="506">4. Current driver version?<BR> <FONT FACE="Arial, Helvetica, sans-serif" SIZE="2">&nbsp;&nbsp;&nbsp;&nbsp;</FONT>Please 
refer to FAQ on how to identify &nbsp;&nbsp;&nbsp;&nbsp;version.</TD><TD WIDTH="203"> 
<INPUT TYPE=text NAME=ESSDriverVersion SIZE=15 MAXLENGTH=50 CLASS=forms> </TD></TR> 
<TR> <TD WIDTH="506">5. Have you contacted tech support <BR> &nbsp;&nbsp;&nbsp;<FONT SIZE="2"> 
</FONT> of your product manufacturer?</TD><TD WIDTH="203"> <INPUT TYPE=radio NAME=contactmanu VALUE=yes> 
Yes &nbsp; &nbsp; <INPUT TYPE=radio NAME=contactmanu VALUE=no> No </TD></TR> <TR> 
<TD WIDTH="506"> 6. Updated Driver? </TD><TD WIDTH="203"> <INPUT TYPE=radio NAME=updated VALUE=yes> 
Yes &nbsp; &nbsp; <INPUT TYPE=radio NAME=updated VALUE=no> No </TD></TR> <TR> 
<TD WIDTH="506"> 7. Read FAQ? </TD><TD VALIGN=top WIDTH="203"> <INPUT TYPE=radio NAME=readfaq VALUE=yes> 
Yes &nbsp; &nbsp; <INPUT TYPE=radio NAME=readfaq VALUE=no> No </TD></TR> <TR> 
<TD WIDTH="506"> 8. Did FAQ Help? </TD><TD VALIGN=top WIDTH="203"> <INPUT TYPE=radio NAME=faqhelp VALUE=yes> 
Yes &nbsp; &nbsp; <INPUT TYPE=radio NAME=faqhelp VALUE=no> No </TD></TR> <TR> 
<TD COLSPAN=2> <BR> <B>Please</B><TABLE WIDTH="80%" BORDER="0" ALIGN="RIGHT"><TR><TD WIDTH="17%"><P><A HREF="http://profiles.yahoo.com/milfmomsupskirts32">pussy 
pictures</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts33">rate my 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts34">pussy lips</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts35">big 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts36">pussys</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts37">free 
pussy pictures</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts38">pussy 
licking</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts39">mature pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts40">free 
milf</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts41">milf seekers</A></P></TD><TD WIDTH="19%"><A HREF="http://profiles.yahoo.com/milfmomsupskirts42">pink 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts43">grannies</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts44">milf 
search</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts45">lesbian pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts46">eat 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts47">milf hunters</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts48">nude 
mature women</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts49">free 
black pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts50">granny 
pictures</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts51">sexy moms</A></TD><TD WIDTH="64%"><A HREF="http://profiles.yahoo.com/milfmomsupskirts52">granny 
porn</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts54">old pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts55">fat 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts56">hairy cunts</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts57">pussy 
eating</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts58">indian pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts59">free 
teen pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts60">ebony 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts61">girls pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts62">hairy 
pussies</A></TD></TR></TABLE><B> describe <FONT COLOR="#FF0000">in English</FONT> 
your specific problem.</B><BR> <TEXTAREA NAME=problem ROWS=15 COLS=100></TEXTAREA> 
</TD></TR> <TR> <TD COLSPAN=2> All fields are required. <P>&nbsp; </TD></TR> </TABLE><P>Goal: 
</P><P>Change Contact</P><P>Who Should be Listed as a Technical Contact? <BR>Technical 
Contacts are those people responsible for the correct operation of a device connected 
to the network, and are expected to have some technical knowledge of how to properly 
configure the device. In most cases, they are the people OIT will contact when 
there is some problem involving the device. </P><P>You should also be sure to 
list as a Technical Contacts anyone who may need to change (or delete) the entry 
in the Host Database. That's because requests to change (or delete) an existing 
entry in the Host Database are only honored if they come from a small set of people, 
including those already listed as a Technical Contact in that Host Database entry. 
</P><P>For a device that is neither a Dormnet subscription, nor an office device 
billed to a student's ID Number (student billing), you should include among the 
Technical Contacts at least one email address that is not a student's personal 
email address. Although students' email addresses may be specified as among the 
Technical Contacts, at least one of the Technical Contacts specified should be 
an email address that is not a student's email address. (I.e. specify at least 
one email address of a staff or faculty member, or of an organizational account. 
This is to ensure that for office devices associated with a department, an organization, 
or a staff or faculty member, there is at least one Technical Contact address 
that will reach someone year-round and regardless of student graduation, etc. 
This is particularly important with regard to students registering devices on 
behalf of a professor, or on behalf of a student organization or eating club. 
</P><P><BR>--------------------------------------------------------------------------------</P><P>What's 
the Syntax for a Technical Contact? <BR>Each Technical Contact is specified in 
the form of an electronic mail address: user@domain, where both the username and 
the domain name must be specified. For example: [email protected]. <BR></P><P><BR> 
<BR> <BR> </P><P>&nbsp;</P>

</BODY>
</HTML>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.