Semantic data structure and method

• US 10,318,753 B2
• Filed: 06/29/2015
• Issued: 06/11/2019
• Est. Priority Date: 06/30/2014
• Status: Active Grant

• Current Assignee: Vescel LLC
• Original Assignee: Vescel LLC
• Inventors: Anton, Dhryl, McFall, Michael
• Primary Examiner(s): Nguyen, Kim T
• Application Number:
  US14/754,514
• Publication Number:
  US 20160063100A1
• Time in Patent Office: 1,443 Days
• Field of Search: 707739
• CPC Class Codes: G06F 16/2219 Large Object storage; Management thereof
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 2221/2149 Restricted operating environment

Abstract

Disclosed is a method, a device, a system and/or a manufacture of a semantic data structure. In one embodiment, a physical memory usable to store information within a datastore comprises a number of domains. Each domain includes a unique identifier and organizes data into a domain structure that includes and an identity element, a content element, and a context element, each of which may be implemented as an EAV triplet. A fundamental instantiation of the domain structure contains a primitive data and a relational instantiation of the domain structure contains references to other domains. The references of the content element may be constrained, for example to a directed acyclic graph architecture, while references of the context element may reference any domain. Additional instantiations may build orders of referential structure, provide security and control of data resources within the datastore, and model users and application programs.

Claims

1. A physical memory usable to store information within a datastore, the memory comprising:

a number of domains each organizing data into a domain structure that includes;

a unique identifier (UID) whereby a particular domain is uniquely addressable within the datastore;

an identity element (TY element) comprising a first set of attribute-value pairs that include identification data usable to at least one of label the particular domain and distinguish the particular domain from any other domain within the datastore;

a content element (NT element) comprising a second set of attribute-value pairs that include contained data that the particular domain contains;

a context element (XT element) comprising a third set of attribute-value pairs that include contextual data that further characterizes the particular domain

wherein each of the TY element, the NT element, and the XT element are individually addressable within the datastore such that at least one of;

(i) only the first set of attribute-value pairs that include identification data usable to label the particular domain and distinguish the particular domain from any other domain within the datastore;

(ii) only the second set of attribute-value pairs that include data that the particular domain contains, and (iii) only the third set of attribute-value pairs that include contextual data that further characterizes the particular domain, can be returned in response to a single query without returning additional data of the particular domain.

2. The memory of claim 1, wherein at least one of the number of domains is:

a fundamental instantiation of the domain structure referred to as a subject domain which is defined by the contained data of the subject domain being a primitive data that is at least one of embedded in the NT element and referenced through a reference to one or more memory addresses containing the primitive data; and

a relational instantiation of the domain structure referred to as a relation domain, the relation domain defined by the contained data of the relation domain comprising one or more references to each of one or more other domains.

3. The memory of claim 2, wherein a set of the relation domains model a set of containing relationships using a directed acyclic graph (DAG) architecture, each NT element of each of the relation domains a vertex of the DAG architecture and each of the one or more references within the contained data of each of the set of relation domains a directed edge of the DAG architecture.

4. The memory of claim 3, wherein one or more of the number of domains model contextual relationships by including within the contextual data of the one or more domains an unconstrained reference to any other domain.

5. The memory of claim 4, wherein at least one of the number of domains is:

an owner instantiation of the domain structure referred to as an owner domain that references each domain owned by the owner domain,

wherein each domain is owned by one and only one instance of the owner domain, and

wherein the identification data of the each of the domains that is owned by the instance of the owner domain includes a reference to the instance of the owner domain;

a user instantiation of the owner domain referred to as a user domain and representing an owner that is a person; and

a machine-user instantiation of the owner domain referred to as a machine-user domain representing an owner that is an application program.

6. The memory of claim 5, wherein at least one of the number of domains is:

an object instantiation of the relation domain referred to as an object domain, the object domain defined by the contained data of the object domain comprising a reference to each of one or more subject domains;

a stack instantiation of the relation domain referred to as a stack domain, the stack domain defined by the contained data of the stack domain comprising a reference to each of two or more object domains; and

a collection instantiation of the relation domain referred to as a collection domain, the collection domain defined by the contained data of the collection domain comprising a reference to each of two or more stack domains.

7. The memory of claim 6,

wherein the contained data of the object domain further comprises a reference to a first instance of the subject domain and a second instance of the subject domain, the first instance having contained data to be primarily acted upon by an application program and the second instance usable by the application program to represent the first instance in order to facilitate a selection of the data to be primarily acted upon by the application program,

wherein the contained data of the stack domain further comprises a reference to an instance of the subject domain usable by one or more application programs to represent the contained data of the stack domain, and

wherein the contained data of the collection domain further comprises a reference to an instance of the subject domain usable by one or more application programs to represent the contained data of the collection domain.

8. The memory of claim 1,

wherein the identification data usable to at least one of label the particular domain and distinguish the particular domain from any other domain within the datastore comprises at least one of a reference to an instance of the owner domain that owns the particular domain, a name of the domain, an alphanumeric string that labels the domain, a unique property of the particular domain, a unique relation of the particular domain, a property with a low occurrence within the datastore, a relation with a low occurrence within the datastore, and a time stamp of at at least one of a time the particular domain was created and a time the particular domain was modified,

wherein the primitive data is at least one of a binary encoded text, an alphanumeric string, a number, a media file, a binary large object (BLOB), an audio file, a video file, a text file, a file of any MIME type, a cryptographic key, and a document,

wherein the contextual data includes at least one of a characteristic, a color, a physical property, a state, a version, a description of the particular domain, a non-containing relationship to another domain within the datastore, a use for the particular domain, a location, and an example of the particular domain.

9. The memory of claim 7, wherein the contextual data of one or more of the number of domains further comprises application-specific data associated with an application program for which the one or more of the number of domains is an application resource.

10. The memory of claim 9, wherein at least one of the number of domains is:

a security instantiation of the domain structure referred to as a security domain, the security domain protecting with a control policy defining an authorized context for which use of a protected resource is authorized, the protected resource stored within at least one of the security domain and stored within the subject domain referenced by the security domain referred to as a shielded domain.

11. The memory of claim 10,

wherein the control policy comprises a control algorithm comprising one or more conditionals each accepting as an input at least one of the set of control values and at least one outside values that is from outside of the security domain and,

wherein the set of control values includes at least one of a location of a device, a geospatial coordinate of the device, a type of the device, an operating system of the device, an application program, a query time, a query date, a number of uses of data of the protected resource, a type of use of data of the protected resource, a number of accesses of data of the shielded domain, a duration of use of the data within the shielded domain, and an identifier of a user of the device.

12. The memory of claim 11,

wherein at least one of the set of domains modeling the directed acyclic graph DAG architecture are referenced by a first vertex of the NT element of a first relation domain and also referenced by a second vertex of the NT element of a second relation domain.

13. A physical memory usable to store information within a datastore, the memory comprising:

a number of domains each organizing data into a domain structure that includes;

a unique identifier (UID) whereby a particular domain is uniquely addressable within the datastore;

an identity element (TY element) comprising a first set of attribute-value pairs that include identification data comprising at least one of a reference to an owner of the particular domain, a name of the domain and a time stamp of a time that the particular domain was created;

a content element (NT element) comprising a second set of attribute-value pairs that include contained data that the particular domain contains; and

a context element (XT element) comprising a third set of attribute-value pairs that include contextual data that further characterizes the particular domain

wherein each of the TY element, the NT element, and the XT element are individually addressable within the datastore such that at least one of;

(i) only the first set of attribute-value pairs that include identification data usable to label the particular domain and distinguish the particular domain from any other domain within the datastore;

(ii) only the second set of attribute-value pairs that include data that the particular domain contains, and (iii) only the third set of attribute-value pairs that include contextual data that further characterizes the particular domain, can be returned in response to a single query without returning additional data of the particular domain.

14. The memory of claim 13, wherein the number of domains further comprises:

a fundamental instantiation of the domain structure referred to as a subject domain which is defined by the primitive data being at least one of a binary encoded text, an alphanumeric string, a number, a media file, a binary large object (BLOB), an audio file, a video file, a text file, a file of any MIME type, a cryptographic key, and a document; and

an object instantiation of the domain structure referred to as an object domain, the object domain defined by the contained data of the object domain comprising a reference to a first instance of the subject domain and a second instance of the subject domain, the first instance having a first primitive data to be primarily acted upon by an application program and the second instance having a second primitive data usable by the application program to represent the first instance of the subject domain in order to facilitate a selection of the primitive data to be primarily acted upon.

15. The memory of claim 14, wherein the number of domains further comprises:

a stack instantiation of the domain structure referred to as a stack domain, the stack domain defined by the contained data of the stack domain comprising a reference to each of two or more object domains along with a reference to one instance of the subject domain having a third primitive data usable by the application program to represent the stack; and

a collection instantiation of the domain structure referred to as a collection domain, the collection domain defined by the contained data of the collection domain comprising a reference to each of two or more stack domains along with a reference to one instance of the subject domain having a fourth primitive data usable by the application program to represent the stack.

16. The memory of claim 13, further comprising:

an ordered key-value store, each key-value pair of the key-value store storing each attribute-value pair within the first set of key value pairs of the TY element, the second set of key-value pairs of the NT element, and the third set of key-value pairs of the XT element.