Transcript MRI issues raised by TBG6

MRI issues raised by TBG6
Mexico
April 6, 2008
List of points proposed
•
•
•
•
CFEM progress status
How to refer to a file
How to deal with context restrictions
Multiple Text Information for language
purpose
• Helping modelers to discover existing
standards and projects
• In general: Cross TBG consistency
CFEM Progress status
•
•
•
•
Progress review spreadsheet
Business Domain View
Business Requirements View
Business Transaction View
How to refer to a file
• Mentioning the URL or URI of a referred to
document or file
• TBG6 intention is to use the binary object ACC
which allows mentioning all required
information.
• Nevertheless, this is not a normal use of the
ACC, with no content most of the time
• A cross TBG recommendation and practice
would be helpful
Same meaning, many languages
• Using multiple text information just to allow different
languages but for the same entity
• Cardinality of 1..n for a text information, even though
the language is an additional element, doesn’t clarify
that it is the same information in different languages.
• ICG recommends the use of a qualified data type
“specified language text”.
• The practice recommended by ICG to TBG6 must lead
to a cross TBG recommendation and practice.
• We should have an indicator saying that the element
gives the same meaning in different languages (or not)
and something giving the reference version
Context restrictions
• Introducing business specific restrictions or other rules:
• It is difficult to produce a different standard for each
specific use and a generic standard relies on an XML
schema that does not ensure the compliance with all
necessary rules.
• Having specific implementation rules for a standard
document and schema is an important need.
• Solutions and guidelines are necessary, schematron
being an interesting option
• Will the Context methodology deal with this problem
and how?
• Can someone clarify ?