Issues raised against the DEXlib infrastructure.

Issue file: dexlib/docs/issues/issues.xml

OTHER issues

Open issue Issue: TJT-1 by Tim Turner (06-03-11) minor_technical issue
Resolution: Accept. Status: open

It appears that the DEXLIB infrastructure does not permit the removal of attributes from an entity when used from a module. However, the facility for handling module entity usage seems to indicate that it is supported. For example, it is possible to state that a subset of the module entities be used and that for a specific entity, and that none, all or a subset of the attributes can be used. However, the attribute subset mechanism appears to be at fault. For example, in the usage section for referencing_task it would be useful to be able to remove the task_method.objective attribute so that the task_objective entity can be left out as this is not required for referencing purposes. Below is one possibility afforded by the relevant dtd. <entity entity_id="Task_specification_arm.Task_method" mode="SUBSET"> <attribute mode="REMOVE" attribute_id="Task_specification_arm.Task_method.Objective"/> </entity>" Another possibility would be to again use SUBSET, but to leave an empty list (i.e. no attributes to be left in when used). Both options would appear to be possible, but neither appear to work. Removing entities without also the ability to remove attributes which may refer to them would not seem a optimal solution.

Open issue Issue: RBN-1 by Rob Bodington (03-11-04) minor_technical issue
Resolution: Accept. Status: open

When using an entity into a capability, you can add or replace the description of an entity / attribute that is pulled from stepmod. If you have two capabilities that use the same entity, you should be able to specify the capability in which the entity is described. Otherwise you can end up with two capabilities providing the different descriptions to the same entity.

Perhaps we should enforce that an entity is only described in one place?

We perhaps need a check in the DEX to see if an entity/module is only brought in once

Open issue Issue: RBN-3 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: open

<express_ref> currently links to stepmod. It should ideally link to any capability that provides additional descriptions.

Open issue Issue: RBN-11 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: open

Summary of ref data application There needs to be a section that list WHERE the ref data can be applied. In other words the entities that can be classified.

Open issue Issue: RBN-12 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: open

Capability conventions Need the XSL to produce a section that describe the diagram conventions and the use of reference data.

Open issue Issue: RBN-13 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: open

DEX deltas Investigate "marking" of entities in the usage section as being for reference only.

Open issue Issue: RBN-21 by Rob Bodington (04-09-30) minor_technical issue
Resolution: Accept. Status: open

There needs to be a better way to index into capabilities from business concepts. The key words are not sufficient. A solution would be to develop a set of business terms and concepts, taking the PLCS terminology as a start. There then needs to be an index into the capabilities. The capabilities then also need to be able refer back into business terms.

Open issue Issue: RBN-22 by Rob Bodington (04-11-24) minor_technical issue
Resolution: Accept. Status: open

The introduction should include the a description of how reference data should be used. It should include a definition of the use of IGNORE strings to indicate that a compulsory string has not been provided. Instead classification is used.

Open issue Issue: RBN-23 by Rob Bodington (04-11-10) minor_technical issue
Resolution: Accept. Status: open

The image displays should scale according to the screen size

Open issue Issue: RBN-26 by Rob Bodington (05-06-13) minor_technical issue
Resolution: Accept. Status: open

We do not need a DEX team with a capability

Open issue Issue: RBN-32 by Rob Bodington (05-09-05) minor_technical issue
Resolution: Accept. Status: open

When displaying the superclasses / subslcasse in the RDL browser, the classes should be sorted.

Open issue Issue: RBN-37 by Rob Bodington (05-10-01) minor_technical issue
Resolution: Accept. Status: open

It has been agreed that the class libraries holding OWL classes (OWL files) will be identified by URNs in the DEXs. DEXlib does not currently support this. In fact, all classes are assumed to be in one OWL file and the XSLT resolves the links. E.g. a hyper link is created by <rdl_ref id="Manufacturer_of" rdl="plcs_owl"/>. The XSL then searches the owl file to find the class to link to. Instead it should be <rdl_ref id="Manufacturer_of" rdl="urn:plcs:rdl:std"/> So there is no way to distinguish between OWL classes that are part of or proposed to be PLCS reference data and OWL classes that are within the context of a business context.

The proposal is to provide a register of URNs in dexlib that will allows an owl file (or set of files) to be indexed by a URN. This will mean the links are now:
<rdl_ref id="Manufacturer_of" rdl="urn:plcs:rdl:std "/>
The URN urn:plcs:rdl:std will resolve to the set of OWL files that are part of or proposed to be PLCS reference data. A URN such as urn:plcs:rdl:ndlo wold resolve to the OWL files that contain the NDLO reference data used in the NDLO business concepts (those that have not been standardized)

In addition to the links from within a capability/DEX, the browsing of the RDL will need to be modified to accommodate the URNs. Currently, just the list of owl files is displayed.

XSL would also be written to summarize the use of the OWL classes in a business concept, capability ect. This will facilitate the harmonisation of reference data.

DEXLib still contains some code and files for reference data that predate the decision to move to OWL. These should be removed. This will also mean deleting the current directories dexlib/data/refdata/ which contain the non OWL reference data and moving the OWL files from dexlib/data/refdata/plcs_owl/ to dexlib/data/refdata/

Comment: (Rob Bodington 06-06-12)

The following changes have been made to address this:

  1. Moved all the OWL files from: dexlib/data/refdata/plcs_owl to: dexlib/data/refdata

  2. Modified dexlib/data/refdata/rdl_index.xml so that it contains a register of OWL files that correspond to a given RDL URN. Note that ideally, one OWL file should have one URN. However, we are importing a number of OWL files that are in development by modellers, e.g. dexlib/data/refdata/plcs-rdl-rbn.owl Hence several OWL files can be referenced under on URN. I.e, they are logically the same file

    The URN register: dexlib/data/refdata/rdl_index.xml has the following format: (note there can be many URNs defined)

    <rdl_index>
    <urn_ref urn="plcs:rdl:std">
    <!-- PLCS standard OWL -->
    <owl_file file="plcs-rdl.owl"/>
    <!-- PLCS registered OWL -->
    <owl_file file="plcs-registered.owl"/>
    <!-- PLCS proposed OWL -->
    <owl_file file="plcs-proposed.owl"/>
    <!-- Modeller files -->
    <owl_file file="plcs-rdl-rbn.owl"/>
    </urn_ref> </rdl_index>

  3. All XML elements that refer to classes have been modified. It is now necessary to specify the URN of the RDL that holds the class. E.g the following have changed:

    • The capability section specifying the classes used:
      <ref_data>
      <class_ref id="Designer_of" urn="plcs:rdl:std"/>
      </ref_data>
    • A reference to a class in the main text:
      <rdl_ref id="Designer_of" urn="plcs:rdl:std"/>
    • A reference to a class in a template parameter: <param_in name="la_class_name" type="CLASS">
      <!-- as the type is a class, list the possible classifications -->
      <classifications>
      <!-- a list of all possible classifications that can be used -->
      <class id="Identifier_type" urn="plcs:rdl:std"/>

    Modified: dexlib/xsl/dex/common.xsl dexlib/xsl/dex/template.xsl

  4. Modified: mk_capability.wsf so that the examples are correct

  5. Modified the main pages for browsing the RDL so that the pages are sorted by URN and the URNs are shown in the class summaries. shown.

    Modified: dexlib/xsl/owl_rdl/dexlib_rdl_index.xsl dexlib/xsl/owl_rdl/inline_issues.xsl dexlib/xsl/owl_rdl/plcs-refdata-likeexpress.xsl dexlib/xsl/owl_rdl/rdl_clause.xsl

  6. Modified the DTDs to reflect the changes: dexlib/dtd/dex/text.ent dexlib/dtd/dex/templates.ent
  7. Modified the help files to reflect the changes: dexlib/help/dex/dvlp_tags.xml
  8. Modified all business concepts, capabilities and DEXs

Open issue Issue: RBN-38 by Rob Bodington (05-10-24) minor_technical issue
Resolution: Accept. Status: open

The RDL index accessed from the tools menu should list the OWL files and allow the OWL file to be viewed and downloaded.

Open issue Issue: RBN-40 by Rob Bodington (05-10-25) minor_technical issue
Resolution: Accept. Status: open

The DEX should contain a pointer to all the OWL files that it uses.

Open issue Issue: RBN-42 by Rob Bodington (05-11-28) minor_technical issue
Resolution: Accept. Status: open

There are a number of blocks of text in the DEXs that are common to every DEX - it would be useful to maintain these centrally and allow each DEX to use from / pull the text into each dex.

Open issue Issue: RBN-43 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: open

Modify the scripts generating the DEX to automatically use the messaging, assigning_ref_data capabilities

Open issue Issue: RBN-45 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: open

The HTML version of the DEX capability dependencies (as accessed on DEX "developer" menu )and the XSL version are different. Add a note to show that the representing subsumes the referencing capability.

Open issue Issue: RBN-51 by Rob Bodington (05-11-06) minor_technical issue
Resolution: Accept. Status: open

Support business reference data in templates

There are currently three templates specifying different ways of assigning reference data:

Assigning_reference_data is used by default in most templates that need reference data e.g. assigning_organization. However, in different situations in business concepts, each of the three approaches to assigning reference data is appropriate. This then raises the question as to how to represent this within a template such as assigning_organization.

The class parameters passed in to the templates should be modified to allow each of the three approaches to be used in a business concept.

Open issue Issue: SMB-1 by Sean Barker and Leif Gyllstrom (05-12-09) minor_technical issue
Resolution: Accept. Status: open

There is no way to assign issues against reference data.

Open issue Issue: RBN-55 by Rob Bodington (06-02-22) minor_technical issue
Resolution: Accept. Status: open

The "DEX Module dependencies" should be sorted

OTHER issues

Closed issue Issue: TJT-2 by Tim Turner on behalf of UK MoD TES/ILS and Eng Pol under TLSS Development Programme. (06-12-04) minor_technical issue
Resolution: Accept. Status: closed

Within the templateX/dvlp/issues.xml body, the list of possible field types available for an issue is not synchronised with the sections found within a template. Hence it is not possible to target the respective section where the issue arises; e.g. the fields such as Model Diagrams, Input Parameters, Reference Parameters, Instantiation path, Instance Diagrams and Characterizations. Those supported field sections which are available within templates (e.g. Cover and Contents) do not appear to load the respective issue when one of those fields is targetted.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=657

Closed issue Issue: TJT-3 by Tim Turner on behalf of UK MoD TES/ILS and Eng Pol under TLSS Development Programme. (06-12-04) minor_technical issue
Resolution: Accept. Status: closed

Given that a template may be placed "in situ" (inside the capability whose functionality is supported by the template), it would seem natural that any issues within a template that was shown "in situ", would also be visible "in situ". Hence the capability should also refer (or collect) the template issues as well as the template(s).
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=658

Closed issue Issue: TJT-4 by Tim Turner on behalf of UK MoD TES/ILS and Eng Pol under TLSS Development Programme. (06-12-04) minor_technical issue
Resolution: Accept. Status: closed

Issues defined against a template (within templateX/dvlp/issues.xml), do not appear within the list of issues returned from the DEXLIB menu item "Tools", "All issues" option. I assume that template issues are equally valid issues and should be visible here.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=659

Closed issue Issue: TJT-5 by Tim Turner on behalf of UK MoD TES/ILS and Eng Pol under TLSS Development Programme. (06-12-04) minor_technical issue
Resolution: Accept. Status: closed

Issues defined against a template (within templateX/dvlp/issues.xml), do not appear to be accounted for in the Dexlib masterlist of capabilities (dexlib menu Tools/Capabililty Summary), where the table provides a total of all the issues for a specific capability. Given that the templates are visible "in situ" for a capability, should not the template issues also form part of the overall issues for that capability? If not, should the table have additional rows/columns to provide a place for the fact that a template (which implement the functionality of a capability), may have an issue?
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=660

Closed issue Issue: RBN-2 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: closed

We need to be able to generate an HTML version of the DEXs. This requires an ANT build and a modification to the XSL so that it can accommodate SAXON as well as MSXML.

Comment: (Rob Bodington 05-11-06)
The ANT build script has been implemented dexlib/utils/dex/build.xml and XSL modified.

Closed issue Issue: RBN-4 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: closed

Need to extend the infrastructure to store and display the test data.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=661

Closed issue Issue: RBN-5 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: closed

Need to extend the infrastructure to store an display the long form express and Part28 XML schema of a DEX.
Comment: (Rob Bodington 05-11-06)
Updated

Closed issue Issue: RBN-6 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: closed

Need to investigate what are the publication requirements of OASIS and then need to modify the infrastructure to accommodate them.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=652

Closed issue Issue: RBN-7 by Rob Bodington (03-11-09) minor_technical issue
Resolution: Accept. Status: closed

Need to provide a dictionary of definitions. These should be pulled from the modules and if appropriate (unlikely) overwritten or alternatives provided.
Comment: (Rob Bodington 05-11-06)
A terminology dictionary has been provided

Closed issue Issue: RBN-9 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: closed

Remove issues from the front page of the capability and access via a button as in stepmod.

Closed issue Issue: RBN-10 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: closed

Dependency check Need to check that all dependent capabilities are included in the DEX
Comment: (Rob Bodington 05-11-06)
Updated

Closed issue Issue: RBN-14 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: closed

DEX ref data We need to investigate whether we can have multiple class_of_classes as filters when a capability is used in a DEX. E.g. on class_of_class for the generic classes of a capability, i.e. applicable to all DEXs and one for the DEX specific classes
Comment: (Rob Bodington 05-11-06)
NO longer applicable

Closed issue Issue: RBN-15 by Rob Bodington (04-01-19) minor_technical issue
Resolution: Accept. Status: closed

When displaying a capability from within a DEX, the usage section just displays the entities etc that have been explicitly brought in by the capability.

In any given DEX, an entity may be brought in by multiple capabilities. Hence it may have different descriptions in the different capabilities and it may have be classified by different ref data.

Furthermore, when displaying the capability from within the DEX there is no way to filter the ref data according to the class_of_class specified at the DEX level.

Therefore I propose to add a section to all DEXs that displays the EXPRESS model summary.

This will collect all the entities from the capabilities that a DEX uses. It will highlight where multiple descriptions are provided. It will indicate whether the entity should be removed or is for reference etc. It will filter the ref data according to the class_of_class specified in the DEX.

Comment: (Rob Bodington 05-11-06)
Updated

Closed issue Issue: THX-1 by Tom Hendrix (04-03-10) minor_technical issue
Resolution: Accept. Status: closed

dex_index.htm does not work right. URL to css wrong.
Comment: (Rob Bodington 05-11-06)
Updated

Closed issue Issue: RBN-16 by Rob Bodington (04-03-04) minor_technical issue
Resolution: Accept. Status: closed

The long form generator should use the DEX name as the schema name through out. Will need to replace the string name in the where rule and functions. Where there is an explicit subtype definition in an entity - the long form generator must prune out the subtypes that are not used in the long form. Re-declaration of derive attributes
Comment: (Rob Bodington 07-03-01)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=642

Closed issue Issue: RBN-17 by Rob Bodington (04-03-18) minor_technical issue
Resolution: Accept. Status: closed

The express definition in a capability should be extracted from the long form NOT the module definition - this is to show the renaming of attribute
Comment: (Rob Bodington 07-03-01)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=643

Closed issue Issue: RBN-18 by Tim Turner (04-03-20) minor_technical issue
Resolution: Accept. Status: closed

when looking at the generated longform, it documents that certain entities have been removed by a capability. Is it possible that the documentation here be adjusted to include the *name* and/or *number* of the capability that has removed an entity? It would make tracking down where this has been done a little easier (for all).
Comment: (Rob Bodington 07-03-01)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=644

Closed issue Issue: RBN-19 by Tim Turner (04-06-09) minor_technical issue
Resolution: Accept. Status: closed

In addition to the checklist it seems apparant that the models are constantly moving and it is difficult to understand if the comments are still relevant by the time they are received. I think that we should at least record the version of the capability against which the comments were raised in addition to the date.

I believe that we will have the same problem when it comes to reviewing at the Dex level. That is, which versions of the capabilities were part of the Dex on a specific date when the review was done? If this could be automated it would be useful - almost like an internal release system against which we could record comments.

Comment: (Rob Bodington 04-06-09)
The revision is displayed in the capability header block. It should be included in the DEX header block as well. The DEX should provide a summary page on the DEX displaying the revisions of the capabilities that have been used. Should all display the revisions of the modules used by the capabilities.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=667

Closed issue Issue: NFN-01 by Nigel Newling (28Sep04) minor_technical issue
Resolution: Accept. Status: closed

A recent revision to the Capability.xml DTD has added review status data elements to the header. However, there is now duplication of the elements that identify the reviewer by name and role with elements in the contacts section. Additionally, the complementary revision to home.XML style sheet does not insert a carriage return after the completion date element and before the Issues header.
Comment: ( )
Comment: (Rob Bodington 04-09-29)
There is no duplication of reviewer. The reviewer in the contacts element is the allocated reviewer. The reviewer in the status element is the person who actually reviewed the capability. A standard PLCS split between the planned and actual!
Comment: (Rob Bodington 04-09-29)
Carriage return added after the completion date on the cover page.

Closed issue Issue: RBN-20 by Rob Bodington (04-09-30) minor_technical issue
Resolution: Accept. Status: closed

How should we specify that certain instantiation templates are optional, and other mandatory? For example, identification must be assigned to a part to provided a part number. A part may be approved.
Comment: (Rob Bodington 07-03-05)
This is done via the characterization section of the templates and shown in diagrams by the template having dashed lines

Closed issue Issue: RBN-24 by Rob Bodington (05-06-13) minor_technical issue
Resolution: Accept. Status: closed

Each capability and DEX should have an images folder
Comment: (Rob Bodington 05-06-13)
Extended mk_capability_main.js and mk_dex_main.js

Closed issue Issue: RBN-25 by Rob Bodington (05-06-13) minor_technical issue
Resolution: Accept. Status: closed

Change the section title from "Business concept overview" to "Business overview"
Comment: (Rob Bodington 05-06-13)
Extended mk_capability_main.js

Closed issue Issue: RBN-27 by Rob Bodington (05-06-13) minor_technical issue
Resolution: Accept. Status: closed

Add a short name to template
Comment: (Rob Bodington 05-06-13)
Modified mk_capability_main.js mk_template.wsf templates.xsl

Closed issue Issue: RBN-28 by Rob Bodington (05-06-14) minor_technical issue
Resolution: Accept. Status: closed

All capabilities should start with "This capability provides the ability to" Update the XSL and the script accordingly.
Comment: (Rob Bodington 05-06-15)
Updated sect_introduction.xsl and km_capability_main.js

Closed issue Issue: RBN-29 by Rob Bodington (05-06-14) minor_technical issue
Resolution: Accept. Status: closed

Modify the capability DTD so that there is an explicit element for business_overview and information_model_overview rather than using the section element. Add characterization to information_model_overview
Comment: (Rob Bodington 05-06-15)
Updated DTD, XSL and make scripts. Also added some boilerplate text

Closed issue Issue: RBN-30 by Rob Bodington (05-06-16) minor_technical issue
Resolution: Accept. Status: closed

Opening up a DEX or capability causes a new windows browser window to be opened. With Windows XP this triggers a security request. Modify so that it is optional as to whether a new browser window is opened.
Comment: (Rob Bodington 05-06-16)
Added options to the menus
Comment: (Rob Bodington 05-06-21)
Changed so that there is no title frame showing whether you are looking a DEX or capabilities

Closed issue Issue: RBN-31 by Rob Bodington (05-06-22) minor_technical issue
Resolution: Accept. Status: closed

The links to entities in the usage section do not work
Comment: (Rob Bodington 05-06-22)
Corrected in: xsl/dex/common_usage.xsl

Closed issue Issue: RBN-33 by Rob Bodington (05-09-05) minor_technical issue
Resolution: Accept. Status: closed

The "reference path" of the template should be referred to as an "instantiation path". Change the sub heading accordingly.
Comment: (Rob Bodington 05-09-05)
Changed reference path to instantiation path in: dexlib/xsl/dex/templates.xsl dexlib/xsl/dex/templates_xml dexlib/dexlib/help/dex/implementor_intro.xml

Closed issue Issue: RBN-34 by Rob Bodington (05-09-05) minor_technical issue
Resolution: Accept. Status: closed

help_ref does not link to correct A NAME
Comment: (Rob Bodington 05-09-05)
Modified help.xsl

Closed issue Issue: RBN-35 by Rob Bodington (05-09-19) minor_technical issue
Resolution: Accept. Status: closed

It should be possible to define Templates in business concepts.
Comment: (Rob Bodington 05-09-19)
Modified template_ref to allow this. template_ref now takes capability, or business_concept and context as parameters.
Comment: (Rob Bodington 05-09-19)
The instantiation path needs to take this into account.

Closed issue Issue: RBN-36 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: closed

Make sure that the names of the issue files in the menu and the titles on page correspond.

Closed issue Issue: RBN-39 by Rob Bodington (05-10-25) minor_technical issue
Resolution: Accept. Status: closed

The DEX should contain a pointer to a set of test data files
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=662

Closed issue Issue: RBN-41 by Rob Bodington (05-11-21) minor_technical issue
Resolution: Accept. Status: closed

The attributes on the capability element @rd_library @rd_class_of_class have been deprecated.
Comment: (Rob Bodington 05-11-21)
Added an error message to trap them.

Closed issue Issue: RBN-44 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: closed

There needs to be a way to flag a capability as being deprecated and to indicate what capability replaces it.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=663

Closed issue Issue: RBN-46 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: closed

The templates listing in dexlib groups together all templates i.e. there is no distinction between templates defined in a capability (i.e. generic) and business mappings.
Comment: (Rob Bodington 07-03-05)
It is now possible to have business templates stored as part of the business context.

Closed issue Issue: RBN-47 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: closed

There should be some functionality in dexlib that summarizes the dependencies between templates and the dependencies between capabilities.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=664

Closed issue Issue: RBN-48 by Rob Bodington (05-11-29) minor_technical issue
Resolution: Accept. Status: closed

There should be some level of configuration change management on dexlib, i.e. which version of the dex, uses which version of the capabilities.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=651

Closed issue Issue: RBN-49 by Rob Bodington (05-11-30) minor_technical issue
Resolution: Accept. Status: closed

The business mapping should contain a long form as defined by a set of capabilities. The business mapping
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=654

Closed issue Issue: RBN-50 by Rob Bodington (05-11-30) minor_technical issue
Resolution: Accept. Status: closed

The business mapping should use the same section headings as the a dex DEX Based upon Introduction Scope (in scope / out scope) Business overview Information model overview List of templates
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=654

Closed issue Issue: RBN-52 by Rob Bodington (05-11-06) minor_technical issue
Resolution: Accept. Status: closed

The business concepts have been rename business DEXs. The XSL needs to be modified to reflect this.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=654

Closed issue Issue: RBN-53 by Rob Bodington (06-01-16) minor_technical issue
Resolution: Accept. Status: closed

Reference to a reference parameter in a path can throw a false error. E.g. -- Bind the Dated_effectivity instantiated by the template representing_dated_effectivity -- to the parameter ^dated_effectivity. The parameter is a reference parameter so the -- Dated_effectivity can be referred to when this template is used. %^dated_effectivity = $representing_dated_effectivity.^dated_effectivity% -- Set the Effectivity_assignment.assigned_effectivity to the Dated_effectivity -- entity instantiated by representing_dated_effectivity Error P4 Cannot find bound parameter dated_effectivity Effectivity_assignment.assigned_effectivity -> ^dated_effectivity Similar error occurs: -- Get the location from assigning_location template call %^ref_location = $assigning_location.location% [warning:]Error P6 Cannot find bound parameter ref_location ^ref_location.alternative_location_representations -> Organization_based_location_representation
Comment: (Rob Bodington 06-02-13)
XSL assumed that every bound parameter was bound to express entity and ignored the templates

Closed issue Issue: RBN-54 by Rob Bodington (06-02-22) minor_technical issue
Resolution: Accept. Status: closed

The "DEX capability dependencies" section is incorrect when the HTML is generated via SAXON
Comment: (Rob Bodington 06-02-22)
Corrected

Closed issue Issue: RBN-56 by Rob Bodington (06-02-22) minor_technical issue
Resolution: Accept. Status: closed

The anchor for an issue should just by the @id
Comment: (Rob Bodington 06-02-22)
Modified

Closed issue Issue: RBN-57 by Rob Bodington (06-05-17) minor_technical issue
Resolution: Accept. Status: closed

The display of the issuesshould include the dex/capability a menu bar to enable navigation from the page.

Closed issue Issue: RBN-58 by Rob Bodington (06-06-19) minor_technical issue
Resolution: Accept. Status: closed

As we are developing the capabilities, we are finding some selects that should have been extended. In a couple of cases, this is preventing us from completing the capabilities, or forcing us to represent something in a less optimal way. I was thinking that we need a formal process for dealing with modifications to the AP that takes into account the short term requirements to make fixes to the AP for implementations and the requirement to ensure that these fixes are rolled back into the ISO document. My proposal is that we: 1) Record the issues against AP239 in a single issue log in dexlib i.e. dexlib/docs/issues/ap239_issues.xml 2) Raise the issue as SEDS so that they are registered against ISO 10303-239, recoding the seds number in the issue log 3) Copy the EXPRESS models for the AP to DEXLIb. Have two files. One a concatenation of all module ARMs, and the other being the long form derived from the ARMs. Fix the EXPRESS according to the issue. 4) Modify the capabilities to use the modified EXPRESS and include a note in the capability referring to the issue and SEDs and to say that it deviates from the standard, but that the issue has been raised against the standard. 5) At some point in time, raise a TC against PLCS. This raise several questions about the TC process. 1) How long does it take to produce a TC? 2) What do we need to produce? A complete new AP package? 3) Does it require a ballot process? 4) How many can we produce? I.e should we wait until we have a number of issues addressed then release the TC, or release a TC everytime we address an issue? 5) Can we make major modifications in the TC? E.g. bring the Risk module, address the config management of tasks, or should we just address clear errors like missing select extensions I realise that this opens a potential Pandora's box of changes that we might be tempted to make, but given where we are with PLCS, I think that we should limit the TC to fixing errors. What does everyone think? In the mean time, I will create: 1) The issue log at: dexlib/docs/issues/ap239_issues.xml 2) The EXPRESS files: dexlib/docs/ap239/ap239_arm_lf.exp dexlib/docs/ap239/ap239_arm_lf.xml (derived from ap239_arm_lf.exp) dexlib/docs/ap239/ap239_arm_sf.exp dexlib/docs/ap239/ap239_arm_sf.xml (derived from ap239_arm_lf.exp)
Comment: (Rob Bodington 06-06-19)
Have added 1) The issue log at: dexlib/docs/issues/ap239_issues.xml 2) The EXPRESS files: dexlib/docs/ap239/ap239_arm_lf.exp dexlib/docs/ap239/ap239_arm_lf.xml (derived from ap239_arm_lf.exp) dexlib/docs/ap239/ap239_arm_sf.exp dexlib/docs/ap239/ap239_arm_sf.xml (derived from ap239_arm_lf.exp) Have also modified common.xsl to allow <ap239_issue> to document the fact that capability deviates from the official ISO 10303-239.
Comment: (Rob Bodington 06-06-26)
Have added:
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=665

Closed issue Issue: RBN-59 by Rob Bodington (06-06-20) minor_technical issue
Resolution: Accept. Status: closed

The links to the template descriptions have moved to: href=../../../../help/dex/techdes_template{$FILE_EXT}#ReadingCapabilityTemplates
Comment: (Rob Bodington 06-06-20)
Modified

Closed issue Issue: RBN-60 by Rob Bodington (06-06-22) minor_technical issue
Resolution: Accept. Status: closed

The tools display does not list the module references for copying into text
Comment: (Rob Bodington 06-06-22)
Updated

Closed issue Issue: RBN-61 by Rob Bodington (06-06-26) minor_technical issue
Resolution: Accept. Status: closed

When using template_table, it should be possible to have all the parameter values displayed by default so that the developer does not have to explicitly list them all.
Comment: (Rob Bodington 06-06-26)
Added attribute all_params to template_table element Modified: dexlib/xsl/dex/templates.xsl dexlib/dtd/dex/templates.ent

Closed issue Issue: RBN-62 by Rob Bodington (06-07-04) minor_technical issue
Resolution: Accept. Status: closed

The characterization of the template should indicate whether they are optional or not.
Comment: (Rob Bodington 06-07-05)
Addressed - fixed template.xsl

Closed issue Issue: MAN-01 by Mats Nilsson (06-11-01) editorial issue
Resolution: Accept. Status: closed

The term Business Concept is in many places used when instead Business DEX should be used.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=654

Closed issue Issue: RBN-63 by Rob Bodington (07-01-02) minor_technical issue
Resolution: Accept. Status: closed

An input parameter can currently only be defined as a STRING | NUMBER | ENUMERATION| INTEGER | REAL | BOOLEAN | LOGICAL | CLASS | URN | URL | ENTITY | SELECT It should be possible to define the parameter as an EXPRESS defined type. E.g. an input parameter of type TYPE year_number = INTEGER; END_TYPE; should be defined as: <param_in name="year" type="TYPE" defined_type="year_number">
Comment: (Rob Bodington 07-01-02)
Updated the DTD (dexlib/dtd/dex/templates.ent) to allow this: <!ELEMENT param_in (classifications?, description?)> <!ATTLIST param_in name CDATA #REQUIRED type (STRING | NUMBER | ENUMERATION| INTEGER | REAL | BOOLEAN | LOGICAL | CLASS | URN | URL | ENTITY | SELECT | TYPE) #IMPLIED select_type CDATA #IMPLIED entity_type CDATA #IMPLIED defined_type CDATA #IMPLIED value CDATA #IMPLIED optional (yes | no) "no" default CDATA #IMPLIED Updated the XSL: dexlib/xsl/dex/templates.xsl

Closed issue Issue: RBN-64 by Rob Bodington (07-01-02) minor_technical issue
Resolution: Accept. Status: closed

An input parameter can currently only be defined as an EXPRESS ENUMERATION. It should be possible to define the ENUMERATION type. E.g. An input parameter of type TYPE offset_orientation = ENUMERATION OF (ahead, exact, behind); END_TYPE; Should be defined as <param_in name="sense" type="ENUMERATION" enumeration_type="offset_orientation">
Comment: (Rob Bodington 07-01-02)
Updated the DTD (dexlib/dtd/dex/templates.ent) to allow this: <!ELEMENT param_in (classifications?, description?)> <!ATTLIST param_in name CDATA #REQUIRED type (STRING | NUMBER | ENUMERATION| INTEGER | REAL | BOOLEAN | LOGICAL | CLASS | URN | URL | ENTITY | SELECT | TYPE) #IMPLIED select_type CDATA #IMPLIED entity_type CDATA #IMPLIED defined_type CDATA #IMPLIED enumeration_type CDATA #IMPLIED value CDATA #IMPLIED optional (yes | no) "no" default CDATA #IMPLIED Updated the XSL: dexlib/xsl/dex/templates.xsl

Closed issue Issue: RBN-65 by Rob Bodington (07-01-04) minor_technical issue
Resolution: Accept. Status: closed

The instantiation path of a template is displayed as plain text when the template is displayed in the context of a capability.
Comment: (Rob Bodington 07-01-04)
Addreseed in: dexlib/dexlib/xsl/dex/templates.xsl, revision: 1.56; dexlib/dexlib/xsl/dex/templates_xml.xsl, revision: 1.28

Closed issue Issue: RBN-66 by Rob Bodington (07-01-15) minor_technical issue
Resolution: Accept. Status: closed

The templates need to be able to specify if an entity instantiated by the template path is unique and what are the parameters that identify it. The intent is that any system reading the PLCS file will use the uniqueness constraint for consolidation on import. I.e.
Comment: (Rob Bodington 07-03-05)
Moved to bugzilla http://www.eurostep.fi/bugs/show_bug.cgi?id=RBN-66

Closed issue Issue: RBN-67 by Rob Bodington (07-02-01) minor_technical issue
Resolution: Accept. Status: closed

In tools -> Capability / Templates - the build does not display the correct HTML
Comment: (Rob Bodington 07-02-01)
Addressed in: dexlib/utils/dex/build.xml revision: 1.61;