[OASIS Issue Tracker] (OBIX-212) 5.4.2 Encoding

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://tools.oasis-open.org/issues/browse/OBIX-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Gemmill  updated OBIX-212:
--------------------------------

    Description: 
Using a name attribute with a slash attribute conflicts with the recommendation characters which should be used in names. Simpler design would be just to have a list of strs:
 
  <list name='encodings'>
    <str val='text/xml'/>
    <str val='application/json'/>
  </list>
 
Sort of same problem for 5.4.3 - typically name is to identify the role of the object within its parent, and names aren't typically used in lists.  So seems better to make the binding name part of the value via 'val' attribute.  Using the documentation URI as the value just seems like a lot of noise to me - I don't even understand what I'd put in there as a server, or why my client code would care about it.  So I'd prefer simple list of str objects.

  was:
Using a name attribute with a slash attribute conflicts with the recommendation characters which should be used in names. Simpler design would be just to have a list of strs:
 
  <list name='encodings'>
    <str val='text/xml'/>
    <str val='application/json'/>
  </list>
 
Sort of same problem for 5.4.3 - typically name is to identify the roll of the object within its parent, and names aren't typically used in lists.  So seems better to make the binding name part of the value via 'val' attribute.  Using the documentation URI as the value just seems like a lot of noise to me - I don't even understand what I'd put in there as a server, or why my client code would care about it.  So I'd prefer simple list of str objects.


> 5.4.2 Encoding
> --------------
>
>                 Key: OBIX-212
>                 URL: https://tools.oasis-open.org/issues/browse/OBIX-212
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: OBIX 1.1 XSD PR02
>         Environment: Brian Frank
>            Reporter: Toby Considine
>            Assignee: Craig Gemmill 
>             Fix For: OBIX 1.1 WD27
>
>
> Using a name attribute with a slash attribute conflicts with the recommendation characters which should be used in names. Simpler design would be just to have a list of strs:
>  
>   <list name='encodings'>
>     <str val='text/xml'/>
>     <str val='application/json'/>
>   </list>
>  
> Sort of same problem for 5.4.3 - typically name is to identify the role of the object within its parent, and names aren't typically used in lists.  So seems better to make the binding name part of the value via 'val' attribute.  Using the documentation URI as the value just seems like a lot of noise to me - I don't even understand what I'd put in there as a server, or why my client code would care about it.  So I'd prefer simple list of str objects.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)