Term



0



[watch]
Term: data object Class:  
 vernacular   (0%)
Created 23 October 2013
Last modified 23 October 2013
Contributed by Gary Berg-Cross

Permalink:
  n2t.net/ark:/99152/h1089

Definition: discrete data, considered as a unit, representing an instance of a datatype that is known or assumed to be known [adapted from ISO/IEC 2382-17}
Examples:

Does a data object have an identity property? I.e. can the question 'is this the same data object as that thing over there' be answered. Submitted 14 April 2016
by Stephen
Data Objects are unambiguously identified using Identifiers that
serve as Names; resolution of these Identifiers is optional. see Kingsley Idehen discussion at https://plus.google.com/112399767740508618350/posts/U4u4FBmLnvx
Submitted 14 April 2016
by Gary
A unit of data that is created, annotated and processed on the user desktop. It represents a native structure the user works with. The usage of the term 'native' is important. It means that a DataObject can be directly mapped to a data structure maintained by a native application. This may be a file, a set of files or a part of a file. The granularity depends on the user. This class is not intended to be instantiated by itself. Use more specific subclasses. See NEPOMUK Information Element Core Ontology http://www.semanticdesktop.org/ontologies/2007/01/19/nie/ Submitted 14 April 2016
by Gary
DO - The actual binary/octet data being operated on (transformed, digested, or signed) by an application -- frequently an HTTP entity [HTTP]. Note that the proper noun Object designates a specific XML element. Occasionally we refer to a data object as a document or as a resource's content. The term element content is used to describe the data between XML start and end tags [XML]. The term XML document is used to describe data objects which conform to the XML specification [XML]. from http://www.w3.org/TR/xmldsig-core/ Submitted 14 April 2016
by Gary