Thanks
David
The source is TRILS –
it was missing from the XSL but was in the XML – I have fixed the XSL so it is
there now.
The intent of a
business concept is to document a term used in business or in a legacy system
and show how that is represented in PLCS. So you are correct – there will be
multiple definitions for the terms.
I agree that we need
to include the source for any definition. Your question makes me wonder
whether that is sufficient. In particular I wonder whether in addition
we need a section in which the context is made explicit.
Maybe
<context
id=”TRILS”/>
and then another file
which contains all the contexts for the business contexts including
descriptions. Maybe dex_index.xml
-----Original Message-----
From: David Price
[mailto:david.price@eurostep.com]
Sent: 17 August 2005 10:27
To:
plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] Business
concepts, Terms and DEXs
I didn't see
a reference to the source or context for the defintion of terms. I
Googled manufacturer item and found this as part of the CIMSteel
project:
What type of products are
Manufacturer's Items?
Manufacturer's
Items are proprietary product items (such as cold rolled
sections) which comply with manufacturer's catalogues. This would also include
"semi-standard" product items that comply to specifications agreed between a
consortium of manufacturers. Such items use an agreed human readable "manufacturer's identifiers" published by
the manufacturer as "manufacturer's
lists". Each of these unique and predefined identifiers has seven
components and takes the form:
M\entity_type\country\manufacturer\manufacturer's-item\manufacture's-range\version
For example, a Metsec cold-rolled zed purlin of
section reference 142.Z.14 is given the manufacturer’s identifier:
Seems like for a
Business Term, the kind of business/industry in which it's used is important.
Business terms will overlap and the same term will have different meanings in
different contexts.
Cheers,
David
P
-----Original
Message-----
From: Rob
Bodington [mailto:rob.bodington@eurostep.com]
Sent: 17 August 2005 08:42
To: Trine.Hansen@dnv.com;
plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] Business
concepts, Terms and DEXs
Thanks
for the comments Trine
I have
responded to the comments in the document and modified the XSL where
appropriate. I will check in these changes shortly.
Does
any one else have any comments on the example?
-----Original Message-----
From: Trine.Hansen@dnv.com
[mailto:Trine.Hansen@dnv.com]
Sent: 16 August 2005 23:06
To: rob.bodington@eurostep.com;
plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] Business
concepts, Terms and DEXs
Hi
Rob.
Good
work (as always)!
I have
been through the example business concept and given a few comments (attached
document).
Leif
T, Leif G and I will discuss the assign_code capability tomorrow afternoon.
We will propose some dates for the next webexs.
Regarding the term
definitions - are there any overlap with reference
data?
Regards
Trine
From: Rob Bodington
[mailto:rob.bodington@eurostep.com]
Sent: 8. august 2005 08:33
To:
plcs-dex@lists.oasis-open.org
Subject: [plcs-dex] Business concepts,
Terms and DEXs
HI
I have done a fair bit of work on
the business concepts.
There is an example in
manufacturers_item.
This shows the XML used and a
proposed layout.
All comments
welcome.
I have also introduced a
terminology dictionary and a way of defining terms in business
concepts.
I was wondering whether we should
add the idea of terms to DEXs and capabilities - perhaps replacing
keywords?
Or maybe keywords should be
defined as terms?
When is our next modellers
telecom?
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)1454 270030
Mobile: +44
(0)7796 176 401
**************************************************************
Neither
the confidentiality nor the integrity of this message can be vouched for
following transmission on the Internet. All messages sent to a DNV email
addressee are swept by Sybari Antigen for the presence of malicious code.
DNV acknowledges that unsolicited email represents a potential security
risk, and DNVs filters to block unwanted emails are therefore continuously
adjusted.
**************************************************************