[ODATA-430] Add term Core.ResourcePath to describe unconventional resource paths in CSDL - OASIS Technical Committees Issue Tracker

Details

Type: Improvement
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: V4.0_CSD01
Fix Version/s: V4.0_CSD02
Component/s: CSDL XML, URL Conventions, Vocabularies
Labels:
None
Environment:

[Applied]

Proposal:

Hide

Add term to Core vocabulary

<Term Name="ResourcePath" Type="Edm.String" AppliesTo="EntitySet SingletonEntity ActionImport FunctionImport">
<Annotation Term="Core.Description" String="Resource path for entity container child, can be relative" />
<Annotation Term="Core.IsUrl" />
</Term>

Refer to term in CSDL and URL Conventions

"Relative" has the same meaning as for other URLs: xml:base if present, Content-Location if present, request URL as last resort

Show
Add term to Core vocabulary <Term Name="ResourcePath" Type="Edm.String" AppliesTo="EntitySet SingletonEntity ActionImport FunctionImport"> <Annotation Term="Core.Description" String="Resource path for entity container child, can be relative" /> <Annotation Term="Core.IsUrl" /> </Term> Refer to term in CSDL and URL Conventions "Relative" has the same meaning as for other URLs: xml:base if present, Content-Location if present, request URL as last resort
Resolution:

Hide

https://www.oasis-open.org/committees/download.php/49613/odata-v4.0-wd02-part1-protocol-2013-06-19.docx
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml?rev=377
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Capabilities.V1.xml?rev=379

https://www.oasis-open.org/committees/download.php/49614/odata-v4.0-wd02-part2-url-conventions-2013-06-19.docx
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=380
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=380

https://www.oasis-open.org/committees/download.php/49615/odata-v4.0-wd02-part3-csdl-2013-06-19.docx
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edmx.xsd?rev=357
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edm.xsd?rev=377
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/MetadataService.edmx?rev=374

https://www.oasis-open.org/committees/download.php/49611/odata-atom-format-v4.0-wd02-2013-06-19.docx
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=382

https://www.oasis-open.org/committees/download.php/49612/odata-json-format-v4.0-wd02-2013-06-19.docx

Show
https://www.oasis-open.org/committees/download.php/49613/odata-v4.0-wd02-part1-protocol-2013-06-19.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml?rev=377 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Capabilities.V1.xml?rev=379 https://www.oasis-open.org/committees/download.php/49614/odata-v4.0-wd02-part2-url-conventions-2013-06-19.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=380 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=380 https://www.oasis-open.org/committees/download.php/49615/odata-v4.0-wd02-part3-csdl-2013-06-19.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edmx.xsd?rev=357 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edm.xsd?rev=377 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/MetadataService.edmx?rev=374 https://www.oasis-open.org/committees/download.php/49611/odata-atom-format-v4.0-wd02-2013-06-19.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=382 https://www.oasis-open.org/committees/download.php/49612/odata-json-format-v4.0-wd02-2013-06-19.docx

Description

Currently the resource path for top-level resources (direct children of entity containers) is only represented in the service document, and even there only for most, but not all top-level resources.

Adding resource paths that do not follow the URL conventions to the metadata document has two benefits:

the resource path can be stated for all top-level resources
the metadata document contains a superset of the information contained in the service document

Add term Core.ResourcePath to describe unconventional resource paths in CSDL

Details

Description

Attachments

Activity

People

Dates