Conference turris::languages

This notefile is currently named LANGUAGES.NOT.  It occurred to me that,
as part of the conversion, a more descriptive file-name could be chosen,
in keeping with evolving VAX Notes conventions.

Two possibilities come to mind:

	PROGRAMMING_LANGUAGES.NOTE

	COMPUTER_LANGUAGES.NOTE

Comments and other suggestions are welcome.

-- Ward

Let's not get fancy here.  I'd rather be able to know that the filespec
FOO""::SYS$NOTES:BAR.NOT will change systematically to 
FOO""::NOTES$LIBRARY:BAR.NOTE, than screw around perfecting the filespec,
especially when people other than system managers shouldn't care.

RE: .2

Most public notefiles were named when we were limited to 9-character
file names.  Since a conference file name becomes the default conference
name in a user's VAX Notes Notebook, the emerging convention is to give
VAX Notes conferences accurate file names.

By the way, with VAX Notes the appropriate file-spec for a conference
located in the NOTES$LIBRARY directory is:

	nodename::conferencename

-- Ward

Re .-1:

Sorry, I didn't know that VAX Notes was throwing away features like note
file titles that older software supported.

I agree that applying the appropriate defaults to FOO""::NOTES$LIBRARY:BAR.NOTE
leaves the filespec FOO::BAR.
				/AHM/THX

By the way, I suppose PROGRAMMING_LANGUAGES is more colloquial.  After all,
I belong to SIGPLAN, not SIGCLAN.
				/AHM/THX

        .4: Attempting a nasty cut at VAX Notes, huh?  "Throwing
        away" what features?
        
        When you ADD ENTRY to add a conference to your notebook,
        the conference file name becomes the default conference name
        in your notebook (equivalent to the old NOTARY).  You can
        change the name if you like, but it makes sense for the default
        to be meaningful.  Note file titles, in any case, have nothing
        to do with it... they don't appear until you OPEN the
        conference.  VAX Notes certainly does have equivalent conference
        titles.
        
        	/dave

I'm not looking forward to the Enet conversion, but I do like the new
features available in VAX Notes (it's much easier to find information!).

It'd be simpler of converted files retained their names across the
mass conversion.  If a name change is desired, that can happen with
less confusion either before or after the conversion.

One problem with having long descriptive notefile names is that folks
will be more likely to create shorter names for them in their notebooks,
and there'll be some confusion in casual conversions, since they'll have
different names for different people.

I strongly suggest leaving the title alone.

Let's not preclude people on non-Vax systems from reading this file.
The change is more likely to CAUSE confusion than clear any up ("what happened
to LANGUAGES.  It doesn't seem to be there anymore").   I also don't want
to have to type a longer name (or have to learn how to abbreviate it.)

	db

You typically won't ever have to type it - you can just position the
cursor to the entry in your "notebook" and press a function key.  This
ability isn't there yet except in Neil's NOTES_SELECT modification, but
it will be there soon.
				Steve

Re .-1:

I thought that arrow was there for a reason.
				/AHM/THX

Re: .8

Using a longer conference name will not preclude access of the conference
from non-VAXen.  The only thing that precludes access is lack of a user
agent except for VMS.  When (if) other user agents are built they need to
allow long conference names.  Since conference names will not be treated
as file names but as tokens to pass to remote servers there should be no
hardship for the user agents to support this.

I would prefer to see longer, more descriptive and less cryptic names for
notesfiles and conferences.
						B.J.