First I should introduce UML profiles. A UML profile is a way of extending metaclasses in the UML metamodel with virtual specialization hierarchies, semantics, constraints, and graphic images. (for hard-core UML metamodel geeks, the reason I use the word virtual is because a stereotype does not technically have a generalization relationship with a UML metaclass, it has a special association with it, called an Extension.) A stereotype can have any number of pseudo meta-properties, called tagged values. Modern UML tools allow a modeler to add values to a stereotyped meta-class instance, such as a UML Class. For example, I can create a stereotype that extends a UML Class, called Resource, that has a URI. Indeed, this is what I've done in the OWL profile.
A UML stereotype can further specialize another UML stereotype, thus adding to the virtual specialization hierarchy of a UML metaclass. For example, I can define a Property stereotype that specializes Resource, and I can further define a Transitive Property stereotype that specializes Property. I can then apply the Transitive Property to a UML Association End, which tells the transformation software how to generate the intended OWL statements and makes it possible to define transitive properties in UML.
In the next posting (Part 2) I will describe the top of my OWL stereotype specialization hierarchy. In subsequent postings I will descend the specialization hierarchy and describe each specialization in detail.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f81582b5-28e5-46d1-8f5e-f45d9cd63af8)
1 comment:
Hi,
I am so glad i found this.
I was considering doing the same thing. Brilliant. Exactly what the world needs.
Big - questions - can I get a copy of the profile?
What tool are you using?
I use Enterprise Architect, and am happy to do some porting work if necessary.
Don Lawn
don_lawn@hotmail.com
Post a Comment