Welcome!

Artificial Intelligence Authors: Liz McMillan, Zakia Bouachraoui, Pat Romanski, Yeshim Deniz, Elizabeth White

RSS Feed Item

Re: Namespaces enable recognition of the type of document, but

Just to clarify:

A namespace is used to disambiguate document components (elements,
attributes, and types) that have the same local name.

A qualified name (QName) uses a namespace to qualify a local name. The
combination of the namespace and the local name should produce a
unique name, and you can use the QName of the root element of a
document as a kind of "signature" for the document type. For example,
a document with a root element of
     <soap-env:Envelope  xmlns="http://schemas.xmlsoap.org/soap/envelope/"
is a SOAP envelope document, and a document with a root element of
      <collection xmlns="http://purl.org/atom/app#">
is an Atom collection document.

The xsi:type attribute allows you to specify the datatype of a
particular element (e.g., primitive datatypes like xsd:string or
custom datatypes like my:customer).

None of these mechanisms enable you to specify a unique identifier for
an instance document. That you would have to specify as an element or
attribute within the document, and the best method is dependent on how
you want to model the data. You should use similar modeling techniques
that you would use when modeling a database. e.g., in some cases you
may want to add a unique ID field to the document, but more often you
want to use an element or attribute that has semantic meaning to the
data. In your claim example, you would probably have a claimID element
to identify the claim. But I also expect that you would have a field
that indicates who filed the claim.

Anne


On Mon, Mar 23, 2009 at 7:18 AM, Michael Kay <[email protected]> wrote:
> No, namespaces don't identify the type of document. All FpML messages, for
> example, use the same namespace. They also share the same root element name;
> in this vocabulary the type of document is identified by an xsi:type
> attribute. Other vocabularies have other conventions.
>
> Michael Kay
> http://www.saxonica.com/
>
>> -----Original Message-----
>> From: Costello, Roger L. [mailto:[email protected]]
>> Sent: 22 March 2009 13:50
>> To: 'xml-dev@l...'
>> Subject:  Namespaces enable recognition of the type
>> of document, but what about recognition of the instance?
>>
>>
>> Hi Folks,
>>
>> Consider a task that receives various types of documents. The
>> task needs to "recognize" the type of each document to enable
>> subsequent processing.
>>
>> The type of an XML document can be recognized by its
>> namespace. Thus, a task at a health-care insurance company
>> can recognize the following XML document is an insurance
>> claim by examining its namespace:
>>
>>     <Claim xmlns="http://www.health-care.org/insurance/claim/">
>>       <patient>John Smith</patient>
>>       <doctor>Dr. Sara Johnson</doctor>
>>       <procedure>Yearly physical</procedure>
>>       <charges>$69.00</charges>
>>     </Claim>
>>
>> Suppose a doctor and a patient mistakenly file the same
>> claim. The two documents contain the same information. As
>> we've seen, namespaces enable the task at the insurance
>> company to recognize that the two documents are both claims,
>> but it does not enable the task to distinguish between the
>> claim filed by the doctor and the claim filed by the patient.
>> The task is confused when it processes the second claim:
>>
>>      Is this the same claim that I processed
>>      earlier (i.e. a system error), or is it
>>      a different claim for the same procedure
>>      (user error)?"
>>
>> Thus, namespaces enable recognition of the type of document,
>> but not the instance. Recognition of both are important.
>>
>> One solution is to include an enterprise-wide identifier in
>> each claim. Here is the claim the doctor files:
>>
>>     <Claim xmlns="http://www.health-care.org/insurance/claim/">
>>       <id>A309PX</id>
>>       <patient>John Smith</patient>
>>       <doctor>Dr. Sara Johnson</doctor>
>>       <procedure>Yearly physical</procedure>
>>       <charges>$69.00</charges>
>>     </Claim>
>>
>> And here is the claim the patient files:
>>
>>     <Claim xmlns="http://www.health-care.org/insurance/claim/">
>>       <id>ZZ34RJ</id>
>>       <patient>John Smith</patient>
>>       <doctor>Dr. Sara Johnson</doctor>
>>       <procedure>Yearly physical</procedure>
>>       <charges>$69.00</charges>
>>     </Claim>
>>
>> Now the task at the insurance company can recognize that:
>>
>> - both documents are claims, and
>> - two separate claims have been submitted for the same
>> procedure (i.e. user error).
>>
>>
>> QUESTIONS
>>
>> 1. Is it best practice to include an enterprise-wide
>> identifier in each business document?
>>
>> 2. Is it best practice to use namespaces to identify the type
>> of an XML document, and an enterprise-wide identifier to
>> identify the instance?
>>
>> 3. Is there a standard for creating enterprise-wide identifiers?
>>
>> 4. Is there a standard way of expressing enterprise-wide
>> identifiers in an XML document?
>>
>>    - above I used a very simple <id>...</id> element
>>
>> 5. Is the requirement for an enterprise-wide identifier
>> something that you would put in a business requirement's
>> document, or is it something that a system implementer adds
>> on his own initiative?
>>
>>
>> /Roger
>> ______________________________________________________________
>> _________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: [email protected]
>> subscribe: [email protected]
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: [email protected]
> subscribe: [email protected]
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

Read the original blog entry...

IoT & Smart Cities Stories
Dion Hinchcliffe is an internationally recognized digital expert, bestselling book author, frequent keynote speaker, analyst, futurist, and transformation expert based in Washington, DC. He is currently Chief Strategy Officer at the industry-leading digital strategy and online community solutions firm, 7Summits.
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...
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...
The standardization of container runtimes and images has sparked the creation of an almost overwhelming number of new open source projects that build on and otherwise work with these specifications. Of course, there's Kubernetes, which orchestrates and manages collections of containers. It was one of the first and best-known examples of projects that make containers truly useful for production use. However, more recently, the container ecosystem has truly exploded. A service mesh like Istio addr...
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...
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...
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...
To Really Work for Enterprises, MultiCloud Adoption Requires Far Better and Inclusive Cloud Monitoring and Cost Management … But How? Overwhelmingly, even as enterprises have adopted cloud computing and are expanding to multi-cloud computing, IT leaders remain concerned about how to monitor, manage and control costs across hybrid and multi-cloud deployments. It’s clear that traditional IT monitoring and management approaches, designed after all for on-premises data centers, are falling short in ...
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...