Omega names: name generation and derivation utilizing nested three or more attributes

US10324909B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10324909-B2
Application numberUS-201715799267-A
CountryUS
Kind codeB2
Filing dateOct 31, 2017
Priority dateJun 28, 2013
Publication dateJun 18, 2019
Grant dateJun 18, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In a computing resource environment including at least two different resource name spaces, a method for generating a fully-qualified name for a resource based on a context-based name of that resource and a usage context is disclosed. Method steps include receiving the resource's name schema, its context-based name, and usage context; comparing an entry in the schema and an entry in the context-based name and identifying schema monikers missing from the context-based name. For a missing moniker, determining whether it is an attribute space (aspace) moniker. If it is an aspace moniker, adding it to a full name that includes the context-based name. If it is not an aspace moniker, determining the aspace associated with the missing moniker; searching the usage context for an association between the missing moniker, its aspace, and a value assigned to the missing moniker; and appending the searched-for items to the full name.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method of deriving a fully-qualified name of a destination resource in a particular system within an environment based on a set of derivation rules associated with the particular system, the method comprising: receiving, as inputs, a name of a source resource, an attribute value associated with the destination resource and a name schema associated with the source resource; generating, by one or more processors, a destination resource name based on the name of the source resource; nesting an attribute name for a first attribute of a second system within the environment within an attribute for a second attribute of the particular system and transforming, by the one or more processors, the generated name into a derived destination resource name using the name schema by: generating a third attribute value for a third attribute based on the derivation rules, the third attribute corresponding to a computing task relating to the destination resource, adding the third attribute value or the attribute value to the generated name, and adding the attribute value for the second attribute to the generated name when the second attribute of the particular system is an instantiation of the first attribute in the second system. 2. The method of claim 1 , wherein transforming the generated name into the derived destination resource name includes extracting a nested attribute name from a third attribute value of the generated name based on the derivation rules. 3. The method of claim 2 , wherein extracting includes: deleting the third attribute value from the generated name, and adding a fourth attribute value for an attribute corresponding to the nested attribute name to the generated name. 4. The method of claim 1 , further comprising, using the derived destination resource name to fulfill the task using the destination resource. 5. The method of claim 1 , wherein the derived destination resource is configured to allow the one or more processors to access the destination resource in order to complete the task. 6. The method of claim 1 , wherein changing includes changing a value of a schema attribute in the generated name such that the derived destination resource name becomes associated with a schema different from that of the source resource. 7. The method of claim 1 , further comprising identifying the derivation rules from the name schema associated with the source resource. 8. The method of claim 1 , further comprising generating the derivation rules from the name schema associated with the source resource. 9. A method of deriving a fully-qualified name of a destination resource in a particular system within an environment based on a set of derivation rules associated with the particular system, the method comprising: receiving, as inputs, a name of a source resource, an attribute value associated with the destination resource and a name schema associated with the source resource; generating a destination resource name based on the name of the source resource; and nesting an attribute name for a first attribute of a second system within the environment within an attribute for a second attribute of the particular system, and transforming the generated name into a derived destination resource name using the name schema by: and generating a third attribute value for a third attribute based on the derivation rules, the third attribute corresponding to a computing task relating to the destination resource, adding the third attribute value or the attribute value to the generated name, and adding the attribute value for the second attribute to the generated name when the second attribute of the particular system is an instantiation of the first attribute in the second system. 10. The method of claim 9 , wherein transforming the generated name into the derived destination resource name includes extracting a nested attribute name from a second attribute value of the generated name based on the derivation rules. 11. The method of claim 10 , where extracting includes: deleting a second attribute value associated with a third attribute from the generated name; and adding a third attribute value for an attribute corresponding to the nested attribute name to the generated name. 12. The method of claim 9 , further comprising identifying the derivation rules from the name schema associated with the source resource. 13. The method of claim 9 , further comprising generating the derivation rules from the name schema associated with the source resource. 14. The method of claim 9 , wherein transforming the generated name includes: generating a second attribute value for a third attribute different from the first attribute based on the derivation rules, the second attribute corresponding to a task relating to the destination resource, and adding the second attribute value to the generated name. 15. A computing system for deriving a fully-qualified name of a destination resource in a particular system within an environment based on a set of derivation rules associated with the particular system, the computing system comprising one or more processors configured to: receive, as inputs, a name of a source resource, an attribute value associated with the destination resource and a name schema associated with the source resource; generate a destination resource name based on the name of the source resource; nesting an attribute name for a first attribute of a second system within the environment within an attribute for a second attribute of the particular system and and transform the generated name into a derived destination resource name using the name schema by: generate a third attribute value for a third attribute based on the derivation rules, the third attribute corresponding to a computing task relating to the destination resource, add the attribute value or the third attribute value to the generated name; and adding the attribute value for the second attribute to the generated name when the second attribute of the particular system is an instantiation of the first attribute in the second system. 16. The system of claim 15 , wherein transforming the generated name into the derived destination resource name includes extracting a nested attribute name from a third attribute value of the generated name based on the derivation rules. 17. The system of claim 16 , wherein extracting includes: deleting the third attribute value from the generated name, and adding a fourth attribute value for an attribute corresponding to the nested attribute name. 18. The system of claim 15 , wherein changing includes changing a value of a schema attribute in the generated name such that the derived destination resource name becomes associated with a schema different from that of the source resource.

Assignees

Inventors

Classifications

  • G06F40/131Primary

    Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces · CPC title

  • Tree-structured documents (parsing G06F40/205; validation G06F40/226) · CPC title

  • Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation · CPC title

  • Lexical analysis, e.g. tokenisation or collocates · CPC title

  • Inventory monitoring · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10324909B2 cover?
In a computing resource environment including at least two different resource name spaces, a method for generating a fully-qualified name for a resource based on a context-based name of that resource and a usage context is disclosed. Method steps include receiving the resource's name schema, its context-based name, and usage context; comparing an entry in the schema and an entry in the context-…
Who is the assignee on this patent?
Google Llc
What technology area does this patent fall under?
Primary CPC classification G06F40/131. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 18 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).