SEMANTIC DATA STRUCTURE AND METHOD

• US 20160063100A1
• Filed: 06/29/2015
• Published: 03/03/2016
• Est. Priority Date: 06/30/2014
• Status: Active Grant

• Current Assignee: Vescel LLC
• Original Assignee: Cloudmode LLC
• Inventors: Anton, Dhryl, McFall, Michael
• Granted Patent: US 10,318,753 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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; and

a context element (XT element) comprising a third set of attribute-value pairs that include contextual data that further characterizes 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.

16. The memory of claim 1, 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.

11. The memory of claim 12,

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.

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.

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.

17. A method for storing data on a machine-readable medium for efficient retrieval, the method comprising:

receiving a selection of a primitive data to be contained by a domain of the datastore referred to as a subject domain;

encapsulating the primitive data within a content element (NT element) of the subject domain, wherein the primitive data is at least one of embedded within the NT element and logically contained through a reference to a memory address that holds the primitive data;

constructing an identity element (TY element) of the subject domain by grouping identity data that at least one of labels the subject domain and distinguishes the subject domain from any other domain within the datastore;

constructing a context element (XT element) of the subject domain by grouping contextual data that further characterizes the subject domain;

generating a unique identifier (UID) of the subject domain usable to uniquely address the subject domain within the datastore;

assembling the subject domain by bundling the TY element of the subject domain, the NT element of the subject domain, the XT element of the subject domain and the UID of the subject domain; and

depositing the subject domain in the machine-readable memory.

18. The method of claim 17, further comprising:

receiving a selection of a first subject domain referred to as a derivative domain containing a first primitive data usable as a primary data to be acted upon by an application program;

receiving a selection of a second subject domain referred to as a representation domain containing a second primitive data usable by the application program as a representation of the primary data, the representation of the primary data usable by the application program to facilitate a selection of the first subject domain within the datastore;

encapsulating a reference to both the derivative domain and the representation domain within a content element (NT element) of an object domain, the object domain defining a relationship between the primary data and the representation of the primary data;

constructing an identity element (TY element) of the object domain by grouping identity data usable to at least one of label the object domain and distinguish the object domain from any other domain within the datastore;

constructing a context element (XT element) of the object domain by grouping contextual data that further characterizes the object domain;

generating a unique identifier (UID) of the object domain usable to uniquely address the object domain within the datastore;

assembling the object domain by bundling the TY element of the object domain, the NT element of the object domain, the XT element of the object domain and the UID of the object domain; and

depositing the object domain in the machine-readable memory.

19. The method of claim 18, further comprising:

selecting one or more object domains to be contained by a stack domain, the stack domain defining a relationship between the one or more object domains;

selecting a third representation domain containing a third primitive data usable by the application program as a representation of the relationship between the one or more object domains, the representation of the one or more object domains usable by the application program to facilitate a selection of the stack domain within the datastore;

encapsulating a reference to each of the one or more object domains within the content element (NT element) of an stack domain; and

constructing an identity element (TY element) of the stack domain by grouping identity data usable to at least one of label the stack domain and distinguish the stack domain from any other domain within the datastore.

20. The method of claim 19, further comprising:

constructing a context element (XT element) of the stack domain by grouping contextual data that further characterizes the stack domain;

generating a unique identifier (UID) of the stack domain usable to uniquely address the stack domain within the datastore;

assembling the stack domain by bundling the TY element of the stack domain, the NT element of the stack domain, the XT element of the stack domain and the UID of the stack domain; and

depositing the stack domain in the machine-readable memory.

21. A physical memory comprising:

a set of one or more domains implementing a datastore, each domain of the set of domains comprising;

a unique identifier (UID);

a first entity of a first EAV triplet comprising one or more attributes and corresponding values that store data that makes a particular domain of the set of domains unique,

wherein the data that makes the particular domain unique comprises an owner of the first domain and at least one of a name of the particular domain and a time at which the particular domain was at least one of created and modified;

a second entity of a second EAV triplet comprising one or more attributes and corresponding values storing data that the particular domain of the set of domains logically contains,

wherein the data that the particular domain of the set of domains logically contains is at least one of a primitive data and one or more references to other domains of the set of domains;

a third entity of a third EAV triplet comprising one or more attributes and corresponding values storing data related to a use for the particular domain.

22. The memory of claim 21, further comprising:

a first order of structure comprising one or more subject domains, the data that each of the one or more subject domains logically contains in the second entity comprising an instance of the primitive data,

wherein the instance of the primitive data is a file of any MIME-type,

wherein each of the one or more subject domains is referenceable as at least one of a derivative subject domain and a representation subject domain, where the derivative subject domain contains a primary data to be used by an application program and the representation subject domain contains data usable by the application program to represent the primary data, and

wherein each of the one or more subject domains is simultaneously referenceable by N domains of any order of structure higher than the first order of structure.

23. The memory of claim 22, further comprising:

a second order of structure comprising one or more object domains as a subset of the set of one or more domains,

wherein the data that a particular object domain of the one or more object domains logically contains comprises a derivative reference to a first instance of the subject domain to act as a derivative subject domain and optionally further comprises a representation reference to a second instance of the subject domain to act as a representation subject domain of the derivative subject domain, and

wherein each object domain of the one or more object domains is simultaneously referenceable by N domains of a third order of structure.

24. The memory of claim 23, further comprising:

the third order of structure comprising one or more stack domains as a subset of the set of one or more domains,

wherein the data that a particular stack domain of the one or more stack domains logically contains comprises a reference to N object domains of the second order of structure,

wherein the data that the particular stack domain logically contains optionally includes a different representation reference to a third instance of the subject domain to act as a representation subject domain of the particular stack domain, and

wherein the particular stack domain is simultaneously referencable by N domains of a fourth order of structure; and

the fourth order of structure comprising one or more collection domains as a subset of the set of one or more domains,

wherein the data that a particular collection domain of the one or more collection domains logically contains comprises a reference to N stack domains of the third order of structure, and

wherein the data that the particular collection domain logically contains optionally includes a different representation reference to a fourth instance of the subject domain to act as a representation subject domain of the particular collection domain.

25. The memory of claim 24,

wherein the data related to the use of the particular domain of the set of domains comprises a reference to an application program that at least one of created and modified the particular domain, and further comprises application specific data of the application program,

wherein the first entity of the particular domain is individually addressable within the datastore such that only the first entity comprising data that makes the particular domain unique can be returned in response to a query without returning additional data of the particular domain,

wherein the second entity of the particular domain is individually addressable within the datastore such that only the second entity comprising data that the particular domain logically contains can be returned in response to a query without returning additional data of the particular domain,

wherein the third entity of the particular domain is individually addressable within the datastore such that only the third entity comprising data related to a use for the particular domain can be returned in response to a query without returning additional data of the particular domain,

wherein the file of any MIME-type is at least one of a record, a document, and a media file, and

wherein the primitive data that represents the first subject domain is an image.