Notifier Notes 4/15/97 (lost mod 4/30)

The basic concept is to provide a utility such that the user runs a
program which (via kerberos) requests service.  the service is to provide
a list of files which have been added or modified.

possibility: the client (or server?) builds a web page of links
(tailored to the user's spec) pointing to pages.

info provider:
	provides "tag" (some kind of group name), "subject" line, and
	file location (a url by any other name)

	could send mail (parse into tag, subject, and data)

how do we "start" a tag?  I suspect this should be a separate operation.

user:
	getnotes - request personalized collection be constructed.
		if one url, just display it.
		if multiple, make up page of links
		if very large, make up page of pages?
		should allow various personalization features.
	might allow
	getnotes nnn --- to get only nnn links at a shot
	getnotes tag --- to get new links for tag

	profilenotes - check out the list of "tags" currently in use,
		set up personal requests, and so forth.  should allow
		me (the user) to prioritize or arrange the tags.

i.e., use browsers, web, and afs files (html, text, etc.) as delivery
system.  build onto that the additional superstructure to make putting
up notes and getting them fairly easy.

setting up a list -- probably a one-word tag.  allow definition of default
"lifetime" for messages.  also -- open posting?  limited to xxx, yyy, zzz?

posting to the list -- list name, start date (default now), end date
(default to list length), one line "subject", location of text or text

(if you allow them to submit text, server must format it, make page,
and then clean up after end date.  simpler for first cut is to only
accept url's)

4/29

client-server interaction for creating list:
	kerberized verification against authorized list?
	name of list
	start of life cycle (when to announce it)
	end of life cycle (when to kill it)
	default message life (in days?)
	type of list - public posting (anyone can post to it)
		       authorized list posting (only members of list)
		       public readership (anyone can read)
		       authorized list reading (only members of list)

should have a delete list and a modify, too.

client-server interaction for posting
	kerberized
	name of list
	start date (defaults to now/tomorrow)
	end date (defaults to start + list default duration)
	"subject" line
	URL for content

optional: allow user to input text, save it and URLize it?
optional: add a server to accept mail for public posting lists

client-server interaction for reading
	kerberized

4/30

design issue - does client keep profile and build list "on the fly" or
does server keep data and build lists as data feeds in?  e.g. does
client say "give me today's list for xyz" and then construct page
locally?  or does client just say "I'm joe, give me joe's lists" and
get a page/data/location fed to it?

In any case - list has entries, person has multiple lists...

are there lists which must have private membership (i.e. limitatations
on reading)?  of course.  (so I go back and modify the list creation
interaction)

6/9/97 sleeping on the job

makelist -- change, delete?

	name
	startdate (default: now?)
	enddate (default: now + x?)
	submission lifetime
	submit (open, list)
	read (open, list)

submit entry -- change, delete?

	listname
	line <- text or URL/link
	startdate (default: NOW)
	enddate (default: start + lifetime)

getnewlists(since???)

	name
	start
	end

=save local if desired

getentry(list, since)

note: should we let the user make their own local lists and entries?
I.e., with the structure in place, letting the user send themselves
notes seems sensible?