# US 2013/0159530 A1 · Representation/invocation of actions/functions in a hypermedia-driven environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159530 A1
- Document ID: US20130159530A1
- Status: Published application
- Kind: A1
- Application number: 13/329,129
- Filed: 2011-12-16
- Published: 2013-06-20
- Earliest claimed: 2011-12-16
- Assignees: Microsoft Corporation
- Inventors: Alex James; Michael Pizzo; Pablo Castro; Mike Flasko; Lance Olson; Jason Clark; Sid Jayadevan
- Web page: https://patentgrep.com/patent/US20130159530A1

## CPC

- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- H04L 9/40: Network security protocols
- H04L 69/329: in the application layer [OSI layer 7]
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The subject disclosure relates to techniques for performing an operation on a resource, based on a state of the resource, by invoking a hypertext transfer protocol (HTTP) request on a universal resource locator (URL) indicating the operation. An interface component can receive a request including an HTTP method and a URL including a first portion indicating a resource and a second portion indicating an operation. Further, an invocation component, in response to the operation being associated with the resource, can invoke the operation on the resource utilizing the HTTP method based on a state of the resource. Other embodiments relate to conditionally returning the operation within a return payload, for example, alone or within a feed, based on an applicability of the operation according to a state of an associated resource.

## Claims

### Claim 1

A method, comprising:
receiving, by a service application of at least one computing device, a request including a hypertext transfer protocol (HTTP) method and a network resource locator identifying an operation that is associated with an instance of a resource;
associating a first portion of the network resource locator indicating the instance of the resource with a second portion of the network resource locator indicating the operation; and
in response to the associating the first portion with the second portion, invoking the operation on the instance utilizing the HTTP method based on a state of the instance.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
publishing the network resource locator as an opaque link within a return payload of one or more requested resources.

### Claim 3 (depends on 2)

The method of claim 2, wherein the publishing the network resource locator further includes publishing the opaque link within at least one of an atom publishing protocol (ATOM) entry or metadata that is associated with a javascript object notation (JSON) object.

### Claim 4 (depends on 2)

The method of claim 2, wherein the publishing the network resource locator further comprises conditionally publishing the opaque link and metadata associated with the opaque link for entries within a feed based on a state of the resource.

### Claim 5 (depends on 1)

The method of claim 1, wherein the invoking the operation further includes invoking an action on the instance having a side effect on at least one of the instance, one or more other related or unrelated instances, or a state of a system.

### Claim 6 (depends on 1)

The method of claim 1, wherein the invoking the operation further includes invoking a function on the instance not having a side effect on the instance.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
defining the operation using one or more entity data model types.

### Claim 8 (depends on 1)

The method of claim 1, wherein the receiving the request further includes receiving the network resource locator including at least one of a function string indicating a function or an action string indicating an action, and wherein the invoking the operation further includes at least one of invoking the function on the instance or invoking the action on the instance.

### Claim 9 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator further includes receiving at least one of:
a resource string indicating the instance;
the resource string being included in the function string;
the resource string being included in the action string;
the action string being appended to the function string; or
the function string being appended to an other function string.

### Claim 10 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator further includes receiving a key indicating a parameter that is associated with at least one of the function or the action.

### Claim 11 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator includes receiving at least one parameter string being appended to the action string and including a parameter that is associated with at least one of the function or the action.

### Claim 12 (depends on 11)

The method of claim 11, wherein the receiving the at least one parameter string includes receiving the function string within a parameter string of the at least one parameter string.

### Claim 13 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator includes receiving the function string being appended to at least one other function string and receiving the action string being appended to the function string.

### Claim 14 (depends on 1)

The method of claim 1, further comprising:
caching metadata that is associated with at least one of the first portion, the second portion, or the instance for re-use.

### Claim 15

A system, comprising:
an interface component stored in a computer readable storage medium configured to receive a request including a hypertext transfer protocol (HTTP) method and a universal resource locator (URL) including a first portion indicating a resource and a second portion indicating an operation; and
an invocation component configured to, in response to the operation being associated with the resource, invoke the operation on the resource utilizing the HTTP method based on a state of the resource.

### Claim 16 (depends on 15)

The system of claim 15, wherein the operation includes an action having a side effect on the resource in response to execution of the action.

### Claim 17 (depends on 15)

The system of claim 15, wherein the operation includes a function not having a side effect on the resource in response to execution of the function.

### Claim 18 (depends on 15)

The system of claim 15, further comprising:
a storage component configured to store metadata that is associated with at least one of the operation or the resource in a cache to obtain cached data, wherein the invocation component is further configured to invoke the operation based on the cached data.

### Claim 19 (depends on 18)

The system of claim 18, wherein the storage component is further configured to modify the cached data based on the URL.

### Claim 20

A computer-readable storage medium comprising computer executable instructions that, in response to execution, cause a computing device to perform operations, comprising:
receiving, from a web client, a request including a hypertext transfer protocol (HTTP) method and a network resource locator including at least one of a function string that is associated with an instance of a resource or an action string that is associated with the instance; and
in response to associating the at least one of the function string or the action string with a respective operation, invoking the respective operation on the instance using the HTTP method based on a state of the resource.

### Claim 21 (depends on 2)

The method of claim 2, wherein the publishing the network resource locator further includes publishing metadata including at least one of an operation identifier, a network resource locator describing the metadata including at least one of any parameters for the operation or a return type for the operation, or a friendly name.

### Claim 22 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator includes receiving at least one parameter string including a placeholder associated with a parameter of the at least one of the function or the action.

### Claim 23 (depends on 8)

The method of claim 8, wherein the receiving the network resource locator includes receiving at least one parameter string in at least one of a uniform resource locator path, a query string, a header, a body of the request, the function string, or the action string.
