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


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

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

Subject: [OASIS Issue Tracker] (COEL-158) Consistency of JSON object specifications

    [ https://issues.oasis-open.org/browse/COEL-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67021#comment-67021 ] 

Joss Langford commented on COEL-158:

I've pushed this through the rest of the document - just need to add the 'Required' text back in on section 5 and David's stepped hierarchy where needed.

> Consistency of JSON object specifications
> -----------------------------------------
>                 Key: COEL-158
>                 URL: https://issues.oasis-open.org/browse/COEL-158
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Improvement
>         Environment: Whole document
>            Reporter: Joss Langford
>            Assignee: David Snelling
> We have 3 standard table headings for JSON objects: Name, Value & Description. The way that 'Value' is populated varies through the document:
> - sometimes just the JSON type e.g. "Integer"
> - sometimes the JSON type with qualifier e.g. "String, HTTP URL"
> - sometimes our own definition e.g. "Two letter country code"

This message was sent by Atlassian JIRA

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