Applications MAY extend the SData URL syntax with application specific URL branches (similar to $service, $schema or $template) or application specific query parameters.
To avoid potential conflicts between application specific extensions and future extensions to the SData protocol, applications SHOULD prefix all their extensions with an underscore (_).
The following table gives examples of application specific extensions:
|http://www.example.com/sdata/myApp/myContract/-/contacts/_deleted||Application specific Extension to query resources that have been "soft deleted".|
|http://www.example.com/sdata/myApp/myContract/-/contacts('254')?_transaction=23||Application specific extension to pass a transaction context to a query.|
Development teams are encouraged to submit their extensions to the SData working group. Extensions that have general applicability may become part of a future version of the standard (they will then loose their underscore).
Applications that extend the protocol SHOULD follow the rules above.