Artificial Intelligence Authors: Elizabeth White, Yeshim Deniz, Pat Romanski, Zakia Bouachraoui, William Schmarzo

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:


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 
   - 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...
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...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
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.
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...