RE: [odata] [OASIS Issue Tracker] (ODATA-1400) Clarify that Validation.DerivedTypeConstraint can be used to restrict Edm.Untyped

I think of Edm.Untyped in a similar manner as null.  

I.e. Edm.Untyped is an assertion that an element does not have a Type.   

 

It would be better to create Edm.Type as the abstract base class for all types.  That would be a better place to apply constraints on the allowed subclasses.

 

George

 

 

-----Original Message-----

From:  <> On Behalf Of OASIS Issues Tracker

Sent: Monday, October 5, 2020 3:51 AM

To: 

Subject: [odata] [OASIS Issue Tracker] (ODATA-1400) Clarify that Validation.DerivedTypeConstraint can be used to restrict Edm.Untyped

 

 

[EXTERNAL EMAIL] 

 

Ralf Handl created ODATA-1400:

---------------------------------

 

             Summary: Clarify that Validation.DerivedTypeConstraint can be used to restrict Edm.Untyped

                 Key: ODATA-1400

                 URL: 
https://issues.oasis-open.org/browse/ODATA-1400

             Project: OASIS Open Data Protocol (OData) TC

          Issue Type: Improvement

          Components: Vocabularies

         Environment: Proposed

            Reporter: Ralf Handl

 

 

Type Edm.Untyped is ["conceptually an abstract base type for any OData type"|[https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_BuiltInAbstractTypes].]

 

This seems to imply that term [Validation.DerivedTypeConstraint|https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Validation.V1.md#DerivedTypeConstraint] can be used to restrict this to a list of concrete(r)
 types.

 

 

 

--

This message was sent by Atlassian Jira

(v8.3.3#803004)

 

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php