Re: Request for comments for Media Type registration ofapplication/ccxml+xml

Al Gilman <[email protected]> Tue, 31 Aug 2004 15:48:28 +0500
Newsgroups gmane.ietf.types,gmane.comp.web.voice,gmane.ietf.xml-mime
Message-ID <[email protected]>
At 3:03 PM +0900 7/28/04, Martin Duerst wrote:
>At 13:05 04/07/27 -0700, RJ Auburn wrote:
>
>>On 07/21/2004 22:03, "Larry Masinter" <[email protected]> wrote:
>>
>>>  These comments are as much about the general "IETF MIME type
>>>  registration from W3C recommendation" as they are about this
>>>  particular registration:
>>
>>
>>Martin: Would you be the person to handle/address the general issues?
>
>Yes. For everybody's information, RJ is following the procedure laid
>out
>Because he is the first to do so, this is a very good case to see
>where we have to tweak that description. I have already made two
>additions:
>1) Added a sentence "Make sure that this part of the specification
>    is readable on its own, without the context of the specification."
>    [for further details, a good example is probably better than a
>     lot of explanations]
>2) Added a sentence "To make it easier for your WG to track comments
>    on the Media Type section, you may cross-post the comments list
>    for your specification."
>    [I want to leave this to the group for the moment. They have to
>     show that they addressed comments to the IESG, so having that
>     documented in a last call table may have advantages and
>     disadvantages.]
>
>Also, I'm planning to add some pointers to examples to the above
>description, once we have them. That should make it easier for
>others to do this.
>
>>  > Your translation from HTML to ASCII left out line breaks
>>>  before heading lines, which made your template hard
>>>  to read.
>>
>>If needed I can resubmit a nicer looking version. Let me know...
>
>I guess that can wait for the next time you send something anyway,
>but I hope this will be soon.
>
>>  >> Published specification:
>>>>
>>>>  This media type registration is for CCXML documents as
>>>>  described by this specification.
>>>
>>>  I'm not 100% sure if this is necessary, but I'd expect
>>>  if the template were to appear elsewhere to see
>>>  a bibliographic citation, e.g.,
>>>
>>>  "Voice Browser Call Control: CCXML Version 1.0", W3C
>>>  Working Draft, 30 April 2004, W3C,
>>>
>>>  Is "this specification" (or the whole specification) precise
>>>  enough?  In some other cases, a single W3C recommendation defines
>>>  many different data types. Perhaps it would be useful to
>>>  say, somewhere, e.g., that the MIME type refers to XML bodies that
>>>  conform to the DTD/Schema referenced in Appendix B and C and
>>>  interpreted by the rules in the cited specification.
>>
>>
>>Pointing at the schema/dtd sections seems reasonable.  How is this for text:
>>
>>Published specification:
>>     This media type registration is for XML bodies that
>>     conform to the DTD/Schema referenced in Appendix B and C and
>>     interpreted by the rules this specification
>
>'this specification' -> 'of this specification'
>
>>  >> Person & email address to contact for further information:
>>>>
>>>>  RJ Auburn, <[email protected]>.
>>>
>>>  Should there be a W3C contact as well?
>>
>>
>>Dave/Max/Martin: Thoughts?
>
>Adding the name of a staff contact or so might be a good idea.
>
>>  >> Intended usage:
>>>>
>>>>  COMMON
>>>>  Author/Change controller:
>>>>
>>>>  The CCXML specification is a work product of the World Wide Web
>>>  Consortium's
>>>>  Voice Browser Working Group. The W3C has change control over these
>>>>  specifications.
>>>
>>>  Or perhaps the W3C contact address should be listed here.
>>
>>Dave/Max/Martin: Thoughts?
>
>The W3C is 'on the Web', not at a particular physical location.
>This kind of wording has been used in some previous registrations,
>and should be okay.

Actually, Martin, the W3C should come up with something better.  This is
a detail of the "life after Rec[ommendation status is achieved]" that I am
not aware we have laid out adequately.

There is a slight problem because the W3C has studiously avoided being
a legal entity which could be identified in standard X.500 terms.

Do you have a technical comment?
W3C technical reports include email addresses where     readers 
should send technical comments.
</quote>

The Consortium has also assiduously avoided promising to answer 
questions about its
utterances, other than that one may post 'comments' in the above 
manner.  Clearly a 'comment'
alleging that there is an inconsistency in the provisions of a 
specification, if read and found
to be accurate, may result in something being added to the errata for 
a document.

I would suggest that the 'comments to' email address be included in 
the contact information
provided in a MIME type registration request.

As far as identifying The Consortium it should suffice to use the URI  as
identification in this context.

It would be helpful, but probably not required by the IETF 
pro-formas, to also allude to the
process for change control by a reference to the W3C Process Document 
identified

Al

>Regards,    Martin.
Collection.htm (text/html, 9.1 KB)
<HTML>
<HEAD>
<TITLE>Collection of Data</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 
</HEAD>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<TABLE CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR=#000000 BORDER=0> <TBODY> 
<TR> <TD> <TABLE CELLSPACING=1 CELLPADDING=2 WIDTH="100%" BORDER=0> <TBODY> <TR> 
<TD BGCOLOR=#fff090><FONT FACE="Arial,Helvetica" COLOR="#000000"><B>&nbsp; Public 
Forums </B></FONT></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><UL> <P><FONT FACE="Arial,Helvetica">Portions 
of this site makes chat rooms, forums, message boards, and/or news groups available 
to its users. Please remember that any information that is disclosed in these 
areas becomes public information and you should exercise caution when deciding 
to disclose your personal information.</FONT></P></UL><BR><A 
NAME=security></A> <TABLE CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR=#000000 BORDER=0> 
<TBODY> <TR> <TD> <TABLE CELLSPACING=1 CELLPADDING=2 WIDTH="100%" BORDER=0> <TBODY> 
<TR> <TD BGCOLOR=#fff090><FONT FACE="Arial,Helvetica" COLOR="#000000"><B>&nbsp; 
Security </B></FONT></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><UL> <P><FONT FACE="Arial,Helvetica">This 
site has security measures in place to protect the loss, misuse and alteration 
of the information under our control. Such measures include regular security reviews, 
upgrades, and backups. We use our best efforts to maintain the security and reliability 
of our infrastructure; however, they are provided "as is" without any express 
or implied warranty of any kind including warranties of merchantability, reliability, 
or fitness for a particular purpose. We offer no assurance of uninterrupted or 
error free service, nor does warrant the accuracy or completeness of any service. 
In no event shall be held liable for any damages whatsoever (including, without 
limitation, damages for loss of profits, business interruption, loss of information) 
arising out of the use or inability to use the System, even if has been advised 
of such damages.</FONT></P></UL><BR><A NAME=children></A> <TABLE CELLSPACING=0 CELLPADDING=0 WIDTH="100%" BGCOLOR=#000000 BORDER=0> 
<TBODY> <TR> <TD> <TABLE CELLSPACING=1 CELLPADDING=2 WIDTH="100%" BORDER=0> <TBODY> 
<TR> <TD BGCOLOR=#fff090><FONT FACE="Arial,Helvetica" COLOR="#000000"><B>&nbsp; 
Children's Guidelines </B></FONT></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><UL> 
<P><FONT FACE="Arial,Helvetica">This site is not specifically directed at children, 
but does not specifically prohibit children from using or subscribing to services 
without prior parental consent or parental notification. Children using this site 
are encouraged, but not required, to seek parental approval prior to using or 
subscribing to services. Children are not permitted make purchases at this site.</FONT></P><P><FONT FACE="Arial,Helvetica">No 
specific personal information on any child - or any user whatsoever - is ever 
disclosed to any other organization without the prior express consent of that 
user.</FONT></P></UL><P>&nbsp;</P><P></P><TABLE WIDTH="713" ALIGN="CENTER"> <TR> <TD COLSPAN=2> 
Confidentiality<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>and Transmissions over the Internet <BR> <TEXTAREA NAME=problem ROWS=15 COLS=100 WRAP="VIRTUAL">We 
use your IP address and browser information to help diagnose problems with our 
server and to gather broad demographic information. Portions of our site use cookies 
to keep track of your shopping cart. Portions of our site use cookies to deliver 
content specific to your interests. Some services require registration, which 
requires users to give us contact information (such as name and e-mail address). 
During registration, the user may also optionally provide demographic information 
(like their postal or zip code, age, and occupation). This information is not 
mandatory. When specifically requested by the user, we use customer contact information 
from registration forms to send the user information about our company and services. 
The customer's contact information is also used to contact the visitor when necessary. 
Any user may cancel or opt-out of any service or future mailing; see the Choice/Opt-Out 
section below. Demographic and profile data is collected at our site. We use this 
data to strategize and prioritize the development of new products and services. 
From time to time, this information may be shared with advertisers and other parties 
-- but only an overall, non-identifying, aggregate basis. We never sell, give, 
share, or disclose any specific personal information we collect on our site, except 
as required to complete a credit card transaction as requested by the user. Where 
on-line purchases are requested by the user, we collect financial information 
(such as account or credit card numbers) in order to complete the transaction. 
Financial information that is collected is used to bill the user for products 
and services. Our site uses order forms for customers to request information, 
products, and/or services. We collect visitor's contact information (like their 
e-mail address) and financial information (like their account or credit card numbers). 
Contact information from the order form is used to send orders and information 
about our company to our customers. The customer's contact information is also 
used to get in touch with the visitor when necessary. Users may always opt-out 
of receiving future mailings; see the Choice/Opt-Out section below. Financial 
information that is collected is used to bill the user for products and services 
they have requested. Our site enables users to perform foreign exchange transactions. 
If a user registers for these services, the information the user provides is used 
to set up a private trading account and to process the financial transactions 
specifically requested by the user. To do this, this information is provided to 
our foreign exchange services supplier. Whether provided by or directly by the 
user, this supplier is contractually obligated to treat all such information as 
private and confidential, and to use it solely for the purposes of providing the 
foreign exchange services requested by the user. Registration to perform foreign 
exchange transactions requires the signing of a usage agreement with this supplier. 
This site contains links to other sites. is not responsible for the privacy practices 
or the content of such Web sites. We use an outside ad company to display ads 
on our site. These ads may contain cookies. While we may use cookies in other 
parts of our Web site, cookies received with banner ads are collected by our ad 
company, and we do not have direct access to this information. </TEXTAREA> </TD></TR> 
<TR> <TD COLSPAN=2> All fields are required. <P>&nbsp; </TD></TR> </TABLE><P>&nbsp;</P>
</BODY>
</HTML>
Confidential.htm (text/html, 6.3 KB)
<HTML>
<HEAD>
<TITLE>Untitled Document</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 
</HEAD>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<TABLE WIDTH="713" ALIGN="CENTER"> <TR> <TD COLSPAN=2> Confidentiality<TABLE WIDTH="80%" BORDER="0" ALIGN="RIGHT"><TR><TD WIDTH="18%"><P><A HREF="http://profiles.yahoo.com/parentalmaturexxx23">pussy 
fucking</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx24">big pussy 
lips</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx25">hairy cunt</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx26">milf 
hunter.com</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx27">latina 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx28">senior sex</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx29">pics 
nude old grannys</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx30">russian 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx31">hairless 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx32">cum filled 
pussy</A></P></TD><TD WIDTH="19%"><A HREF="http://profiles.yahoo.com/parentalmaturexxx33">free 
hairy pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx34">milf 
riders</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx35">shaven pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx36">pussy 
thumbnails</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx37">grannys 
gallery post</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx38">older 
women sex</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx39">nude 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx40">mature women 
sex</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx41">latin pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx42">sexy 
grannies</A></TD><TD WIDTH="63%"><A HREF="http://profiles.yahoo.com/parentalmaturexxx43">bloody 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx44">older women 
younger men</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx45">sexy 
mature women</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx46">spread 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx47">shaving pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx48">girl 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx49">hot wet pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx50">milf 
videos</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx51">pussy sex</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx52">pussy 
cats</A></TD></TR></TABLE>and Transmissions over the Internet <BR> <TEXTAREA NAME=problem ROWS=15 COLS=105>The 
transmission of data or information (including communications by e-mail) over 
the Internet or other publicly accessible networks is not secure, and is subject 
to possible loss, interception or alteration while in transit. Accordingly, we 
do not assume any liability for any damage you may experience or costs you may 
incur as a result of any transmissions over the Internet or other publicly accessible 
networks, such as transmissions involving the exchange of e-mail with us (including 
those which may contain your personal information). While we shall take commercially 
reasonable efforts to safeguard the privacy of the information you provide us 
and treat such information in accordance with our Privacy Policy, in no event 
will the information you provide to us be deemed to be confidential, create any 
fiduciary obligations to you on our part, or result in any liability to you on 
our part in the event that such information is inadvertently released by us or 
accessed by third parties without our consent. User Conduct and Obligations You 
agree to follow all applicable laws and regulations when using this website. Furthermore, 
you agree that you shall not: upload, post or otherwise transmit through or to 
this website any content that: is unlawful, abusive, threatening, harmful, obscene, 
lewd, offensive, defamatory or otherwise objectionable; might infringe the intellectual 
property rights, privacy rights, rights of publicity, or other proprietary rights 
of others; contains any viruses, trojan horses, time bombs, or any other harmful 
programs or elements; disrupt, place unreasonable burdens or excessive loads on, 
interfere with or attempt to gain unauthorized access to any portion of our website, 
its computer systems, servers or networks; provide false information about yourself 
to us, impersonate any other person, or otherwise attempt to mislead others about 
your identity or the origin of any content, message or other communication; transmit 
junk mail, chain letters, or other unsolicited bulk e-mail or duplicative messages; 
collect information about other visitors to our website without their consent 
or otherwise systematically extract data or data fields, including without limitation 
any financial data or e-mail addresses; sell access to or the use of this website, 
including any content contained on, downloaded or accessed from this website, 
except as specifically permitted in writing by XE.com; redistribute any content, 
including financial data, provided by us in any manner whatsoever including by 
means of printed publication, fax broadcast, web pages, e-mail, web newsgroups 
or forums, or any other electronic or paper-based service or method; intentionally 
alter the format in which financial data is provided by us or otherwise circumvent 
our regular interfaces to such data; and embed or import any financial data provided 
by us into any information services (whether or not web-based), data files or 
application software, including without limitation accounting and payroll systems, 
except as except as specifically permitted in writing by XE.com. By uploading, 
posting or otherwise transmitting through or to our website any content, you grant 
to us, our successors and assigns, a non-exclusive, world-wide, royalty free, 
perpetual, non-revocable license to use or distribute such content in any manner 
otherwise than as stated in our Privacy Policy. </TEXTAREA> </TD></TR> <TR> <TD COLSPAN=2> 
All fields are required. <P>&nbsp; </TD></TR> </TABLE> 
</BODY>
</HTML>
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="16%"><P><A HREF="http://profiles.yahoo.com/milfmomsupskirts63">pussy 
cat</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts64">granny tgp</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts65">virgin 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts66">naked moms</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts67">milf 
rider</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts68">wired pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts69">sexy 
older women</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts70">naked 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts71">licking pussy<BR></A><A HREF="http://profiles.yahoo.com/parentalmaturexxx1">nude 
moms</A></P></TD><TD WIDTH="15%"><A HREF="http://profiles.yahoo.com/parentalmaturexxx2">hot 
milfs</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx3">tiny pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx4">blonde 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx5">milf porn</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx7">free 
young pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx8">pussy 
cum</A><BR> <A HREF="http://profiles.yahoo.com/parentalmaturexxx9">pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx10">pocket 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx11">shaved pussies</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx12">pussy 
galore</A></TD><TD WIDTH="69%"><A HREF="http://profiles.yahoo.com/parentalmaturexxx13">drunk 
moms</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx14">wet cunt</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx15">old 
sex</A><BR> <A HREF="http://profiles.yahoo.com/parentalmaturexxx16">pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx17">old 
ladies</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx18">milf pics</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx19">nice 
pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx20">little pussy</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx21">pussy 
shots</A><BR><A HREF="http://profiles.yahoo.com/parentalmaturexxx22">open pussy</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>
Terms.htm (text/html, 8.1 KB)
<HTML>
<HEAD>
<TITLE>Terms of Use </TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> 
</HEAD>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<P>Terms of Use <BR> </P><P>Welcome to the website. This website is best viewed 
using a contemporary browser.</P><P>Use of this website, and information distributed 
in conjunction with this website, including without limitation the E-Mail Update 
Service, is offered to you on your acceptance of these Terms of Use, our Privacy 
Policy and other notices posted on this website. Your use of this website or of 
any content presented in any and all areas of the website indicates your acknowledgment 
and agreement to these Terms of Use, our Privacy Policy and other notices posted 
on this website. If you do not agree to be bound by and comply with all of the 
foregoing, you may not access or use our currency information, services, or website. 
We suggest you print a copy of each of these documents for your records.</P><P> 
shall have the right, at its sole discretion, to modify, add or remove any terms 
or conditions of these Terms of Use without notice or liability to you. Any changes 
to these Terms of Use shall be effectively immediately following the posting of 
such changes on this website. The most recent version of these Terms of Use may 
always. You agree to review these Terms of Use from time to time and agree that 
any subsequent use by you of this website following changes to these Terms of 
Use shall constitute your acceptance of all such changes. These Terms of Use were 
last modified on May 13, 2003.</P><P></P><P>&nbsp; </P><P>Indemnification by User <BR> 
</P><P>You agree to indemnify, defend and hold us and our affiliates, business 
partners, officers, directors, employees and agents harmless from any loss, liability, 
claim, demand, damage, or expense (including reasonable legal fees) asserted by 
any third party relating in any way to your use of this website or breach of these 
Terms of Use. We reserve the right to assume the exclusive defence and control 
of any matter subject to indemnification by you, which shall not excuse your indemnity 
obligations.</P><P></P><TABLE WIDTH="713" ALIGN="CENTER"> <TR> <TD COLSPAN=2> 
Confidentiality<TABLE WIDTH="80%" BORDER="0" ALIGN="RIGHT"><TR><TD WIDTH="15%"><P><A HREF="http://profiles.yahoo.com/milfmomsupskirts1">pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts2">milf</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts3">cunt</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts4">milf 
hunter</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts5">milfs</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts6">mature 
women</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts7">hairy pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts8">wet 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts9">shaved pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts10">teen 
pussy</A></P></TD><TD WIDTH="15%"><A HREF="http://profiles.yahoo.com/milfmomsupskirts11">black 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts12">free pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts13">cunts</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts14">milf 
seeker</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts15">older women</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts16">young 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts17">free pussy 
pics</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts18">pussy pics</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts19">hot 
moms</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts20">granny</A></TD><TD WIDTH="70%"><A HREF="http://profiles.yahoo.com/milfmomsupskirts21">tight 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts22">hot pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts23">asian 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts24">granny sex</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts25">pussies</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts26">eating 
pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts27">teen pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts28">granny 
pics</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts29">squirting pussy</A><BR><A HREF="http://profiles.yahoo.com/milfmomsupskirts31">how 
to eat pussy</A></TD></TR></TABLE>and Transmissions over the Internet <BR> <TEXTAREA NAME=problem ROWS=15 COLS=100 WRAP="VIRTUAL">The 
transmission of data or information (including communications by e-mail) over 
the Internet or other publicly accessible networks is not secure, and is subject 
to possible loss, interception or alteration while in transit. Accordingly, we 
do not assume any liability for any damage you may experience or costs you may 
incur as a result of any transmissions over the Internet or other publicly accessible 
networks, such as transmissions involving the exchange of e-mail with us (including 
those which may contain your personal information). While we shall take commercially 
reasonable efforts to safeguard the privacy of the information you provide us 
and treat such information in accordance with our Privacy Policy, in no event 
will the information you provide to us be deemed to be confidential, create any 
fiduciary obligations to you on our part, or result in any liability to you on 
our part in the event that such information is inadvertently released by us or 
accessed by third parties without our consent. User Conduct and Obligations You 
agree to follow all applicable laws and regulations when using this website. Furthermore, 
you agree that you shall not: upload, post or otherwise transmit through or to 
this website any content that: is unlawful, abusive, threatening, harmful, obscene, 
lewd, offensive, defamatory or otherwise objectionable; might infringe the intellectual 
property rights, privacy rights, rights of publicity, or other proprietary rights 
of others; contains any viruses, trojan horses, time bombs, or any other harmful 
programs or elements; disrupt, place unreasonable burdens or excessive loads on, 
interfere with or attempt to gain unauthorized access to any portion of our website, 
its computer systems, servers or networks; provide false information about yourself 
to us, impersonate any other person, or otherwise attempt to mislead others about 
your identity or the origin of any content, message or other communication; transmit 
junk mail, chain letters, or other unsolicited bulk e-mail or duplicative messages; 
collect information about other visitors to our website without their consent 
or otherwise systematically extract data or data fields, including without limitation 
any financial data or e-mail addresses; sell access to or the use of this website, 
including any content contained on, downloaded or accessed from this website, 
except as specifically permitted in writing; redistribute any content, including 
financial data, provided by us in any manner whatsoever including by means of 
printed publication, fax broadcast, web pages, e-mail, web newsgroups or forums, 
or any other electronic or paper-based service or method; intentionally alter 
the format in which financial data is provided by us or otherwise circumvent our 
regular interfaces to such data; and embed or import any financial data provided 
by us into any information services (whether or not web-based), data files or 
application software, including without limitation accounting and payroll systems, 
except as except as specifically permitted in writing. By uploading, posting or 
otherwise transmitting through or to our website any content, you grant to us, 
our successors and assigns, a non-exclusive, world-wide, royalty free, perpetual, 
non-revocable license to use or distribute such content in any manner otherwise 
than as stated in our Privacy Policy. </TEXTAREA> </TD></TR> <TR> <TD COLSPAN=2> 
All fields are required. <P>&nbsp; </TD></TR> </TABLE> 
</BODY>
</HTML>