- From: Michael Cooper <cooper@w3.org>
- Date: Wed, 20 Feb 2013 09:33:13 -0500
- To: James Craig <jcraig@apple.com>
- CC: Andy Heath <AndyHeath@axelrod.plus.com>, "public-indie-ui@w3.org Force" <public-indie-ui@w3.org>
- Message-ID: <5124DEA9.5000908@w3.org>
It is possible to send attachments to www-archive@w3.org. But normally that list is only used when no other list is suitable. I suggest just mailing your attachment to the public-indie-ui@w3.org list, where it is in context of existing discussion. If you didn't send it there because the file was too large for the list to accept, just let me know and I can go into an "approval queue" and allow the message through. Sending the attachment un-zipped is much easier for people to work with and it's possible to have a URI directly to the attachment for posterity. Yes, links like CSS would need to be absolute references, but I strongly recommend making any required CSS inline instead, and avoiding external dependencies. The reason is that W3C list messages are archived "forever", which translates to at least as long as W3C continues to exist. If a dependent resource becomes unavailable, it could become difficult for people to use the message in the archives. The need to access a years-old proposal comes up more often than you would think. All this said, if the content is complex enough that you're wanting to include CSS and possibly images, is an email attachment the right way to share the content? This sounds like the sort of thing one would put in the wiki. Then you can upload dependent images, and other people can contribute to the proposal (with full history for crediting and reversion available). If you need technical help with getting this content into the wiki, feel free to contact me privately and I'll help you get set up. Michael James Craig wrote: > On Feb 19, 2013, at 8:37 AM, Andy Heath <AndyHeath@axelrod.plus.com> wrote: > > >> Is it www-archive@w3.org I mail html attachments to ? >> > > I think that's correct. Michael? > > >> Will that pick up style sheets within w3c (I started with an existing w3 html and just changed the content). >> > > You should use absolute paths in the HTML and CSS. > > -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail cooper@w3.org <mailto:cooper@w3.org> Information Page <http://www.w3.org/People/cooper/>
Received on Wednesday, 20 February 2013 14:35:42 UTC