OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ODATA-383) Examples, distinguishing from normative text

    [ http://tools.oasis-open.org/issues/browse/ODATA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33414#action_33414 ] 

Ralf Handl commented on ODATA-383:

Syntax snippets (ABNF, operator signatures) now use a paragraph style different from the examples. Examples keep the current style with black background while syntax snippets have a style more similar to the prose text: white background, no border, same font size as normal text, but using a monospace font and indented a little.

Given the problems we already face with broken links, disappearing anchors, and headings loosing their style I'd refrain from numbering all the examples. The time necessary for doing this (and keeping it working) is in my opinion better spent in improving the content of the documents.

> Examples, distinguishing from normative text
> --------------------------------------------
>                 Key: ODATA-383
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-383
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData CSDL, OData JSON Format, OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>            Reporter: Patrick Durusau
>             Fix For: V4.0_CSD02
> section 1 of odata-v4.0-csprd01-part1-protocol (the first sentence) provides:
> ****
> All text is normative unless otherwise labeled.
> ****
> But, section 3 says:
> ****
> Some sections of this specification are illustrated with non-normative example OData request and response payloads. However, the text of this specification provides the definition of conformance.
> All code examples in this document are non-normative.
> ****
> So when I read under
> ****
> The following Prefer header requests that the annotation with the term name subject within the display namespace be returned if applied:
>     Prefer: odata.include-annotations="display.subject"
> In the case that the client has specified the odata.include-annotations preference in the request, the service MAY include a Preference-Applied response header containing the odata.include-annotations preference to specify the annotations that MAY have been included in the response. This value MAY differ from the annotations requested in the Prefer header of the request. 
> ****
> Is the code block "Prefer: odata.include-annotations="display.subject"" non-normative followed by a normative interpretation of the example? 
> That seems risky at best if examples are truly non-normative and divorced from the normative portions of the text. 
> One strategy would be to label the code blocks as "Example" and simply have it follow normative text. And the normative text doesn't say anything about the example, they just appear as appropriate in the text. What a reader makes of them is on their watch. 
> A partial example from
> Accepting the normative text above: "For example, the following Prefer header requests" for the moment, it would then be followed by a typographically distinct region:
> Example:
> Ex.1 Prefer header requests all annotations within a metadata document to be returned:
>     Prefer: odata.include-annotations="*" 
> Ex.2 Prefer header requests that no annotations are returned:
>     Prefer: odata.include-annotations="-*" 
> and so on.
> I have inserted numbers to avoid the ambiguity of following/previous, which I will list as a separate issue.

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]