News

Added automatic builds
Each day a ZIP-file is created via cron.
The builds consist of XMI, XSD, DocBook, PDF and graphs in dot, svg and png.
Added basic validation for names
installed module for validation, some rules for object and package names have been defined.
Added help for creating and managing the model
Guidelines for naming and propeties.
Added stage-tagging for objects
Re-arranged "Status" and added field for Stage, filter added on objects page.
Changes for Datatype
Datatype taxonomy is replaced by a datatype content type, to create a new one go to /node/add/datatype. You can specify basic documentation of the datatype and specify enumerated values. A datatype must be placed in a package.

StrictOrderList

Subtype of collection supporting a strict order list. When realizing this class replicate the inherited property hasRelationSpecification and replace documentation with the following:
"Fixed to List. A strict ordered asymmetric relationship expressed as a list: Anti_Reflexive, Anti_Symmetric, Transtive"

ListItem

defines the order and member of a list item

OrderedListRelation

This class describes directional (ordered) relations between two objects, a source and a target. The relationship is only implied between the two classes and the members of those classes. For example if the relationship is defined by setting the Relation Specification to ParentChild when realizing this class, the parent designated in the domain is the parent of all the objects listed in a collection identified as the range. A different class should be realized for each type of Relation Specification required by the applied use.

NewCollectionPattern

New collection pattern as discussed at Lawrence Sprint
(note that some class names are not final until we retire existing classes with same/similar names)

REALIZATION
(by realizing the abstract extension base for list and listRelation the number of needed subtypes can be recorded, added to or constrained to as appropriate. This could be a realization of an UnorderedList, StrictOrderList, or OrderedListRelation).

ProcessOverview

Process is an implementation of an algorithm. It is the series of steps taken as a whole. It is decomposable into ProcessSteps, but this decomposition is not necessary. Process Overview should be used when a description of the process in general is all that is desired.

DesignOverview

High level, descriptive, human informative, design statement The design may be used to specify how a process will be performed in general. This would most commonly be used in a Codebook along with an AlgorithmOverview and a MethodologyOverview. The design informs a specific or implemented process as to its general parameters. Supports specification of any realization of Goal.

AlgorithmOverview

High level, descriptive, human informative, algorithm statement used to describe the overall methodology. This would most commonly be used in a Codebook along with a MethodologyOverview and a DesignOverview.The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.

MethodologyOverview

High level, descriptive, human informative methodology statement used to describe the overall methodology, identify related design, algorithm, and process information. A methodology is normally informed by earlier research and clarifies how earlier research methods were incorporated into the current work.
This would most commonly be used in a Codebook along with an AlgorithmOverview and a DesignOverview. Note that Process may be described in more detail than a high level overview.

MethodologyOverviewPackage

Descriptive Methodology provides the basic means of describing in methodology in a descriptive, or human informative, terms rather than machine actionable content. Where available, specific use realizations of the Methodology Pattern should be created and/or use. All of these support general description as well as machine actionable description and may contain additional, defined metadata related to the specialized use.

RankingResponseDomain

A response domain capturing a ranking response which supports a "ranking" or "Ordering" of provided categories.
Note: This item still must be modeled and is incomplete at this time.

Pages

Subscribe to DDI Moving Forward RSS