OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-dex message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Changes to referencing owl classes in dexlib


Hi

I have addressed the following issue to do with creating links to reference data in dexlib.

As you can see from the comment on the issue, this will result in some changes to the XML elements used to refer to OWL classes.

 

Unless any has any strong objections, I propose to check in these changes tomorrow, and change ALL the capabilities and DEXs that are affected.

Please let me know if you are working on any capabilities at the moment and please make sure that you check in all capabilities etc.

 

I will also be moving the OWL files and the rdl_index.xml as discussed below.

 


Open issueIssue: 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:

o        The capability section specifying the classes used:
<ref_data>
<class_ref id="Designer_of" urn="plcs:rdl:std"/>
</ref_data>

o        A reference to a class in the main text:
<rdl_ref id="Designer_of" urn="plcs:rdl:std"/>

o        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

 Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Web Page:
http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1452 810 960
Mobile: +44 (0)7796 176 401

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]