Topic

• ❑ TAG Directions
  • ❑ Maintenance of webarch
    • ❑ Keeping Existing Web (shared information space) healthy
      • ❑ network effects: one web, not 2 or N
    • ❑ Educational resources
  • ❑ (httpRange-14 gets done 1st)
  • ❑ URIs
    • ❑ Web Services
      • ❑ URIs for WS
      • ❑ abstractComponentRefs-37
      • ❑ endPointRefs-47
    • ❑ URNsAndRegistries-50
    • ❑ URIGoodPractice-40
    • ❑ rdfURIMeaning-39
    • ❑ IRIEverywhere-27
    • ❑ metadataInURI-31
    • ❑ DerivedResources-43
  • ❑ Security
    • ❑ Authentication
      • ❑ Don't use passwords in the clear
    • ❑ Ajax
    • ❑ Principle of Least Power; executable stuff
  • ❑ Semantic Web
    • ❑ Using URIs for anything, not just for pages
    • ❑ Merging Graphs
    • ❑ Looking stuff up
  • ❑ Versioning/Extensibility
    • ❑ Namespaces + XML + Languages
  • ❑ P2P
    • ❑ should bittorrent get its own URI scheme, or should it back the http: scheme? (schemeProtocols-49)
    • ❑ Are GET/PUT/POST/DELETE sufficiently important that P2P systems should support them specially?
  • ❑ Streaming
    • ❑ do media types make sense for streamed video?
    • ❑ (proposed) best practice: put the access information in the URI, not in a little file pointed to by a URI. don't do http://../.ram; do rtsp:...
  • ❑ Web Applications
    • ❑ Flash, Avalon, ...
    • ❑ Ajax
  • ❑ Side effects, user identity, state, context
  • ❑ XML entities
    • ❑ SOAP vs DTD
  • ❑ A layering (NM 2003)
    • ❑ Web of Names
    • ❑ Web of widely deployed URI schemes
    • ❑ RESTful Web - Get/Post
    • ❑ HTTP/HTTPs Web
    • ❑ Web of widely deployed media types (i.e. the browsable web)