all.htm
3.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
<html>
<head>
<title>Web Architecture</title>
</head>
<body>
<h1>Web Architecture</h1>
<p><em>Addressing and Data Formats</em>
<p>Dan Connolly<br>
<a href="http://www.w3.org/">W3C</a>
<p>WAPForum Meeting<br>
February 1998<br>
Fort Worth, TX
<h1>Overview</h1>
<ul>
<li>Architecture
<li>Addressing: URIs
<li>Data Formats: XML
<li>Q&A...
</ul>
<h1>Web Architecture</h1>
<ol>
<li>Addressing: URIs
<li>Protocols: HTTP, ...
<li>Data Formats: HTML, XML, ...
</ol>
<p><a href="http://www.w3.org/DesignIssues/">notes from '91</a>
<h1>Addressing: URIs</h1>
<ul>
<li>Jun '94: URI spec Informational <br>(RFC 1630)
<li>Dec '94: URL Proposed Standard <br>(RFC 1738, 1808)
<li>Aug '98: Common Syntax to Draft Standard <br>(RFC 2396)
</ul>
<h1>Addressing: Issues</h1>
<ul>
<li>Parsing, extensibility bugs
<li>Maintenance of the list of URI schemes
<br>guidelines
<li>Persistence (URNs, DOIs, rights management)
<li>Integrating TV, telephone
</ul>
<h1>Addressing: Opportunities</h1>
<p>1st class objects vs.
<ul>
<li>overuse of POST
<li>MIME x-types
<li>mailto: misnomer
</ul>
<p>"value of the network varies with the square of the number of resources"
<h1>Data Formats</h1>
<ul>
<li>HTML, plain text
<li>GIF, JPEG, ...
<li>Style Sheets: CSS, XSL
<li>XML
</ul>
<h1>Format Negotiation</h1>
<ul>
<li>In Theory: Client advertises capabilities
<br>Server optimizes response
<li>In Practice: Client advertises product codes
<br>Server kludges around bugs
</ul>
<h1>Format Negotiation</h1>
<ul>
<li>Lesson: evolution of capability list
</ul>
<h1>W3C Data Format Architecture: XML</h1>
<ul>
<li>Self-evident, self-similar structure
<br><em>no tag inference</em>
<li>Make HTML components usable by reference
</ul>
<h1>XML: past, present, future</h1>
<ul>
<li>Fall 1996: 1st Draft at SGML Conference
<li>Nov 1997: Proposed Recommendation
<li>Feb 1998: Recommendation
<li>June 1998: Continuing Work on XML
<li>Jan 1999: Namespaces Recommendation
</ul>
<h1>XML Applications</h1>
<ul>
<li>HTML Math (MathML)
<li>Synchronized Multimedia Integration Language (SMIL)
<li>Resource Description Framework (RDF)
<li>Scalable Vector Graphics (SVG)
</ul>
<h1>XML Namespaces</h1>
<ul>
<li>Address tag name collisions, ambiguity
<li>Namespaces are 1st class (addressable) resources
</ul>
<h1>RDF</h1>
<p>metadata infrastructure for...
<ul>
<li>Automated contract exchange
<li>Web structure analysis
<li>Bibliographic records (Dublin Core)
<ul>
<li>Persistence (availability guarantees, rights management)
</ul>
</ul>
<h1>XML Activity</h1>
<ol>
<li>XML Schema WG
<li>XML Linking WG
<li>XML Fragments WG
<li>XML Syntax WG
<li>XML Infoset WG
</ol>
<h1>XML Schemas</h1>
<ul>
<li>Provide DTD facilities in self-similar syntax
<li>Provide 1st-class module facility
<li>Integrate with modern data stores?
<li>Integrate with modern software development?
</ul>
<h1>XML Linking</h1>
<ul>
<li>modularize HTML linking
<li>link services, annotations, ...
<li>bring the web into the '70s
</ul>
<h1>XML Fragments</h1>
<ul>
<li>deal with fragments out of context
<li><em>update-grams?</em>
<li><em>packaging?</em>
</ul>
<h1>XML Syntax</h1>
<ul>
<li>profile
<li>maintenance
</ul>
<h1>XML Infoset</h1>
<ul>
<li>make the implicit data model explicit
</ul>
@@namespaces
@@XML linking and WML
@@XML profile, voyager profile
</body>
</html>