XML-binary Optimized Packaging (XOP) is a mechanism defined for the serialization of XML Information Sets ( infosets ) that contain binary data, as well as deserialization back into the XML Information Set.
7-617: XOP may refer to: XML-binary Optimized Packaging , a W3C recommendation for embedding binary data in XML External Operations in IGOR Pro, used to add data acquisition, manipulation and analysis features X-ray Oriented Programs, a widget-based driver software that is used as front-end interface optical simulations XOP instruction set , a computer instruction set introduced by AMD in 2009 A touhou -like game, but without
14-449: Is different from Wikidata All article disambiguation pages All disambiguation pages XML-binary Optimized Packaging XOP allows the binary data part of an XML Infoset to be serialized without going through the XML serializer. The XML serialization of an XML Infoset is text based, so any binary data will need to be encoded using base64 . Using XOP avoids this by extracting
21-599: Is essentially the original XML Infoset with the binary parts replaced by external references). The references in the XOP Infoset are represented using the "xop:Include" element. The XOP Infoset plus the extracted content can be serialized into a representation called the "XOP Package". The XOP Package can be sent or stored. To reconstitute the XML Infoset, the XOP Package is deserialized into the XOP Infoset plus
28-496: The Japanese. Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title XOP . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=XOP&oldid=541639702 " Category : Disambiguation pages Hidden categories: Short description
35-415: The binary data out of the XML Infoset so that the XML Infoset does not contain binary data and the binary data can be serialized differently. Therefore, XOP can reduce the size of the serialization (since base64 encoding has approximately a 33% size overhead) and (depending on how it is implemented) might allow processing efficiencies. This size increase results in extra resources needed to transmit or store
42-483: The data. XOP introduces another level of processing. Therefore, it introduces extra complexity and processing overheads. The representation of the XOP packages introduces some overhead. These are negligible when the binary data is large, but could be significant if the binary data is small. XOP operates on a single XML Infoset. The binary parts of the original XML infoset are extracted out, leaving an "XOP Infoset" (which
49-410: The extracted content, and then the extracted content is put back into the XML Infoset. XOP can be used with a number of different packaging mechanisms. A packaging mechanism defines how the XOP Infoset and the binary chunks are represented. The XOP specification defines how MIME can be used as a packaging mechanism. When used with MIME, the XOP Infoset is represented as XML in the root MIME part, and
#778221