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=67009#comment-67009 ] 

David Snelling commented on COEL-158:

Revision 57 includes example tables for this issue applied to Query Request and Response.

However, the 'Value' column was not included, as it duplicated information in the type column and occationaly the description (e.g. only in the case of Pseudonymous Key).

Dave is not entirely happy with the reprsentation of the Key column, as the full key needs to be included in some way. he schema make it clear, but the table should be consistent as well. Thoughts welcome

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