[Moims-sc] MAL ObjectRef

[Stefan.Gaertner at dlr.de]

Dear all,

do we really need two names? Why don’t we use something like that:

ObjectRef<ObjectToBeReferenced>
for what we previously called StaticObjectRef. “ObjectToBeReferenced” would be replaced with the concrete allowed object type.

ObjectRef<any>
for FullObjectRef or ObjectRefExplicit.

This makes the type information much clearer and is actually similar to how we treat lists of different types. Otherwise, what would your proposal be to show the type of the object to be referenced?

Cheers,
Stefan


From: MOIMS-SC <moims-sc-bounces at mailman.ccsds.org> On Behalf Of Roger Thompson via MOIMS-SC
Sent: Donnerstag, 18. November 2021 20:43
To: 'Coelho, César' <cesar.coelho at cgi.com>; 'Mehran Sarkarati' <Mehran.Sarkarati at esa.int>; moims-sc at mailman.ccsds.org
Subject: Re: [Moims-sc] MAL ObjectRef

OK with me.

From: Coelho, César <cesar.coelho at cgi.com<mailto:cesar.coelho at cgi.com>>
Sent: 16 November 2021 14:08
To: Mehran Sarkarati <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>; roger.rocketbrain at btinternet.com<mailto:roger.rocketbrain at btinternet.com>; moims-sc at mailman.ccsds.org<mailto:moims-sc at mailman.ccsds.org>
Cc: Peter van der Plas <Peter.van.der.Plas at esa.int<mailto:Peter.van.der.Plas at esa.int>>
Subject: RE: MAL ObjectRef

Hi Roger,

Can we call it ObjectRefExplicit ?

Best regards,
César Coelho

Dr. César Coelho
CGI Deutschland B.V. & Co. KG  | Space
Mornewegstr. 30 | 64293 Darmstadt | Germany
T: +49 173 54100 45 | email: cesar.coelho at cgi.com<mailto:cesar.coelho at cgi.com>

Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben.



From: Mehran Sarkarati <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>
Sent: Monday, November 15, 2021 5:28 PM
To: roger.rocketbrain at btinternet.com<mailto:roger.rocketbrain at btinternet.com>; moims-sc at mailman.ccsds.org<mailto:moims-sc at mailman.ccsds.org>
Cc: Coelho, César <cesar.coelho at cgi.com<mailto:cesar.coelho at cgi.com>>; Peter van der Plas <Peter.van.der.Plas at esa.int<mailto:Peter.van.der.Plas at esa.int>>
Subject: Re: MAL ObjectRef

EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.


Ok for me.

Regards
Mehran

From: "roger.rocketbrain at btinternet.com<mailto:roger.rocketbrain at btinternet.com>" <roger.rocketbrain at btinternet.com<mailto:roger.rocketbrain at btinternet.com>>
Date: Friday, 12 November 2021 at 19:20
To: "moims-sc at mailman.ccsds.org<mailto:moims-sc at mailman.ccsds.org>" <moims-sc at mailman.ccsds.org<mailto:moims-sc at mailman.ccsds.org>>, Mehran Sarkarati <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>
Cc: "cesar.coelho at cgi.com<mailto:cesar.coelho at cgi.com>" <cesar.coelho at cgi.com<mailto:cesar.coelho at cgi.com>>, Peter van der Plas <Peter.van.der.Plas at esa.int<mailto:Peter.van.der.Plas at esa.int>>
Subject: MAL ObjectRef

Hi All,

As I am currently reviewing the MPS Information model with respect to usage of ObjectRef and the new StaticObjectRef MAL::Attribute types, I would like to make the following observation and resulting recommendation.

The great majority of object references are to objects of known type – the “StaticObjectRef”, with only a small minority requiring the full context ObjectRef.

Could I therefore propose, that the attribute type “ObjectRef” is used for the more common attribute type pointing to a fixed type (the “static” object ref), and that we find a new name for the rarer full object ref that includes the Area and Type – my suggestion is “FullObjectRef”.
I think it makes sense to have the simpler name for the most commonly used type – plus it has the advantage that I don’t have to change all the references in the existing MPS model!

Cheers,

Roger
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int<mailto:dpo at esa.int>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20211119/abdad46d/attachment-0001.htm>