Issue 14940: UML: Provide unique URL/URI Reference to/from Model Elements (uml2-rtf)
Source: Change Vision (Mr. Michael Jesse Chonoles, mjchonoles(at)yahoo.com)
Nature: Uncategorized Issue
Severity: 
Summary: Unique URL/URI Reference to/from Model Elements

In Model-Driven Development (MDD), the model is the repository of truth on the project. However, we recognize that the complete containment of all information on a project in a single tool repository is not a near-term solution. To this end, we need the ability to support explicit references from model elements to externals (such as documents, other types of models) and similar references back. 

This are not just pointers, we need the ability to incorporate information (e.g., documents, web pages, diagrams, pictures) from elsewhere and to support refreshing with current data, as well as the export of model information into external locations. Some simple examples:

1.    A driving requirements document may contain tables and pictures, a modeler will need direct access to these elements.

2.    A reviewer of a model may need to see diagrams where the appropriate and current icons substitute for the UML graphical elements.

3.    An organization may wish to publish documentation of a particular aspect of the model on the internet and wish that the visitors always obtained the latest information

Resolution: 
Revised Text: 
Actions taken:
January 11, 2010: received issue
Discussion: 

End of Annotations:=====
te: Mon, 11 Jan 2010 00:21:59 -0500
From: "Chonoles, Michael J" <michael.j.chonoles@lmco.com>
Subject: UML: Provide unique URL/URI Reference to/from Model Elements
To: "issues@omg.org" <issues@omg.org>
Thread-Topic: UML: Provide unique URL/URI Reference to/from Model Elements
Thread-Index: AcqSff4vHbZh4uBqSfKzT2646j5rIw==
Accept-Language: en-US
acceptlanguage: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 


Unique URL/URI Reference to/from Model Elements

In Model-Driven Development (MDD), the model is the repository of truth on the project. However, we recognize that the complete containment of all information on a project in a single tool repository is not a near-term solution. To this end, we need the ability to support explicit references from model elements to externals (such as documents, other types of models) and similar references back. 

This are not just pointers, we need the ability to incorporate information (e.g., documents, web pages, diagrams, pictures) from elsewhere and to support refreshing with current data, as well as the export of model information into external locations. Some simple examples:

1.    A driving requirements document may contain tables and pictures, a modeler will need direct access to these elements.

2.    A reviewer of a model may need to see diagrams where the appropriate and current icons substitute for the UML graphical elements.

3.    An organization may wish to publish documentation of a particular aspect of the model on the internet and wish that the visitors always obtained the latest information