Data exchange

From Wikipedia, the free encyclopedia

Template:Short description Data exchange is the process of moving data from one information system to another. It often involves transforming data that is native to the source system into a form that is consumable by the target system or to a standardized form that is consumable by any compatible system. In particular, data exchange allows data to be shared between computer programs.

Data exchange is similar to data integration except that data may be restructured with possible loss of content. There may be no way to transform a particular collection based on exchange constraints. Conversely, there may be multiple ways to transform the data, in which case one option must be identified in order to achieve compatibility between source and target.

There are two main types of data exchange: broadcast and peer-to-peer (a.k.a. unicast).[1] For broadcast, data is transmitted simultaneously to all consumers. Just as a conference call, all participants get the same information from the speaker at the same time. [2] For peer-to-peer, data is sent to a single receiver, defined by a specific address. For example, a letter goes to just one mail box.[3]

Single-domain

In some domains, a multiple source and target schema (proprietary data formats) may exist. An exchange or interchange format is often developed for a single domain, and then necessary routines (mappings) are written to (indirectly) transform/translate each and every source schema to each and every target schema by using the interchange format as an intermediate step. That requires less work than writing and debugging the many routines that would be required to directly translate each source schema directly to each target schema.

Examples of these transformative interchange formats include:

  • Standard Interchange Format for geospatial data;
  • Data Interchange Format for spreadsheet data;
  • Open Document Format for spreadsheets, charts, presentations and word processing documents;
  • GPS eXchange Format or Keyhole Markup Language for describing GPS data;
  • GDSII for integrated circuit layout.

Representation

A data exchange (a.k.a. interchange) language defines a domain-independent way to represent data.[4] These languages have evolved from being markup and display-oriented to support the encoding of metadata that describes the structural attributes of the information.[5]

Practice has shown that certain types of formal languages are better suited for this task than others, since their specification is driven by a formal process instead of particular software implementation. For example, XML is a markup language that was designed to enable the creation of dialects (the definition of domain-specific sublanguages).[6] However, it does not contain domain-specific dictionaries or fact types. Beneficial to a reliable data exchange is the availability of standard dictionaries-taxonomies and tools libraries such as parsers, schema validators, and transformation tools.[citation needed]

XML

The popularity of XML for data exchange on the World Wide Web has several reasons. First of all, it is closely related to the preexisting standards Standard Generalized Markup Language (SGML) and Hypertext Markup Language (HTML), and as such a parser written to support these two languages can be easily extended to support XML as well. For example, XHTML has been defined as a format that is formal XML, but understood correctly by most (if not all) HTML parsers.[6]

YAML

YAML was designed to be human-readable and authored via a text editor with notion similar to reStructuredText and wiki syntax. YAML 1.2 also includes a shorthand notion that is compatible with JSON, and as such any JSON document is also valid YAML; this however does not hold the other way.[7]

REBOL

REBOL was designed to be human-readable and authored via a text editor. It uses a simple free-form syntax with minimal punctuation and a rich set of data types (such as URL, email, date and time, tuple, string, tag) that respect common standards. It is designed to not need any additional meta-language, being designed in a metacircular fashion which is why the parse dialect used for definitions and transformations of REBOL dialects is also itself a dialect of REBOL.[8] REBOL was used as a source of inspiration for JSON.[9]

Gellish

Gellish English is a formalized subset of natural English (language), which includes a simple grammar and a large, extensible dictionary (taxonomy) that defines the general and domain specific terminology, whereas the concepts are arranged in a hierarchy, which supports inheritance of knowledge and requirements. The dictionary also includes standardized fact types. The terms and relation types together can be used to create and interpret expressions of facts, knowledge, requirements and other information. Gellish can be used in combination with SQL, RDF/XML, OWL and various other meta-languages. The Gellish standard is a combination of ISO 10303-221 (AP221) and ISO 15926.[10]

List

The following describes and compares popular data exchange languages.

Name Schemas Flexible Semantic verification Dictionary Information Model Synonyms and homonyms Dialecting Web standard Trans-formations Light-weight Human readable Compatibility
Template:Rh class="table-rh" |RDF YesPage Template:Citation/styles.css has no content.[1] Yes Yes Yes Yes Yes Yes Yes Yes Yes Partial Subset of Semantic web
Template:Rh class="table-rh" |XML YesPage Template:Citation/styles.css has no content.[2] Yes No No No No Yes Yes Yes No Yes subset of SGML, HTML
Template:Rh class="table-rh" |Atom Yes Unknown Unknown Unknown No Unknown Yes Yes Yes No No XML dialect
Template:Rh class="table-rh" |JSON No Unknown Unknown Unknown No Unknown No Yes No Yes Yes subset of YAML
Template:Rh class="table-rh" |YAML NoPage Template:Citation/styles.css has no content.[3] Unknown Unknown Unknown No Unknown No No NoPage Template:Citation/styles.css has no content.[3] Yes YesPage Template:Citation/styles.css has no content.[4] superset of JSON
Template:Rh class="table-rh" |REBOL YesPage Template:Citation/styles.css has no content.[7] Yes No Yes No Yes Yes No YesPage Template:Citation/styles.css has no content.[7] Yes YesPage Template:Citation/styles.css has no content.[5]
Template:Rh class="table-rh" |Gellish Yes Yes Yes YesPage Template:Citation/styles.css has no content.[8] No Yes Yes ISO No Yes PartialPage Template:Citation/styles.css has no content.[6] SQL, RDF/XML, OWL
Columns
  • Schemas – Whether supports representing domain specific data structure definition
  • Flexible – Whether supports extension of the semantic expression capabilities without modifying the schema
  • Semantic verification – Whether supports semantic verification of the correctness of expressions in the language
  • Dictionary – Whether includes a dictionary and a taxonomy (hierarchy) of concepts with inheritance
  • Information model – Whether supports an information model
  • Synonyms and homonyms – Whether supports the use of synonyms and homonyms in expressions
  • Dialecting – Whether is available in multiple natural languages or dialects
  • Web standard – Whether is standardized by a recognized body
  • Transformations – Whether includes a translation to other standards
  • Lightweight – Whether a lightweight version is available
  • Human readable – Whether expressions are understandable without training[11]
  • Compatibility – Which other tools can be used or are required

See also

Notes

  1. Page Template:Citation/styles.css has no content.^ RDF is a schema-flexible language.
  2. Page Template:Citation/styles.css has no content.^ The schema of XML contains a very limited grammar and vocabulary.
  3. Page Template:Citation/styles.css has no content.^ Available as an extension.
  4. Page Template:Citation/styles.css has no content.^ In the default format, not the compact syntax.
  5. Page Template:Citation/styles.css has no content.^ The syntax is fairly simple (the language was designed to be human-readable); the dialects may require domain knowledge.
  6. Page Template:Citation/styles.css has no content.^ The standardized fact types are denoted by standardized English phrases, which interpretation and use needs some training.
  7. Page Template:Citation/styles.css has no content.^ The Parse dialect is used to specify, validate, and transform dialects.
  8. Page Template:Citation/styles.css has no content.^ The English version includes a Gellish English Dictionary-Taxonomy that also includes standardized fact types (= kinds of relations).

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content.Heidarzadeh, A.; Sprintson, A. (2017-03-30). "Optimal exchange of data over broadcast networks with adversaries". 2016 Information Theory and Applications Workshop (ITA). pp. 1–5. doi:10.1109/ITA.2016.7888157. ISBN 978-1-5090-2529-9.
  2. ^ Page Module:Citation/CS1/styles.css has no content."What is a Broadcast?". IONOS Digital Guide. 2023-03-20. Retrieved 2024-04-03.
  3. ^ Page Module:Citation/CS1/styles.css has no content."Unicast". IONOS Digital Guide. 2023-03-23. Retrieved 2024-04-03.
  4. ^ Page Module:Citation/CS1/styles.css has no content.Billingsley, F.C. (1988). "General Data Interchange Language". ISPRS Archives. 27 (B3): 80–91. Retrieved 25 May 2018. The transformation routines will constitute a language and syntax which must be discipline and machine independent.
  5. ^ Page Module:Citation/CS1/styles.css has no content.Nurseitov, N.; Paulson, M.; Reynolds, R.; Izurieta, C. (2009). "Comparison of JSON and XML Data Interchange Formats: A Case Study". Scenario: 157–162.
  6. ^ a b Page Module:Citation/CS1/styles.css has no content.Lewis, J.; Moscovitz, M. (2009). AdvancED CSS. APress. pp. 5–6. ISBN 9781430219323. Retrieved 25 May 2018.
  7. ^ Page Module:Citation/CS1/styles.css has no content.Bendersky, E. (22 November 2008). "JSON is YAML, but YAML is not JSON". Eli Bendersky's website. Retrieved 29 May 2018.
  8. ^ Page Module:Citation/CS1/styles.css has no content.Sassenrath, C. (2000). "The REBOL Scripting Language". Dr. Dobb's Journal. 25 (314): 64–8. Retrieved 29 May 2018.
  9. ^ Page Module:Citation/CS1/styles.css has no content.Sassenrath, C. (13 December 2012). "On JSON and REBOL". REBOL.com. Retrieved 29 May 2018.
  10. ^ Page Module:Citation/CS1/styles.css has no content.van Renssen, A.; Vermaas, P.E.; Zwart, S.D. (2007). "A Taxonomy of Functions in Gellish English". Proceedings from the International Conference on Engineering Design 2007: DS42_P_230. Retrieved 29 May 2018.
  11. ^ Page Module:Citation/CS1/styles.css has no content."human-readable". Oxford Dictionaries. Oxford University Press. Archived from the original on May 30, 2018. Retrieved 29 May 2018.

Template:Data Exchange Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Lua error in package.lua at line 80: module 'Module:Authority control/config' not found.

Retrieved from "https://cosmopedia.co/index.php?title=Data_exchange&oldid=3676079"