You are here:   Community > Forums
Register   |  Login
 
CIM EA ForumCIM EA ForumCollaborationCollaborationCIM ProfilesCIM ProfilesHow to share profilesHow to share profiles
Disabled 
Previous
 
Next Next
New Post
 8/24/2010 4:35 PM
 
Is it possible to save and share just the profile and then load it into a different base model?

If not, does that mean we have to post the full EAP model in order to share a profile?
New Post
 8/24/2010 5:07 PM
 
You can do this actually, to a point. If the base models came from the same source -- and so all the objects had the same GUIDs -- you could do this with the XMI import/export or something similar. But it isn't smart enough to try resolving objects by name / path. 

It isn't an explicit use case we are addressing right now though, and problems could arise if the two base models had differences in package structure or if classes were deleted. We will start adding support and tutorials for this moving forward though, as it is a good way to share profiles.
New Post
 8/24/2010 9:27 PM
 

We might think about taking an approach where a specific version of a model, say the CIM, is loaded to a folder here on cimea.org.  Then, all profiles built using that base model could be loaded ‘under’, from a hierarchal perspective, that base model.  If someone wants to create a new base model , CIM or not, they could load it to the site and start profiles profiles for it.  This is more of a organizational/governance approach to the problem but it might accomplish what a ‘community’ of users is looking for?

New Post
 8/25/2010 12:28 PM
 
I would recommend that each version of the CIM have its own location where the profiles can be uploaded.  I ran a quick test on Asset Models using IEC61970cim14V13_IEC61968cim10v28 and IEC61970cim13v19_IEC61968cim10v18.  The profiles generated by each of these models actually differ in content much less GUID values.  The differences are noted below:

IEC61970cim14V13_IEC61968cim10v28
    AssetModel
        corporateStandardKind
        modelNumber
        modelVersion
        usageKind
        weightTotal
        AssetModelCatalogueItems


IEC61970cim13v19_IEC61968cim10v18
    AssetModel
        corporateStandardKind
        modelNumber
        modelVersion
        usageKind
        weightTotal

While I could theoretically resolve the two models, the reality is that the profile created is very specific to the model used to create that profile.  The mixing of the profiles created from different versions of the CIM model could lead to usability issues when loading it into a base model.

If the profiles are segregated by CIM version then there should be no need to post the full EAP file.
New Post
 8/25/2010 5:57 PM
 
I think we do need to specify exactly which base model a profile is built on. I'll see about organizing the forums differently to make that kind of distinction clear. 

For what it is worth, users are now able to upload some documents via the 'Document Manager'. Just XML documents and zip files for now. RDF and XSD are forthcoming; eap files should always be zipped up and even then might not be optimal in terms of size. 

We've given the users considerable freedom in where they put these artifacts, although we expect everyone to be reasonable about creating new folders and the like. We will have a best practices document when we write up a mini-how to on how to use the document manager. 

In terms of the CIM, we should either host or link (depending on CIMUGs preference) to the major public versions of the CIM on here for convenience sake, and try to keep all hosted profiles centered around those. But if users have some other UML model with which they want to share profiles on, I see no reason to disallow posting of full (zipped) EAP files. 
Disabled 
Previous
 
Next Next
CIM EA ForumCIM EA ForumCollaborationCollaborationCIM ProfilesCIM ProfilesHow to share profilesHow to share profiles

Download

Get v1.3.16 
of the tool.
 
Download the latest version of CIM EA