[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[osee-dev] Relation Ordering Changes
|
A fully robust relation ordering solution needs to handle conflict
detection, concurrent modification, performance considerations, and an
API that supports graphical and non graphical use-cases. Here is a
summary of what has been discussed thus far.
We have identified 3 basics types of ordering; user-defined,
lexicographical order, and unordered. Each relation type will have a
default order type associated with it. If someone wants to specify a
sort order other than the default, or the type requires meta-information
such as user defined, then that information will be stored in an
attribute on the parent artifact.
The attribute with the order information will be an xml string and there
will be a maximum of one orderAttribute per artifact. This means that
multiple relationType to orderType pairs may be in the attribute.
Example xml:
<OrderList>
<Order relationType="name" orderType="someGuid"
list="guid1,guid2,guid3"/>
<Order relationType="name2" orderType="someGuid"
list="guid3,guid2,guid1"/>
</OrderList>
Thoughts, concerns, etc..?
-Andy
