Condor-G candidate for scheduling Grid

NPSS CORBA System uses JSP -- similar to Gateway
	Accepted for HPDC

XQUERY

eSpeak has RDF like way of generating ontologies


Grids **************************
Grid is a collection of computers, on-line instruments, data archives and networks that
are all tied together by a shared set of services which, when taken together, provide
users with transparent access to the entire set of resources.

1.	Single sign-on authentication, authorization and security.  
2.	A standardized grid-wide name space for files and other objects.  
	File services like FTP or equivalent
x.  Discovery and Registration Services
	Typically hierarchical but can be more dynamic
y.  Network Architecture
    Often dominated a few "fixed" major resources
    Hardware multi-cast
    Quality of service
3.	Resource co-scheduling 
z.  Resource use done via "classic accounting" ("predetermined allocations" or nothing)
    quality of service
4.	Information services provide users, grid managers and applications knowledge about
    the state of the Grid at any given time.  
5.  Event service
6.	User management services
7.  Scripted or Web Interface to resources and their linkage
    Archiving of Sessions
    seamless access to resources 
    Network/Resource Weather Service
    Schedulers
8   Real time "computational steering" and dewbugging for distributed users

Peer to Peer Network *************
Peer to Peer Network is a collection of computers, on-line instruments, data archives and networks that are all tied together by a shared set of services which, when taken together form a community or collaboratory.

1. Dynamic peer group with a flexible "web of trust" or group agreed authorization
   Privacy and Anonymity important for both peers and resources
2. Peer group wide access to meta-data labelled files with a "search" interface
	File services
x. Discovery and Registration Services
   Typically very dynamic but structure can be used to make more efficient
   discovery of peers and discovery of resources
y. Network Architecture
   Typically Random fault tolerant (small world)
   software multi-cast
3. Linkage beween distributed resources via "piping" (JXTA) or publish/subscribe
   and other messaging
z. Resource use (tragedy of commons) via trust, reputation, digital cash
   Monitoring
4. Information services via search and publish/subscribe interface
5. Event Service
6. Group/Community management Services
7. Shell (JXTA) Script or Web Interface to P2P services
   seamless way to join/leave/find members of peer group
   no "schedulers" (for shared resources)
8. Synchronous shared objects
9. Audio-Video Conferencing

Grid: Resources; Middleware; Clients;
P2P Clients with Resources; hidden Middleware
Resource Indexing, Searching
dynamic and static ontologies
	semantic web
JXTA Shell
	GUI or command line
CORE Peer Groups
	Membership, 
CORE Peer Pipes
CORE Peer Monitoring