{
  	"@context": {
		"@vocab": "https://schema.org/",
		"dcat": "http://www.w3.org/ns/dcat#",
        "dc":"http://purl.org/dc/elements/1.1/",
        "dct":"http://purl.org/dc/terms/", 
		"ecrro": "http://cor.esipfed.org/ont/earthcube/",
        "ecrr": "https://n2t.net/ark:/23942/g2"
	},
"@id":"http://n2t.net/ark:/23942/g2sw6d",
 "@type": [
 "CreativeWork",	"Product" ],
    "name": "XDR: External Data Representation Standard",
"subjectOf":[{"@type":"CreativeWork", "name":"RFC page", "url":"https://tools.ietf.org/html/rfc4506"}],
"description": "XDR is a standard for the description and encoding of data.  It is useful for transferring data between different computer architectures, and has been used to communicate data between such diverse machines as the SUN WORKSTATION*, VAX*, IBM-PC*, and Cray*. XDR fits into the ISO presentation layer, and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation.  The major difference between these two is that XDR uses implicit typing, while X.409 uses explicit typing.     XDR uses a language to describe data formats.  The language can only be used only to describe data; it is not a programming language. This language allows one to describe intricate data formats in a concise manner. The alternative of using graphical representations (itself an informal language) quickly becomes incomprehensible when faced with complexity.  The XDR language itself is similar to the C language. Protocols such as ONC RPC (Remote Procedure Call) and the NFS* (Network File System) use XDR to describe the format of their data.  The XDR standard makes the following assumption: that bytes (or octets) are portable, where a byte is defined to be 8 bits of data. A given hardware device should encode the bytes onto the various media in such a way that other hardware devices may decode the bytes without loss of meaning.  For example, the Ethernet* standard suggests that bytes be encoded in 'little-endian' style, or least significant bit first.  This document makes no technical changes to RFC 1832 and is published for the purposes of noting IANA considerations, augmenting security considerations, and distinguishing normative from informative references.",
"datePublished": "2006-05-01","editor":[{"@type":"Person","name":"M. Eisler"}],
"keywords": "data description",
"license": [{"@type":"CreativeWork","name":"not specified", "identifier":"undefined"}],
"version":"Mon May 01 2006 00:00:00 GMT-0700 (Mountain Standard Time)",
"audience": [{"@type":"Audience","audienceType":"Data Producers", "identifier":"http://cor.esipfed.org/ont/earthcube/AUT_0000001"},{"@type":"Audience","audienceType":"Data Users", "identifier":"http://cor.esipfed.org/ont/earthcube/AUT_0000002"},{"@type":"Audience","audienceType":"Technologists", "identifier":"http://cor.esipfed.org/ont/earthcube/AUT_0000004"},{"@type":"Audience","audienceType":"Data Managers", "identifier":"http://cor.esipfed.org/ont/earthcube/AUT_0000005"},{"@type":"Audience","audienceType":"Developers", "identifier":"http://cor.esipfed.org/ont/earthcube/AUT_0000006"}],
"about": [{"@type":"DefinedTerm","name":"Discipline-agnostic", "identifier":"http://cor.esipfed.org/ont/earthcube/ADO_0000188"}],
"isRelatedTo":[{"@type":"CreativeWork", "name":"obsoletes RFC1832", "url":"https://www.ietf.org/rfc/rfc1832.txt"}],
"mainEntity":[{
  "@type": "CreativeWork",
"url": "http://cor.esipfed.org/ont/earthcube/ECRRO_0000204",
"name": "Specification"
  },{
  "@type": "CreativeWork",
"url": "http://cor.esipfed.org/ont/earthcube/SPKT_0000009",
"name": "Metadata Vocabulary"
  }
],
"additionalProperty": [{
 "@type": "PropertyValue",
  "propertyID": "dc:BibliographicCitation",
"name": "Bibligraphic citation",
"value":"M. Eisler, editor, R. Srinivasan author,  2006-05,  XDR: External Data Representation Standard: IETF Request for Comments 4506, accessed 2021-01-05, https://tools.ietf.org/html/rfc4506."
  },
{
 "@type": "PropertyValue",
  "propertyID": "ecrro:ECRRO_0000138",
"name": "has maturity state",
"value": {
 "@type": "DefinedTerm",
"name": "In production",
"identifier": "http://cor.esipfed.org/ont/earthcube/MTU_0000002"
} 
  },
{
 "@type": "PropertyValue",
  "propertyID": "ecrro:ECRRO_0000219",
"name": "expected lifetime",
"value": {
 "@type": "DefinedTerm",
"name": "1 - 5 years",
"identifier": "http://cor.esipfed.org/ont/earthcube/ELT_0000003"
} 
  },
{
 "@type": "PropertyValue",
  "propertyID": "ecrro:ECRRO_0000600",
"name": "primary publication",
"value":"IETF RFC 4506,  https://tools.ietf.org/html/rfc4506"
  },
{
 "@type": "PropertyValue",
  "propertyID": "ecrro:ECRRO_0000218",
"name": "Stewardship",
"value":
 [{"@type":"Organization", "name":"Internet Engineering Task Force"}]
},
{
 "@type": "PropertyValue",
  "propertyID": "ecrro:ECRRO_0000017",
"name": "Usage",
"value": {
 "@type": "DefinedTerm",
"name": "Unknown",
"identifier": "http://cor.esipfed.org/ont/earthcube/UBA_0000004"
} 
  },
{
 "@type": "PropertyValue",
  "propertyID":"ecrro:ECRRO_0001301","name": "registration metadata",
"value": {
 "@type": "StructuredValue", "additionalType": "ecrro:ECRRO_0000156", "contributor": {
"@type": "Person",
"name":"Stephen M. Richard",
"identifier": "https://orcid.org/0000-0001-6041-5302"  },
"datePublished": "2021-01-05T19:40:41Z"
  } 
 } ]}