IP Library Granted Patent US 11,461,078
Granted Patent B2
US 11,461,078 · App. 16/838,647 · Granted Oct 4, 2022

Device and method for producing a backend application utilizing metaprogramming and a domain ontology having a syntactic and semantic specification

Inventor: Vincent Lextrait (Boston, MA)
Assignee: Metaspex LLC
G06F8/42G06F8/436G06F8/44G06F8/447
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,461,078
App. No.
16/838,647
Granted
Oct 4, 2022
Kind
B2
Abstract

Embodiments of the innovation relate to, in a development device, a method of generating a backend application for execution by a server device. The method comprises receiving, by the development device, ontology information associated with an enterprise domain, the ontology information including syntactic information and semantic information; applying, by the development device, a metaprogramming engine to the ontology information to generate the backend application; and forwarding, by the development device, the backend application to the server device.

Claims (62)

1. In a development device, a method of generating a backend application for execution by a server device, comprising:

receiving, by the development device, ontology information defining aspects of an enterprise domain, the ontology information having a list of types, each type of the list of types configured to carry at least one attribute, the ontology information including syntactic information rules and semantic rules,

each syntactic rule of the syntactic rules comprising an origin type and one or more target types and establishing relationships between the origin type and the one or more target types,

each type of the list of types appearing as an origin and as one or more targets in the syntactic rules,

a same type of the list of types configured to appear multiple times as an origin and as one or more targets in the syntactic rules,

the semantic rules attached to any type of the list of types, each semantic rule of the semantic rules expressed as an evaluation function, each semantic rule identifying bidirectional dependencies between a semantic attribute value and data of at least one of the same type and a different type of the list of types,

the evaluation function, referencing at least one of other semantic attributes, the attributes defined by the enterprise domain, relationships, changes in the attributes defined by the enterprise domain, and changes in the relationships, configured to propagate to dependent semantic attributes;

indexing, by the development device, the semantic attribute value in a searchable database;

applying, by the development device, a metaprogramming engine to the ontology information to generate the backend application, the backend application being configured to manage backend documents, the backend documents following at least one syntactic rule and bearing at least one semantic attribute, the semantic attribute configured to be calculated from the evaluation function; and

forwarding, by the development device, the backend application to the server device.

2. The method of claim 1 , wherein receiving ontology information associated with an enterprise domain comprises:

receiving, by the development device, enterprise domain information from an enterprise;

accessing, by the development device, an ontology library based upon a correspondence between the enterprise domain information and an enterprise domain identifier associated with the ontology library; and

retrieving, by the development device, the ontology information associated with the enterprise domain from the ontology library.

3. The method of claim 1 , wherein receiving ontology information associated with the enterprise domain comprises receiving ontology information associated with the enterprise domain where the semantic rules are attached to the syntactic rules.

4. The method of claim 1 , wherein applying the metaprogramming engine to the ontology information to generate the backend application comprises:

identifying, by the development device, a metaprogramming tag associated with each of the syntactic rules and the semantic rules; and

applying, by the development device, the metaprogramming engine to each of the corresponding metaprogramming tags for the syntactic rules and semantic rules to generate at least a portion of the backend application.

5. The method of claim 1 , wherein:

receiving ontology information associated with the enterprise domain further comprises receiving, by the development device, ontology security information associated with the enterprise domain, the ontology security information including syntactic information and semantic information for defining a role of an end user of the server device; and

applying the metaprogramming engine to the ontology information to generate the backend application comprises applying, by the development device, the metaprogramming engine to the ontology information and to the ontology security information to generate the backend application having an associated security application.

6. The method of claim 1 , wherein the at least one semantic attribute of the backend document is derived from one or more of at least one syntactic attribute.

7. The method of claim 1 , wherein the at least one semantic attribute comprises, as a semantic attribute value, a nested document.

8. An enterprise system, comprising:

a server device having a controller comprising a memory and a processor; and

a development device disposed in electrical communication with the server device, the development device having a controller comprising a memory and a processor;

wherein the development device is configured to:

receive ontology information defining aspects of an enterprise domain, the ontology information having a list of types, each type of the list of types configured to carry at least one attribute, the ontology information including syntactic rules and semantic rules,

each syntactic rule of the syntactic rules comprising an origin type and one or more target types and establishing relationships between the origin type and the one or more target types,

each type of the list of types appearing as an origin and as one or more targets in the syntactic rules,

a same type of the list of types configured to appear multiple times as an origin and as one or more targets in the syntactic rules,

the semantic rules attached to any type of the list of types, each semantic rule of the semantic rules expressed as an evaluation function, each semantic rule identifying bidirectional dependencies between a semantic attribute value and data of at least one of the same type and a different type of the list of types,

the evaluation function, referencing at least one of other semantic attributes, the attributes defined by the enterprise domain, relationships, changes in the attributes defined by the enterprise domain, and changes in the relationships, configured to propagate to dependent semantic attributes;

index the semantic attribute value in a searchable database;

apply a metaprogramming engine to the ontology information to generate the backend application, the backend application being configured to manage backend documents, the backend documents following at least one syntactic rule and bearing at least one semantic attribute, the semantic attribute configured to be calculated from the evaluation function; and

forward the backend application to the server device.

9. The enterprise system of claim 8 , wherein when receiving ontology information associated with an enterprise domain, the development device is configured to:

receive enterprise domain information from an enterprise;

access an ontology library based upon a correspondence between the enterprise domain information and an enterprise domain identifier associated with the ontology library; and

receive the ontology information associated with the enterprise domain from the ontology library.

10. The enterprise system of claim 8 , wherein when receiving ontology information associated with the enterprise domain, the development device is configured to receive ontology information associated with the enterprise domain where the semantic rules is attached to the syntactic rules.

11. The enterprise system of claim 8 , wherein when applying the metaprogramming engine to the ontology information to generate the backend application, the development device is configured to:

identify a metaprogramming tag associated with each of the syntactic rules and the semantic rules; and

apply the metaprogramming engine to each of the corresponding metaprogramming tags for the syntactic rules and semantic rules to generate at least a portion of the backend application.

12. The enterprise system of claim 8 , wherein:

when receiving ontology information associated with the enterprise domain, the development device is further configured to receive ontology security information associated with the enterprise domain, the ontology security information including syntactic information and semantic information for defining a role of an end user of the server device; and

when applying the metaprogramming engine to the ontology information to generate the backend application, the development device is further configured to apply the metaprogramming engine to the ontology information and to the ontology security information to generate the backend application having an associated security application.

13. The enterprise system of claim 8 , wherein the at least one semantic attribute of the backend document is derived from one or more of at least one syntactic attribute.

14. The enterprise system of claim 8 , wherein the at least one semantic attribute comprises, as a semantic attribute value, a nested document.

15. The enterprise system of claim 8 , wherein the server device is configured to:

store the backend document in a database; and

index the backend document based on at least one semantic attribute included in the backend document.

16. A computer program product having a non-transitory computer-readable medium including computer program logic encoded thereon that, when performed on a controller of a development device causes the development device to:

receive ontology information defining aspects of an enterprise domain, the ontology information having a list of types, each type of the list of types configured to carry at least one attribute, the ontology information including syntactic rules and semantic rules,

each syntactic rule of the syntactic rules comprising an origin type and one or more target types and establishing relationships between the origin type and the one or more target types,

each type of the list of types appearing as an origin and as one or more targets in the syntactic rules,

a same type of the list of types configured to appear multiple times as an origin and as one or more targets in the syntactic rules,

the semantic rules attached to any type of the list of types, each semantic rule of the semantic rules expressed as an evaluation function, each semantic rule identifying bidirectional dependencies between a semantic attribute value and data of at least one of the same type and a different type of the list of types,

the evaluation function, referencing at least one of other semantic attributes, the attributes defined by the enterprise domain, relationships, changes in the attributes defined by the enterprise domain, and changes in the relationships, configured to propagate to dependent semantic attributes;

index the semantic attribute value in a searchable database;

apply a metaprogramming engine to the ontology information to generate the backend application, the backend application being configured to manage backend documents, the backend documents following at least one syntactic rule and bearing at least one semantic attribute, the semantic attribute configured to be calculated from the evaluation function; and

forward the backend application to a server device.

Assignments (2)
CHANGE OF NAME Recorded Mar 18, 2021
From: MACROMETA LLC
To: METASPEX LLC
Reel/Frame 055649/0114 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2020
From: LEXTRAIT, VINCENT
To: MACROMETA, LLC
Reel/Frame 052895/0078 →
Continuity (2)
Provisional Application 62828661 · Apr 3, 2019
Related Publication 20200319863A1 · Oct 8, 2020