Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update url-components.md #297

Merged
merged 1 commit into from
Jul 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Odata-docs/concepts/url-components.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ http://host:port/path/SampleService.svc/Categories(1)/Products?$top=2&$orderby=N
The service root of a url is the base url of the service. When a _GET_ request is made to this url it will return a service document that defines all the resources available via that service.

2. ***Resource path***
A resource by REST definition is an object which is accessible over the HTTP by using the standard GET,POST,PUT,PATCH and DELETE methods. It could be a single object or a collection of similar objects, presented in an ordered or unordered.
A resource by REST definition is an object which is accessible over HTTP by using the standard GET,POST,PUT,PATCH and DELETE methods. It could be a single object or a collection of similar objects, presented in an ordered or unordered fashion.
An object is constructed of a certain type, has relationships with other objects and has methods that operate on it.
Some examples for resources might be: customers, a single customer, orders related to a single customer, and so forth.
Examples of addressable aspects of these resources as exposed by the data model might be: collections of entities, a single entity, properties, links, operations, and so on.
Expand Down