Data Fragmentation - Revision history

User at 15:14, 26 August 2023

2023-08-26T15:14:06Z

User at 15:13, 26 August 2023

2023-08-26T15:13:21Z

User: Created page with "'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements..."

2021-12-03T02:12:16Z

Created page with "'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements..."

New page

'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements of the service with individual processing needs of different consumers. Rather than forcing all consumers of a service to always accept and process every element of the message or service response, the consumers can select which of the elements as data fragments (groups of elements) that they require. Consumers specify the required data fragments in the request message using filters. Filters are simple XML elements that have an allowable value of “true” (i.e., “on” or “yes”) and “false” (i.e., “off” or “no”). Each filter is mapped one-to-one with a data fragment (collection of data elements defined to a parent, complex type element) of the message. For each data fragment that is required by a service consumer, the value of the filter is set to “true” in the request message. Upon receiving the request message, the service unmarshals the filter elements and data values from the message, maps the request values to the service and data access object model, processes the request and acquires the data from the data at rest sources, and returns only the requested data elements in the reply message.<ref>Definition - What Does Data Fragmentation Mean? [https://www.sciencedirect.com/science/article/pii/B9780123748911000150 James Bean]</ref>

← Older revision		Revision as of 15:14, 26 August 2023
Line 1:		Line 1:
−	'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements of the service with individual processing needs of different consumers. Rather than forcing all consumers of a service to always accept and process every element of the message or service response, the consumers can select which of the elements as data fragments (groups of elements) that they require. Consumers specify the required data fragments in the request message using filters. Filters are simple XML elements that have an allowable value of “true” (i.e., “on” or “yes”) and “false” (i.e., “off” or “no”). Each filter is mapped one-to-one with a data fragment (collection of data elements defined to a parent, complex type element) of the message. For each data fragment that is required by a service consumer, the value of the filter is set to “true” in the request message. Upon receiving the request message, the service unmarshals the filter elements and data values from the message, maps the request values to the service and data access object model, processes the request and acquires the data from the data at rest sources, and returns only the requested data elements in the reply message.<ref>Definition - What Does Data Fragmentation Mean? [https://www.sciencedirect.com/science/article/pii/B9780123748911000150 James Bean]</ref>	+	'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting [[data]] elements of the service with individual processing needs of different consumers. Rather than forcing all consumers of a service to always accept and process every element of the message or service response, the consumers can select which of the elements as data fragments (groups of elements) that they require. Consumers specify the required data fragments in the request message using filters. Filters are simple XML elements that have an allowable value of “true” (i.e., “on” or “yes”) and “false” (i.e., “off” or “no”). Each filter is mapped one-to-one with a data fragment (collection of data elements defined to a parent, complex type element) of the message. For each data fragment that is required by a service consumer, the value of the filter is set to “true” in the request message. Upon receiving the request message, the service unmarshals the filter elements and data values from the message, maps the request values to the service and data access object model, processes the request and acquires the data from the data at rest sources, and returns only the requested data elements in the reply message.<ref>Definition - What Does Data Fragmentation Mean? [https://www.sciencedirect.com/science/article/pii/B9780123748911000150 James Bean]</ref>

← Older revision		Revision as of 15:13, 26 August 2023
Line 1:		Line 1:
	'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements of the service with individual processing needs of different consumers. Rather than forcing all consumers of a service to always accept and process every element of the message or service response, the consumers can select which of the elements as data fragments (groups of elements) that they require. Consumers specify the required data fragments in the request message using filters. Filters are simple XML elements that have an allowable value of “true” (i.e., “on” or “yes”) and “false” (i.e., “off” or “no”). Each filter is mapped one-to-one with a data fragment (collection of data elements defined to a parent, complex type element) of the message. For each data fragment that is required by a service consumer, the value of the filter is set to “true” in the request message. Upon receiving the request message, the service unmarshals the filter elements and data values from the message, maps the request values to the service and data access object model, processes the request and acquires the data from the data at rest sources, and returns only the requested data elements in the reply message.<ref>Definition - What Does Data Fragmentation Mean? [https://www.sciencedirect.com/science/article/pii/B9780123748911000150 James Bean]</ref>		'''Data Fragmentation''' is a canonical message and service interface design approach that balances between the scope of information requirements and supporting data elements of the service with individual processing needs of different consumers. Rather than forcing all consumers of a service to always accept and process every element of the message or service response, the consumers can select which of the elements as data fragments (groups of elements) that they require. Consumers specify the required data fragments in the request message using filters. Filters are simple XML elements that have an allowable value of “true” (i.e., “on” or “yes”) and “false” (i.e., “off” or “no”). Each filter is mapped one-to-one with a data fragment (collection of data elements defined to a parent, complex type element) of the message. For each data fragment that is required by a service consumer, the value of the filter is set to “true” in the request message. Upon receiving the request message, the service unmarshals the filter elements and data values from the message, maps the request values to the service and data access object model, processes the request and acquires the data from the data at rest sources, and returns only the requested data elements in the reply message.<ref>Definition - What Does Data Fragmentation Mean? [https://www.sciencedirect.com/science/article/pii/B9780123748911000150 James Bean]</ref>
		+
		+
		+
		+	== See Also ==
		+	#Database Normalization
		+	#Distributed Database
		+	#[[Database Management System (DBMS)]]
		+	#[[Data Replication]]
		+	#Data Allocation
		+	#[[Relational Database]]
		+	#Data Redundancy
		+	#Data Warehouse]]
		+	#Data Partitioning
		+	#Database Performance Tuning
		+
		+
		+
		+
		+
		+
		+
		+	== References ==
		+	<references />