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


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

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

Subject: [OASIS Issue Tracker] (OBIX-209) Document Consistency

    [ https://tools.oasis-open.org/issues/browse/OBIX-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37079#comment-37079 ] 

Markus Jung commented on OBIX-209:

Removed "It is derived from the object literals of JavaScript, as defined in the ECMAScript Programming Language Standard (ECMA)". Which seems to be the problematic statement. The other parts of the intro could be shortened, but just provide a neutral description of the JSON format. 

> Document Consistency
> --------------------
>                 Key: OBIX-209
>                 URL: https://tools.oasis-open.org/issues/browse/OBIX-209
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Improvement
>          Components: ENCODINGS Specification
>    Affects Versions: ENCODINGS PR02
>         Environment: Toby Considine
>            Reporter: Toby Considine
> Compare intro to section 3 (Binary) and to section 4 (JSON). Also, if we are going to go into the history of JSON, it is more properly routed in the LISP family of exchanges from which the literals of JavaScript are derived. We should avoid formulations that can even begin to suggest disputation of history to the reader. The intro to 5 (EXI) is the clearest and least argumentative example.

This message was sent by Atlassian JIRA

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