 |
Where this path exists after GLR, a column name override could be specified as well. This rolepath alias should be entered in addition to the otft-alias. The otft and alias and rolefixes as visible in the otft-list. Additionally a rolepath name could be presented there as well.. If used as a rolefix it should be unique among the OTFT names. If not used as such, the path names should be unique within the names of paths. |
|
|
Path requires no name, for various rolepaths may be "joined" before the end result may be named. The "join"-part is not yet modelled. |
|
|
-- Table "PATH" -- -- "Named Path path <PathNo> is called <Path Name>." -- "Path <PathNo> exists." -- "Path <PathNo> is of type <Path Kind>." CREATE TABLE "PATH" ( "PATH_NO" "PATH_NO" NOT NULL, -- PathNo "PATH_NAME" "PATH_NAME", -- Named Path/Path Name "PATH_KIND" "PATH_KIND" NOT NULL, -- Path Kind "COMMENT" "COMMENT" NULL, -- Path Comment PRIMARY KEY ("PATHNO") ); -- Table "PATH_PART" -- -- "Path <Path>.<Part No>, references <Role>." CREATE TABLE "PATH_PART" ( "PATH" "PATH_NO" NOT NULL, -- Path "PART_NO" "PART_NO" NOT NULL, -- Part No "ROLE" "ROLENO" NOT NULL, -- PathPart Role/Role "COMMENT" "COMMENT" NULL, -- Path Part Comment PRIMARY KEY ("PATH", "PART_NO") ); -- Table "PATH_PART_EXPRESSION" -- -- "Path <Path>.<Part No> uses verbalization with <Expression>." CREATE TABLE "PATH_PART" ( "PATH" "PATH_NO" NOT NULL, -- Path "PART_NO" "PART_NO" NOT NULL, -- Part No "EXPRESSION" "EXPCODE" NOT NULL, -- Part Expression / Expression / ExpCode PRIMARY KEY ("PATH", "PART_NO", "EXPRESSION") ); |
|
|
In addition to simply documenting the rolepaths, they may be used for fixing (aka overruling column names after glr), simple select paths for xml or other hierarchy purposed, of for future joining of various rolepaths. So, the PATH_KIND needs to be extended for future possibilities. Also some COMMENT or CUSTOM_ATTRIBUTE needs to be applicable to PATH and PART. Also a non destructive GLR could perhaps be implemented here. It requires all rolepaths to be build, and than duplicate these paths for a specific GLR implementation which have the roles removed from them. This would require the PATH to include a SCOPE which is set to GLR_SQL, G_XSD, etc.. |
|
|
CaseTalkRolePathModel.png (22,926 bytes) |
|
|
A subset constraint should also be applicable to roles in this rolepath parts. |
|
|
"Path Part" should get a "Role Replace Fix" to overcome the limited 'fixes in role'. This allows the modelers to use role fixing (only full replacefix) as proper naming columns in database implementations. These rolefixes are only used for naming implementations. |
|
|
The naming of rolepaths is always and limited to a lexiclization path starting at a specific role. The parts determine the depth of the named path. |
|
|
Joining various RolePaths is another story indeed. The initial implementation should support lexicalization path naming. |
- Anonymous
