|
1 | | -<relaton-collection xmlns="https://open.ribose.com/relaton-xml"><title>Collection title</title><contributor><role type='author'/><organization><name>Ribose</name></organization></contributor><relation type='partOf'><bibdata type="standard" schema-version="v1.4.1"> |
| 1 | +<relaton-collection xmlns="https://open.ribose.com/relaton-xml"><title>Collection title</title><contributor><role type='author'/><organization><name>Ribose</name></organization></contributor><relation type='partOf'><bibdata type="standard" schema-version="v1.5.6"> |
2 | 2 | <title language="en" type="main" format="text/plain">The Holy Hand Grenade of Antioch</title> |
3 | 3 | <title language="en" type="abbrev" format="text/plain">Hand Grenade of Antioch</title> |
4 | 4 | <uri type="xml">spec/fixtures/documents/antioch.xml</uri> |
|
72 | 72 | </contributor> |
73 | 73 | <language>en</language> |
74 | 74 | <script>Latn</script> |
75 | | - <abstract language="en" script="Latn">Ever since Gutenberg discovered and patented ASCII and the corresponding "Courier New" font with its now-famous "ten" point size, artisans and artificers have striven to represent their views of the world in print.Similarly, starting from Darwin's discovery of the hippogriff and his subsequent registration of the creature as an International Trade Mark, men (and some women) have struggled to catalog the fabulous variety that is called "nature".This document supplies a number of representations of all manner of things (both elemental and hypothetical) supplied by some of our best collectors of curios and delivered in a manner that may well be reused by the cunning document author.</abstract> |
| 75 | + <abstract language="en" script="Latn" format="text/plain">Ever since Gutenberg discovered and patented ASCII and the corresponding "Courier New" font with its now-famous "ten" point size, artisans and artificers have striven to represent their views of the world in print.Similarly, starting from Darwin's discovery of the hippogriff and his subsequent registration of the creature as an International Trade Mark, men (and some women) have struggled to catalog the fabulous variety that is called "nature".This document supplies a number of representations of all manner of things (both elemental and hypothetical) supplied by some of our best collectors of curios and delivered in a manner that may well be reused by the cunning document author.</abstract> |
76 | 76 | <series type="main"> |
77 | 77 | <title language="en" script="Latn" format="text/plain">RFC</title> |
78 | 78 | <number>8140</number> |
|
90 | 90 | <doctype>internet-draft</doctype> |
91 | 91 | </ext> |
92 | 92 | </bibdata></relation> |
93 | | -<relation type='partOf'><bibdata type="standard" schema-version="v1.4.1"> |
| 93 | +<relation type='partOf'><bibdata type="standard" schema-version="v1.5.6"> |
94 | 94 | <title language="en" type="main" format="text/plain">RFC XML v3 Example: A Standard for the Transmission of IP Datagrams on Avian Carriers</title> |
95 | 95 | <title language="en" type="abbrev" format="text/plain">IP Datagrams on Avian Carriers</title> |
96 | 96 | <uri type="xml">spec/fixtures/documents/example.xml</uri> |
|
200 | 200 | </contributor> |
201 | 201 | <language>en</language> |
202 | 202 | <script>Latn</script> |
203 | | - <abstract language="en" script="Latn">This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised.</abstract> |
| 203 | + <abstract language="en" script="Latn" format="text/plain">This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised.</abstract> |
204 | 204 | <series type="main"> |
205 | 205 | <title language="en" script="Latn" format="text/plain">RFC</title> |
206 | 206 | <number>1000</number> |
|
239 | 239 | </contributor> |
240 | 240 | <language>en</language> |
241 | 241 | <script>Latn</script> |
242 | | - <abstract language="en" script="Latn">This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information.</abstract> |
| 242 | + <abstract language="en" script="Latn" format="text/plain">This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information.</abstract> |
243 | 243 | <series type="main"> |
244 | 244 | <title language="en" script="Latn" format="text/plain">RFC</title> |
245 | 245 | <number>1200</number> |
|
294 | 294 | </contributor> |
295 | 295 | <language>en</language> |
296 | 296 | <script>Latn</script> |
297 | | - <abstract language="en" script="Latn">This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</abstract> |
| 297 | + <abstract language="en" script="Latn" format="text/plain">This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</abstract> |
298 | 298 | <series type="main"> |
299 | 299 | <title language="en" script="Latn" format="text/plain">RFC</title> |
300 | 300 | <number>2010</number> |
|
335 | 335 | </contributor> |
336 | 336 | <language>en</language> |
337 | 337 | <script>Latn</script> |
338 | | - <abstract language="en" script="Latn">This document describes the use of 1993 ISO X.500 Standard protocols for managing the root context. Whilst the ASN.1 is compatible with that of the X.500 Standard, the actual settings of the parameters are supplementary to that of the X.500 Standard. This memo defines an Experimental Protocol for the Internet community.</abstract> |
| 338 | + <abstract language="en" script="Latn" format="text/plain">This document describes the use of 1993 ISO X.500 Standard protocols for managing the root context. Whilst the ASN.1 is compatible with that of the X.500 Standard, the actual settings of the parameters are supplementary to that of the X.500 Standard. This memo defines an Experimental Protocol for the Internet community.</abstract> |
339 | 339 | <series type="main"> |
340 | 340 | <title language="en" script="Latn" format="text/plain">RFC</title> |
341 | 341 | <number>2120</number> |
|
353 | 353 | <doctype>rfc</doctype> |
354 | 354 | </ext> |
355 | 355 | </bibdata></relation> |
356 | | -<relation type='partOf'><bibdata type="standard" schema-version="v1.4.1"> |
| 356 | +<relation type='partOf'><bibdata type="standard" schema-version="v1.5.6"> |
357 | 357 | <title language="en" script="Latn">The Holy Hand Grenade of Antioch</title> |
358 | 358 | <uri type="xml">spec/fixtures/documents/antioch.rfc.xml</uri> |
359 | 359 | <docidentifier type="Internet-Draft" primary="true">draft-camelot-holy-grenade-01</docidentifier> |
@@ -390,12 +390,12 @@ as well as "Spamalot", the musical inspired by the movie.</abstract> |
390 | 390 | <status> |
391 | 391 | <stage>Informational</stage> |
392 | 392 | </status> |
393 | | - <ext schema-version="v1.0.1"> |
| 393 | + <ext schema-version="v1.1.2"> |
394 | 394 | <doctype>rfc</doctype> |
395 | 395 | <flavor>ietf</flavor> |
396 | 396 | </ext> |
397 | 397 | </bibdata></relation> |
398 | | -<relation type='partOf'><bibdata type="standard" schema-version="v1.4.1"> |
| 398 | +<relation type='partOf'><bibdata type="standard" schema-version="v1.5.6"> |
399 | 399 | <title language="en" script="Latn">RFC XML v3 Example: A Standard for the Transmission of IP Datagrams on Avian Carriers</title> |
400 | 400 | <uri type="xml">spec/fixtures/documents/example.rfc.xml</uri> |
401 | 401 | <contributor> |
@@ -431,7 +431,7 @@ some cities, usually based upon a central hub topology.</abstract> |
431 | 431 | <status> |
432 | 432 | <stage>Published</stage> |
433 | 433 | </status> |
434 | | - <ext schema-version="v1.0.1"> |
| 434 | + <ext schema-version="v1.1.2"> |
435 | 435 | <doctype>rfc</doctype> |
436 | 436 | <flavor>ietf</flavor> |
437 | 437 | </ext> |
|
0 commit comments