odata message

Subject: [OASIS Issue Tracker] Commented: (ODATA-534) Tag type definition in Core should have default boolean value = true

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Tue, 1 Oct 2013 07:10:40 +0000 (UTC)

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

Ralf Handl commented on ODATA-534:
----------------------------------

DefaultValue seems to be more related to using a type, e.g. in a property or term, and less to defining a type.

Also function and action parameters don't allow the DefaultValue facet, so we'd have to decide whether type definitions with a DefaultValue cannot be used as parameter types, or whether the DefaultValue is simply ignored when used as a parameter type.

So the current situation seems at least as good, and definitely is easier to "apply".

> Tag type definition in Core should have default boolean value = true
> --------------------------------------------------------------------
>
>                 Key: ODATA-534
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-534
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> In the core vocabulary we define a type definition for terms used as tags as:
>       <TypeDefinition Name="Tag" UnderlyingType="Edm.Boolean">
>         <Annotation Term="Core.Description" String="This is the type to use for all tagging terms" />
>       </TypeDefinition>
> The intention of this was to allow the mere presence of a term (such as IsLanguageDependent) to be true.
> However, we neglected to define the default value as part of the TypeDefinition, so each use of the Tag must ALSO specify the default value of true (which kinda defeats the purpose).
> Perhaps this was because we don't currently list DefaultValue (or Nullable) in the allowable facets for a type definition (why?)

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