Re: RFCWiki comments and SVN Offer

david nicol wrote:
> it's a work in progress.  What do you need for XML support?  There are
> a lot of tags defined in the RFCXML standard, and I don't know if I
> should definie WikiMarkup for everything or just make editors embed
> the tags, with a reference listing them handy, and have the view
> component treat them right.

In terms of useful markup, the stuff that really needs to be put in marked 
fields is what appears in the <front> and <back> sections of the spec, 
because they are used for citation purposes. It shouldn't be too hard to put 
<section> and <t> tags in the appropriate places when every section is 
already being entered in a different box.

Further markup within the text probably doesn't need to be handled specially 
by the editor.

> an XML view is obviously high on the to-do list, so far I've
> concentrated on simple usability and the paragraph rearranging
> system.
> 
> What tools would we need for SVN access?

You would simply need a working version of Subversion, which can be obtained 
from <http://subversion.tigris.org/>, and is also included in most popular 
GNU/Linux distributions. A MS Windows client is also available through the 
download page.

For purposes of this work, you wouldn't need to learn much about SVN usage 
if you have basic working knowledge of CVS. It's just a matter of checking 
out a working copy, editing, updating, and committing (checking in). There's 
a very good tutorial in the online book, found at 
<http://svnbook.red-bean.com/>.

Sincerely,
Philip Miller

> On Fri, 2004-05-21 at 20:53, Philip Miller wrote:
> 
>>david nicol wrote:
>>
>>>So here's my announcement:
>>>
>>>[http://zarquon.advenge.com/RFCwiki/view?doc=AF the draft loaded into a
>>>shared editing environment] you will need to log in to see it, no
>>>salesmen will call. Reload after logging in.
>>>
>>>I will add editors to the ACL as needed.
>>
>>I'm logged in and looking at the edit page, so I assume any changes I make
>>can be saved.
>>
>>However, there appears to be a downside to this system: I don't see any
>>convenient way to generate clean XML sources. The XML format does indeed
>>have some very strong advantages: multiple output format generation,
>>consistent formatting of output forms, and ease of addition to citation
>>indexes of Internet Drafts.
>>
>>As I said before, I'm quite willing to give write access to the SVN
>>repository to the others working on this document, which would have the
>>added benefit of maintaining a complete revision history, so that if a
>>change is made that we later agree is undesirable, it's very easy to revert
>>it. Complete, dated history also provides protection for all of the
>>contributors and the product if there is ever a patent dispute.
>>
>>Philip Miller