A Concept for Orchestration of Microservices
US-2024281220-A2 · Aug 22, 2024 · US
US9384187B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9384187-B2 |
| Application number | US-201213567557-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 6, 2012 |
| Priority date | Nov 27, 2007 |
| Publication date | Jul 5, 2016 |
| Grant date | Jul 5, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method includes identifying a document structure instance that includes structure components. A selected structure component is chosen from the structure components. The method includes generating, with a processor, a hierarchical graph based on the selected structure component. The hierarchical graph includes classes, a class definition relationship, and an instance identifier that identifies the selected structure component. The hierarchical graph is output.
Opening claim text (preview).
We claim: 1. A method comprising: identifying a document structure instance that includes a plurality of structure components; selecting one structure component from the structure components; selecting by a processor, a pre-configured core ontology hierarchy associated with the selected structure component, the pre-configured core ontology hierarchy including a plurality of classes, and a class definition relationships; generating a document specific ontology hierarchy based on the selected pre-configured core ontology, wherein the document specific ontology includes a subset of the classes included in the pre-configured core ontology hierarchy; inserting into the document specific ontology instance identifiers associated with each respective structure component; and outputting the document specific ontology hierarchy. 2. The method of claim 1 , where the class definition relationship illustrates a relationship between at least two of the classes. 3. The method of claim 1 , where identifying comprises identifying the document structure instance using a document structure identifier. 4. The method of claim 3 , where the document structure identifier identifies a document type including structure categories; and where the selected structure component is associated with at least one of the structure categories of the document type. 5. The method of claim 1 , where the classes include a root class and a child class of the root class. 6. The method of claim 5 , where the class definition relationship identifies a vertical relationship between the root class and the child class. 7. The method of claim 1 , further comprising: determining a glossary associated with the selected structure component, the glossary including permissible terms for a structure category associated with the selected structure component, the permissible terms including hierarchy parameters indicating parent or child relationships for the permissible terms. 8. The method of claim 7 , where generating comprises generating the hierarchical graph using the hierarchy parameters of the permissible terms in the glossary. 9. The method of claim 1 , where the class definition relationship comprises an affect relationship, a contradict relationship, a dependency relationship, an implement relationship, a similarity relationship, or any combination. 10. A system comprising: a memory comprising: a document structure instance that includes structure components; instructions to: receive a selected structure component from the structure components; select a pre-configured core ontology hierarchy associated with the selected structure component, the pre-configured core ontology hierarchy including a plurality of classes, and a class definition relationships generate a document specific ontology hierarchy based on the selected pre-configured core ontology, wherein the document specific ontology includes a subset of the classes included in the pre-configured core ontology hierarchy; insert into the document specific ontology instance identifier that identifies the selected structure component; and output the hierarchical graph; and a processor configured to execute the instructions. 11. The system of claim 10 , where the class definition relationship identifies a relationship between at least two of the classes. 12. The system of claim 10 , where the class definition relationship comprises an affect relationship, a contradict relationship, a dependency relationship, an implement relationship, a similarity relationship, or any combination. 13. The system of claim 10 , where the classes include a root class and a child class of the root class; and where the class definition relationship identifies a vertical relationship between the root class and the child class. 14. The system of claim 10 , further comprising: a glossary associated with the selected structure component, the glossary including permissible terms for a structure category associated with the selected structure component, the permissible terms including hierarchy parameters indicating parent or child relationships for the permissible terms; and where the hierarchical graph is generated according to the hierarchy parameters of the permissible terms in the glossary. 15. The system of claim 10 , where the selected structure component is a first selected structure component and where the hierarchical graph that is generated is a first hierarchical graph, and where the memory further comprises: instructions to: receive a second selected structure component from the structure components; and generate a second hierarchical graph of said document structure instance corresponding to the second selected structure component. 16. The system of claim 10 , where the memory further comprises: instructions to: modify the hierarchical graph to include instance identifiers of each respective structure component in the hierarchical graph. 17. The system of claim 10 , where the memory further comprises: instructions to compare the hierarchical graph with a predetermined hierarchical graph to detect compatibility of the document structure instance with a predetermined format of a document comprising the document structure instance. 18. A method comprising: accessing a pre-configured core ontology hierarchy that defines a hierarchy of classes and class definition relationships between at least some of the classes, where each of the classes of the ontology model is associated with a search term; analyzing a first document structure instance against the ontology model to determine a first class associated with the first document structure instance by searching the first document structure instance for a first search term associated with the first class; analyzing a second document structure instance against the ontology model to determine a second class associated with the second document structure instance by searching the second document structure instance for a second search term associated with the second class; and analyzing, with a processor, the class definition relationships to determine whether the first class affects the second class generating a document specific ontology hierarchy based on the selected pre-configured core ontology, wherein the document specific ontology includes a subset of the classes included in the pre-configured core ontology hierarchy and a first instance identifier that identifies the first class associated with the first document structure instance and a second instance identifier that identifies the second class associated with the second document structure instance; and outputting the ontology model. 19. The method of claim 18 , where the classes include a root class and a child class.
Creation of semantic tools, e.g. ontology or thesauri · CPC title
Requirements analysis; Specification techniques · CPC title
Document management systems · CPC title
Lexical analysis, e.g. tokenisation or collocates · CPC title
Grammatical analysis; Style critique · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.