Forwarded: Thu, 05 Jul 2001 15:07:31 -0400 Forwarded: John Yin Return-Path: msen@anabas.com Return-Path: Delivered-To: fox@csit.fsu.edu Received: from epimetheus.hosting4u.net (unknown [209.15.2.70]) by mailer.csit.fsu.edu (Postfix) with SMTP id 2B0D023A08 for ; Fri, 29 Jun 2001 15:55:49 -0400 (EDT) Received: (qmail 21837 invoked from network); 29 Jun 2001 19:55:48 -0000 Received: from capricornus.hosting4u.net (HELO anabas.com) (209.15.2.36) by mail-gate.hosting4u.net with SMTP; 29 Jun 2001 19:55:48 -0000 Received: from hizmet ([66.47.65.114]) by anabas.com ; Fri, 29 Jun 2001 14:55:46 -0500 Message-ID: <006201c100d5$709a02a0$9865fea9@hizmet> From: "mehmet sen" To: Cc: "John Yin" , Subject: object infos Date: Fri, 29 Jun 2001 12:55:24 -0700 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_005E_01C1009A.C38B62A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 This is a multi-part message in MIME format. ------=_NextPart_000_005E_01C1009A.C38B62A0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_005F_01C1009A.C38B62A0" ------=_NextPart_001_005F_01C1009A.C38B62A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I like to suggest that giving some more attention to objects' = information listing than fast Java API preparation might be more = useful.=20 Here, I list very preliminary listing. Please go over it at parallel and = check whether these informations are sufficient enough for JSP front end = functionality before fixing the preAPI. I will organize them more by = time. Mehmet P.S. I believe that JSP front end should not have context terminology = but concept. ------=_NextPart_001_005F_01C1009A.C38B62A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

I like to suggest that giving some more = attention=20 to objects' information listing than fast Java API preparation = might be=20 more useful.
Here, I list very preliminary listing. Please go over = it at=20 parallel and check whether these informations are sufficient enough for = JSP=20 front end functionality before fixing the preAPI. I will organize them = more by=20 time.

Mehmet

P.S. I believe that JSP front end = should not have=20 context terminology but concept.

------=_NextPart_001_005F_01C1009A.C38B62A0-- ------=_NextPart_000_005E_01C1009A.C38B62A0 Content-Type: text/plain; name="objectinfos.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="objectinfos.txt" COURSE OBJECT INFO COURSEID TITLE DESCRIPTION=09 OWNER STAFF (INSTRUCTOR(ID),...) LEVEL ( beginner,intermediate,advanced,...) LOCATION (please clarify this, URL, room, etc.) PRICE (when offering to an institution) STATUS (scheduled,active,cancelled,finished,...) VENDOR DATES (could be same as TIMES as below) STARTDATE,STOPDATE ACTUAL STARTDATE,ACTUAL STOPDATE ACCEPTBYDATE(nonsense with enrollments) TIMEZONE TIMEZONEOFFSET REFERENCES RELATEDURL+ ENROLLMENT CAPACITY PRICE (when offering to a student) ENROLLMENTDATES ENROLLMENT START DATE ENROLLMENT STOP DATE DROPDATE FINANCIAL DROP DATE -TIMEZONE etc (can be acquired from course) PREREQUISTS ENROLLMENTs=09 ENROLLMENTID (??) ENROLLMENT TIME STATUS ...there should be more here SESSIONs (will be same as current meeting[meeting has more info]) SESSIONID OWNER TITLE+ TYPE DESCRIPTION LOCATION(please clarify this, URL, room, etc.) REFERENCES RELATEDURL SIPURL PASSWORDs TIMES STARTTIME,STOPTIME, ACTUALSTARTTIME,ACTUALSTOPTIME ACCEPTBYTIME DURATION TIMEZONE TIMEZONEOFFSET STATE (STATUS, ...) PARTICIPATION (this may feed enrolment for summary) ACCEPTENCE (accepted,declined) ATTENDANCE (attended[duration,activetime,starttime,stoptime,...]) ...future gradings USERS (i think that our user info gathering is simpler than this) USERID PASSWORD (temporary or for efficiency) =09 PERSONAL NAMES FIRSTNAME,MIDNAME,LASTNAME =09 PREFIX,SUFFIX TITLES ([organization,primary,secondary*],..) ( we can remove org. = for simplicity) NICKNAME (can be more complicated but I believe this is enough for now) ORGANIZATION (strange here) CONTACT ORGANIZATION ADDRESS(STREET,EXTENTION,CITY,STATE,ZIP,COUNTRY) (can be in USPS = management complexity) EMAIL(PRIMARY,SECONDARY*) PHONE(COUNTRY,AREA,NUMBER) FAX ROLES=09 USERROLE (reserved) RELATIONS (i'll arrange more with security) GROUPS=20 USERGROUP(reserved) PAYMENT (please fill out some fields, credit card, bank, billing = address, etc. ;What will we have?) HOSTINGS INVITATIONS PREFERENCES ENEWS SECURITY(includes groups and passwords) =09 MEETINGS (similar to sessions) ------=_NextPart_000_005E_01C1009A.C38B62A0--