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-98) 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"


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

Mark Biamonte  commented on ODATA-98:
-------------------------------------

Sections 3.8.1 and 3.8.2 also use the terms internally and externally.  Also what does "next to" mean in the proposal for 3.8?  Is it valid for an annotation of an array or primitive to come before or after the construct or must it always come before?

In addition to the proposed change to 3.8 above how about something like the following for sections 3.8.1 and 3.8.2

3.8.1
------
Old: 
This section applies when annotating a name/value pair for which the value is represented as a JSON object.
Each annotation MUST be applied internally. Each annotation MUST be represented as a single name/value pair.

Proposed:
This section applies when annotating a name/value pair for which the value is represented as a JSON object.
Each annotation MUST be applied within the object. Each annotation MUST be represented as a single name/value pair.

3.8.2
------
Old:
This section applies when annotating a name/value pair for which the value is not represented as a JSON object.
The set of all annotations that apply to this name/value pair MUST be applied externally. This set of annotations is represented as a single name/value pair.

Proposed:
This section applies when annotating a name/value pair for which the value is not represented as a JSON object.
The set of all annotations that apply to this name/value pair MUST be be placed next to the annotated model construct. This set of annotations is represented as a single name/value pair.




> 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
> -------------------------------------------------------------------------------------
>
>                 Key: ODATA-98
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-98
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Mark Biamonte 
>            Priority: Minor
>             Fix For: WD01
>
>
> Section 3.8 uses the phrase "express an annotation internally or externally" without defining the terms.
> Instead just point out that the representation of annotation depends on the representation of the annotated model construct.

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