← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Created: (ODATA-485) Clarify that element notation of UrlRef expression can directly contain a literal string that is a URL

From
OASIS Issues Tracker <>
Date
2013-08-21T07:16:23+00:00
ID
235643081.5011377069399812.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Created: (ODATA-485) Clarify that element notation of UrlRef expression can directly contain a literal string that is a URL
Clarify that element notation of UrlRef expression can directly contain a literal string that is a URL
------------------------------------------------------------------------------------------------------

                 Key: ODATA-485
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-485
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData CSDL
    Affects Versions: V4.0_CS
         Environment: [Proposed]
            Reporter: Ralf Handl
             Fix For: V4.0_ERRATA01


The second sentence in section 14.5.15 Expression UrlRef states that

    The edm:UrlRef element MUST contain exactly one expression of type Edm.String. 

This caused questions whether the correct form is

    <UrlRef>http://some/url</UrlRef>

or

    <UrlRef><String>http://some/url<String></UrlRef>

Both forms are allowed and yield the same result, but the shorter first form is preferred

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
← Prev in month ← Prev in thread
Next in thread → Next in month →