-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart D. Gathman wrote:
> I am supposed to write about SPF vs SID.  I thought it should go under
> "Related Solutions".

What I had in mind was an extra article whose sole focus is to lift the 
confusion over SPF and SID.  Many people think that they're the same or 
that SPF is an integral part of SID.  I wouldn't go into too much of the 
politics, though, just the facts.  I propose the page name "SPF vs Sender 
ID".

But what you wrote on the "Related Solutions" page so far is great!  I just 
wouldn't link to RFC 4408 directly, but to the "Specifications" page 
instead (we're going to have the XML and HTML versions there, too).

Oh, and I added a "Website/Style Guide" page[1] with a few formatting 
guidelines.  I've applied those formatting styles to the "Related 
Solutions" page.

> Ok, I created a Sitemap/Drafts page, then created a link to 
> "Related Solutions", not noticing that it wasn't a subpage.
> Sorry, my first time for this type of Wiki.  The Wiki
> only allows two levels, so I created "Drafts/Related Solutions" also,
> and copied to article so far to there.  But the article is already
> linked from Sitemap.

You don't have to create draft pages as sub-pages of "Drafts".  The 
concepts of "linking" and "location" are entirely separate, so a page 
isn't visible (except in the automatically generated page index) unless 
you link to it from somewhere.  You can create draft pages with their 
permanent name right away, and just have them be "#PRIVATE" and with no 
links pointing to them until the pages are done.

(I deleted the redundant "Drafts/Related Solutions" page.)

References:
 1. http://new.openspf.org/Website/Style_Guide

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEXxXewL7PKlBZWjsRAuZrAJ41WV9TeIpdUpvavdogVKCu6Vt5+ACgx0et
+rSSVIEC3zYaDLl/osc6yTc=
=8qj0
-----END PGP SIGNATURE-----

-------
To unsubscribe, change your address, or temporarily deactivate your 
subscription, 
please go to http://v2.listbox.com/member/[EMAIL PROTECTED]

Reply via email to