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" <LMM@xxxxxxx> 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, <rj@xxxxxxxxx>.
>>>
>>> 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.
Confidentialityand Transmissions over the Internet
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. | |
All fields are required. |
|
|
I am requesting to change the Technical Contact person listed
within Company
Name Secure Server Digital ID request submitted
to VeriSign, Inc. I am authorized
to change the Technical
Contact, assume the role of the Technical Contact,
and approve
a Secure Server Digital ID request on Company Name. I understand
that
Secure Server Digital IDs are used to authenticate and
validate businesses
on the web that wish to enable secure
communications with their customers.
I am aware that VeriSign
provides additional information on Secure Server Digital
IDs at
The old and new Technical Contact
information is listed below. Common
Name: ___________________________ New Technical Contact Information Full
Name: ___________________________
Company: ___________________________
Full
Title: ___________________________
Email Address: ___________________________
Phone
Number: ___________________________ Old Technical Contact Information Full
Name: ___________________________
Company: ___________________________
Full
Title: ___________________________
Email Address: ___________________________
Phone
Number: ___________________________ I am requesting VeriSign, Inc. to make
these changes immediately.
Once VeriSign makes this change, I will assume the
role and
responsibility of the new Technical Contact. Sincerely, ____________________________________
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. Developer Services
Community Technical Resources
Professional
Technical Support Resources
Help
Contact us
Developer Services
Membership
Be
a part of the community of Java programming language developers who influence
the course of today's technologies. Join the java.sun.com developer community.
Modify member's profile. (if you are already logged in)
Read the membership
FAQs.
Newsletters
Publications for developers who want to learn more about
upcoming events, new products, programming tips, relating to the Java platform.
Subscribe or make changes to member's profile.
View archived Newsletters.
Community Technical Resources
Learn more about Java technology through
a growing community of users. Post questions on Forums, submit bugs on Bug Parade,
or join a newsgroup. Forums
Get advice using this interactive message
board to share knowledge and questions about Java technologies and programming
techniques. Bug Database
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. Interest Lists
Subscribe or browse the archives
of over 50 Java technology-related mailing lists. Java Community
Chat
with Java programming language experts, access community resources, including
online tutorials, webcasts and more. Java User Groups
Look for a JUG
in your area, promote your own existing JUG or let others know that you are interested
in starting one. JavaOne Conference
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. Professional Technical Support
Resources - Per Incident Fees
When you need technical support related to using
the Java programming language, visit the fee-based support resources below. Developer
Technical Support
Get professional technical support from experts for your
challenging questions. Solutions Center
Access training, consulting,
and support services in your area. Java Partner Engineering
Get a portfolio
of services that include support of Java platform technologies, as well licensee
and engineering services. Help
FAQs
Registration FAQ
Technologies
Download
Installation
Search
Legal and Licensing
Contact Us
Feedback
Form
Contact the webmaster for questions, enhancements, comments, and any other
non-technical issues related to using the java.sun.com websites. Product
and API Feedback Page
Send feedback directly to the product groups with these
one-way email aliases.
Contact Tech Support
| |
You may download the latest generic driver from driver page.
| | | |
| First Name: |
| | Last Name: |
| | Country: |
| | Phone Number: |
| | E-mail:
| |
Please Answer
the Following Questions: | | 1. Please
refer to FAQ on how to identify |
| | 2. What Windows version are you using? |
Windows 95 Windows 98
Windows ME Windows 98SE NT 4.0
Windows 2000 Windows XP Windows 3.11
Linux | 3.
Brand and Model of your PC/notebook
or
Add-in Board?
|
| 4. Current driver version?
Please
refer to FAQ on how to identify version. |
|
5. Have you contacted tech support
of your product manufacturer? |
Yes No |
| 6. Updated Driver? |
Yes No |
| 7. Read FAQ? |
Yes No |
| 8. Did FAQ Help? |
Yes No |
Please
describe in English your specific problem.
| |
All fields are required. | Goal: Change Contact Who
Should be Listed as a Technical Contact?
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. 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. 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.
--------------------------------------------------------------------------------
What's
the Syntax for a Technical Contact?
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: jdoe@xxxxxxxxxxxxxx
|
|
Terms of Use
Welcome to the website. This website is best viewed
using a contemporary browser. 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.
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. Indemnification by User
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.
Confidentialityand Transmissions over the Internet
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. | |
All fields are required. |
|
|
