Service Endpoint Technical Asset

I agree with your Service Endpoint choice.  It is lacking a few properties that you'll want to add for yourself so build a Technical Asset extension model (which you likely already have :) to capture these.  If that first screenshot is a website, you should capture that in the 'location link' property of the Enterprise Context property group.  You could add 'xml link' and 'json link' to this property group so that the actual endpoint URLs are associated to each Service Endpoint.  These would be datatype properties with a value of 'anyURI'.  Alternatively, you could treat each XML link and JSON link as instances of Service Endpoint.  This decision would depend on the granularity you are after.

Regarding the fun message...I would go to that boolean property and deactivate it for now.  This field is likely auto populated by some of the lineage business logic.  I'll make sure a ticket is created to dig into this deeper.  Deactivating the property will get this message out of your way and will not hinder your development in any way.

All the best,

Jesse

I am trying to determine where the data in the below image belongs in EDG. After some definition reading and relationship traversing I landed on Service Endpoint (instead of Software Service or Software API) . What questions should I be asking myself to determine if this is, in fact, the correct class to be using? I selected Service Endpoint because it has a relationship back to an Interoperable class using the "depends on data from" property.

Service Endpoint does not have a property for the endpoint URL. Does that mean I am using the wrong class?

 

Also, I am getting this fun message:

I went and looked at the model and that field is a boolean it says, but where am I supposed to capture in the incoming and outgoing flows in order to populate this section?

 

 

Apologies if this is not enough information to answer my question.