71:. It was also to be possible to obtain a URC from a URN by the use of a resolving service. The design goals of URCs were that they should be simple to use, easy to extend, and compatible with a wide range of technological systems. The URC syntax was intended to be easily understood by both humans and software.
87:
link and meant to help users decide if the link might be interesting. The working group later changed the acronym expansion to
Uniform Resource Characteristic, intended to provide a standardized representation of document properties, such as owner, encoding, access restrictions or cost. The group
88:
discussed URCs around 1994/1995, but it never produced a final standard and URCs were never widely adopted in practice. Even so, the concepts on which URCs were based influenced subsequent technologies such as the
244:
80:
29:
61:
360:
67:
The use of a URC would allow the location of a Web resource to be obtained from its standard name, via the use of a
355:
17:
83:
within the IETF URI working group as a small package of metadata elements (which became the ERC) to accompany a
93:
41:
334:
57:
121:
49:
53:
33:
251:. Proceedings of the International Conference on Dublin Core and Metadata Applications 2001.
365:
8:
199:
311:
318:
174:
170:
117:
146:
68:
349:
330:
48:. URC metadata was envisioned to include sufficient information to support
45:
223:
262:
89:
79:
The term "URC" was first coined as
Uniform Resource Citation in 1992 by
248:
84:
37:
224:"Proceedings of the Twenty-Fifth Internet Engineering Task Force"
284:
338:
322:
288:
230:
203:
178:
150:
125:
175:"Encoding and Use of Uniform Resource Characteristics"
144:
285:"Functional Requirements for Uniform Resource Names"
263:"Uniform Resource Characteristics/Citations (URCs)"
198:Hoffman, Paul E.; Daniel, Ron Jr. (21 April 1995).
283:Sollins, Karen; Masinter, Larry (December 1994).
347:
282:
317:Daniel, Ron Jr.; Allen, Terry (16 June 1995).
115:
335:"How Roy would Implement URNs and URCs Today"
249:"A Metadata Kernel for Electronic Permanence"
197:
316:
111:
109:
64:in the mid-1990s, but were never adopted.
329:
169:
145:IETF URI Working Group (14 April 1994).
106:
348:
243:
265:. UKOLN Metadata Group. 10 June 1998
13:
14:
377:
305:
42:Uniform Resource Identifier (URI)
233:. 16 November 1992. p. 503.
147:"URN to URC resolution scenario"
122:"URC Scenarios and Requirements"
22:Uniform Resource Characteristic
312:IETF URC working group charter
276:
255:
237:
216:
191:
163:
138:
94:Resource Description Framework
58:Uniform Resource Locator (URL)
1:
99:
7:
319:"An SGML-based URC Service"
54:Uniform Resource Name (URN)
10:
382:
200:"Trivial URC Syntax: urc0"
74:
60:. URCs were proposed as a
44:, a string identifying a
361:Technical specifications
356:History of the Internet
50:persistent identifiers
120:(21 November 1994).
52:, such as mapping a
20:specifications, a
171:Mealling, Michael
118:Mealling, Michael
116:Daniel, Ron Jr.;
69:resolving service
36:representing the
373:
342:
326:
299:
298:
296:
295:
280:
274:
273:
271:
270:
259:
253:
252:
247:(January 2001).
241:
235:
234:
228:
220:
214:
213:
211:
210:
195:
189:
188:
186:
185:
167:
161:
160:
158:
157:
142:
136:
135:
133:
132:
113:
381:
380:
376:
375:
374:
372:
371:
370:
346:
345:
333:(7 July 1995).
308:
303:
302:
293:
291:
281:
277:
268:
266:
261:
260:
256:
242:
238:
226:
222:
221:
217:
208:
206:
196:
192:
183:
181:
173:(8 July 1994).
168:
164:
155:
153:
143:
139:
130:
128:
114:
107:
102:
77:
12:
11:
5:
379:
369:
368:
363:
358:
344:
343:
327:
314:
307:
306:External links
304:
301:
300:
275:
254:
236:
215:
190:
162:
137:
104:
103:
101:
98:
76:
73:
9:
6:
4:
3:
2:
378:
367:
364:
362:
359:
357:
354:
353:
351:
340:
336:
332:
331:Fielding, Roy
328:
324:
320:
315:
313:
310:
309:
290:
286:
279:
264:
258:
250:
246:
240:
232:
225:
219:
205:
201:
194:
180:
176:
172:
166:
152:
148:
141:
127:
123:
119:
112:
110:
105:
97:
95:
91:
86:
82:
72:
70:
65:
63:
62:specification
59:
56:to a current
55:
51:
47:
43:
39:
35:
31:
27:
23:
19:
292:. Retrieved
278:
267:. Retrieved
257:
239:
218:
207:. Retrieved
193:
182:. Retrieved
165:
154:. Retrieved
140:
129:. Retrieved
78:
66:
46:Web resource
25:
21:
15:
366:URI schemes
245:Kunze, John
90:Dublin Core
350:Categories
294:2013-03-07
269:2022-02-06
209:2013-03-07
184:2013-03-07
156:2013-03-07
131:2022-02-06
100:References
81:John Kunze
34:characters
85:hypertext
38:metadata
75:History
28:) is a
30:string
227:(PDF)
40:of a
339:IETF
323:IETF
289:IETF
231:IETF
204:IETF
179:IETF
151:IETF
126:IETF
92:and
18:IETF
32:of
26:URC
16:In
352::
337:.
321:.
287:.
229:.
202:.
177:.
149:.
124:.
108:^
96:.
341:.
325:.
297:.
272:.
212:.
187:.
159:.
134:.
24:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.