[OASIS Issue Tracker] Created: (ODATA-416) Non-normative text in conformance 3.1 of part 1

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Non-normative text in conformance 3.1 of part 1
-----------------------------------------------

                 Key: ODATA-416
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-416
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_WD01
            Reporter: Patrick Durusau


Under 13.1 oDATA Service Conformance Levels, the following non-normative text appears outside of a note:

*****
The conformance levels are design to correspond to different service scenarios. For example, a service that publishes data compliant with one or more of the OData defined formats may comply with the OData Minimal Conformance Level without supporting any additional functionality. A service that offers more control over the data that the client retrieves may comply with the OData Intermediate Conformance Level. Services that conform to the OData Advanced Conformance Level can expect to interoperate with the most functionality against the broadest range of generic clients.

Services are encouraged to support as much additional functionality beyond their level of conformance as is appropriate for their intended scenario. Services can advertise their level of conformance by annotating entity containers with the ConformanceLevel annotation defined in [OData-VocCap][OData-VocCap].
*****

The entire first paragraph is non-normative.

The second sentence of the second paragraph may be normative, but then it should not appear here, but rather under ConformanceLevel annotation.



-- 
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