Welcome!

Artificial Intelligence Authors: Yeshim Deniz, Elizabeth White, Zakia Bouachraoui, Pat Romanski, Jason Bloomberg

RSS Feed Item

Re: RE: Keep business-process-specific data separate?

At 2009-01-30 08:32 -0500, Costello, Roger L. wrote:
>3. "Business-process-specific data versus 
>business-process-independent data" is a false distinction. There is 
>only kind of data: data for some  purpose or purposes, and there is 
>only one kind of XML vocabulary: vocabulary that supports a purpose 
>or purposes.

I would soften that a bit.  What the information in a document means 
is up to the recipient.  Hopefully he is understanding the 
information in the way the sender intended, but he isn't obliged to 
stick to that understanding.  A recipient could choose their own 
document constraints (i.e. schema) and their own stylesheet or 
application to do anything they want with the information captured 
using an XML vocabulary and interpret it any way they wish.

>6. Distinguish between the XML vocabulary you create versus the XML 
>vocabulary that is actually used in practice: when creating the XML 
>vocabulary, identify the optional markup (data) as described above. 
>Recognize, however, that the XML vocabulary may be used in 
>unforeseen contexts that require markup (data) above and beyond the 
>provided by your XML vocabulary. Design your XML vocabulary to 
>support these unforeseen use cases.

One approach is illustrated in figure 21 on page 33 of the draft UBL 
Customization Guidelines:

   http://docs.oasis-open.org/ubl/guidelines/UBL-Customization1.0prd01.pdf

This shows a processing model with two possible steps for schema 
validation, followed by a separate step for value validation (for 
code lists, identifiers and other business rule values).

Focusing on the two steps for schema validation, a receiver may have 
created a "UBL Customization" comprising a subset of the very large 
UBL vocabulary.  This subset has only those parts of UBL they are 
interested in, and for which they have programmed in their 
application.  Their application may even be constrained to accept 
only the subset of UBL (perhaps they have turned on validation in 
JAXB and an instance is only bound to Java objects if the instance is 
valid; thus in order to inspect anything found in the instance it can 
only have what is expected).

A document arrives at the system and the first schema validation may 
or may not succeed.  If it does succeed, the process continues with 
value validation.

If the first pass does not succeed, a transformation removes from the 
instance all unexpected constructs by only allowing expected 
constructs through an identity transformation.  This transformed 
instance is then validated with the same schema as used in the first pass.

If the second pass does not succeed, there is no point in continuing.

If the second pass does succeed, the process continues with value validation.

So there are two paths that will take content in to an application, 
and the pre-validation ensures the instance will be acceptable to an 
application that uses validation in its data bindings.  The UBL TC 
suggests instances utilize available elements declaring the 
customization and subset to which they conform so that applications, 
when they do get around to inspecting the content, can look at these 
values to make a business decision regarding proceeding.  These two 
paths then bring the instance to the application and the application 
can inspect the declared customization information against the 
expected customization information.

There are four cases:

  No errors on the first pass and the customization is as expected:
   - processing continues and business is accomplished

  An error on the first pass and the customization is as expected:
   - the sender included unexpected information not defined by the 
customization
   - what is in hand is all that is needed, and according to the 
rules of the customization, anything removed wasn't important
   - probably acceptable to do business, unless the community 
dictates that unexpected content violates the rules of sending instances

  No errors on the first pass and the customization is not as expected:
   - this is a foreign instance but there is enough information with 
which to do business and nothing was taken away from the original
   - may want to flag for out-of-band exception handling, but 
probably acceptable since nothing was removed
   - business rules might require rejection if the instance is not 
marked for the customization

  An error on the first pass and the customization is not as expected:
   - this is a foreign instance and some information has been removed
   - something had to be removed to be processed
   - not knowing the rules of the customization, what was removed 
might have been important
   - may want to flag for out-of-band exception handling as one 
cannot be sure the original information wasn't somehow important
   - business rules might require rejection if the instance is not 
marked for the customization

Again, this is all done as a prelude to the application running in 
order to (1) pre-validate the instance as acceptable, and (2) massage 
the instance in order for a validating data binding to pass the 
information to the application.

We've been editing the document and diagrams based on feedback and 
our face-to-face plenary last week, and a new edition is expected soon.

Note that the UBL vocabulary is designed to be both restricted and 
extended (as described in more detail in that document).

I hope this is considered helpful.

. . . . . . . . . . . . . Ken

--
Upcoming hands-on XSLT, UBL & code list hands-on training classes:
Brussels, BE 2009-03;  Prague, CZ 2009-03, http://www.xmlprague.cz
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:[email protected]
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/x/
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Read the original blog entry...

IoT & Smart Cities Stories
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Early Bird Registration Discount Expires on August 31, 2018 Conference Registration Link ▸ HERE. Pick from all 200 sessions in all 10 tracks, plus 22 Keynotes & General Sessions! Lunch is served two days. EXPIRES AUGUST 31, 2018. Ticket prices: ($1,295-Aug 31) ($1,495-Oct 31) ($1,995-Nov 12) ($2,500-Walk-in)
IoT is rapidly becoming mainstream as more and more investments are made into the platforms and technology. As this movement continues to expand and gain momentum it creates a massive wall of noise that can be difficult to sift through. Unfortunately, this inevitably makes IoT less approachable for people to get started with and can hamper efforts to integrate this key technology into your own portfolio. There are so many connected products already in place today with many hundreds more on the h...
Digital Transformation is much more than a buzzword. The radical shift to digital mechanisms for almost every process is evident across all industries and verticals. This is often especially true in financial services, where the legacy environment is many times unable to keep up with the rapidly shifting demands of the consumer. The constant pressure to provide complete, omnichannel delivery of customer-facing solutions to meet both regulatory and customer demands is putting enormous pressure on...
Business professionals no longer wonder if they'll migrate to the cloud; it's now a matter of when. The cloud environment has proved to be a major force in transitioning to an agile business model that enables quick decisions and fast implementation that solidify customer relationships. And when the cloud is combined with the power of cognitive computing, it drives innovation and transformation that achieves astounding competitive advantage.
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
Charles Araujo is an industry analyst, internationally recognized authority on the Digital Enterprise and author of The Quantum Age of IT: Why Everything You Know About IT is About to Change. As Principal Analyst with Intellyx, he writes, speaks and advises organizations on how to navigate through this time of disruption. He is also the founder of The Institute for Digital Transformation and a sought after keynote speaker. He has been a regular contributor to both InformationWeek and CIO Insight...
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.