Re: Dev Guide + IP Schema Design DocBook conversion (was Re: ETX Protocol Spec)

Hey Chase (et al.),

On Sat, 17 Apr 2004, Chase Phillips wrote:

> On Sat, 17 Apr 2004, Chase Phillips wrote:
>
> > Dave, I had planned to convert the documents you'd posted to the list
> > recently.  Is this also something in which you're interested?
>
> I've converted two more documents: the Developer's Guide and the Network
> IP Schema Design.  I've also updated the ETX Protocol Spec to match some
> conventions I've introduced.  I took a stab at suggesting a doc numbering
> schema a la other technical projects (think IETF's RFC, Jabber's JEP).
> The addition was a numbering scheme for each document with a prefix of
> "CTR".  CTR stands for "CUWiN Technical Report".

I like this schema.  It will help us to organize content and will greatly
help when referring back to stuff.  My main question is how would these
things interact with our Subversion repositories and with versioning?

> For example, the Developer's Guide is entitled "CTR-0001: Developer's
> Guide" since it is (what I understand to be) the first technical write-up
> listed under the CUWiN Documents page.  The second write-up is "CTR-0002:
> Network IP Schema Design".  The title of the ETX Spec has changed to
> reflect its third listing.  I assume "OSI Grant Text" isn't considered a
> technical write-up but I'm not ruling that possibility out until I hear
> from Sascha or its other authors.

This sounds fine -- I think that we should probably have a "Technical
Reports" section and a "Useful Resources" section.

> I thought this CTR concept would make navigating and understanding the
> whole of the write-ups easier but maybe I'm off.  What do others think of
> the idea?

I'm in favor of this as long as we can integrate it with our current
version control system.  Ideally, I would like to see this information
automatically update to the website, but we may still be a bit away from
that yet.

What do others think?

--Sascha

> Developer's Guide
> -----------------
>
>   Note:
>     I assumed the prompt was tcsh based on some remarks in the guide.  Let
>     me know if I'm off on this.
>
>   Input XML source
>     http://shepard.ameth.org/developers-guide/Developers-Guide.xml
>
>   Chunked XHTML
>     http://shepard.ameth.org/developers-guide/
>
>   Single XHTML
>     http://shepard.ameth.org/developers-guide/Developers-Guide.html
>
>   PDF
>     http://shepard.ameth.org/developers-guide/Developers-Guide.pdf
>
>   Text
>     http://shepard.ameth.org/developers-guide/Developers-Guide.txt
>
> Network IP Schema Design
> ------------------------
>
>   Input XML source
>     http://shepard.ameth.org/network-ip-schema/Network-IP-Schema-Design.xml
>
>   Chunked XHTML
>     http://shepard.ameth.org/network-ip-schema/
>
>   Single XHTML
>     http://shepard.ameth.org/network-ip-schema/Network-IP-Schema-Design.html
>
>   PDF
>     http://shepard.ameth.org/network-ip-schema/Network-IP-Schema-Design.pdf
>
>   Text
>     http://shepard.ameth.org/network-ip-schema/Network-IP-Schema-Design.txt
>
> _______________________________________________
> CU-Wireless mailing list
> [email protected]
> http://lists.cu.groogroo.com/cgi-bin/listinfo/cu-wireless
> Project Page: http://cuwireless.ucimc.org
>

-- 
Sascha Meinrath
Project Manager & President      *      Project Manager
Acorn Active Media Foundation   ***     Eggplant Active Media
www.acornactivemedia.com         *      www.eggplantmedia.com
_______________________________________________
CU-Wireless mailing list
[email protected]
http://lists.cu.groogroo.com/cgi-bin/listinfo/cu-wireless
Project Page: http://cuwireless.ucimc.org