Welcome!

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

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
BMC has unmatched experience in IT management, supporting 92 of the Forbes Global 100, and earning recognition as an ITSM Gartner Magic Quadrant Leader for five years running. Our solutions offer speed, agility, and efficiency to tackle business challenges in the areas of service management, automation, operations, and the mainframe.
At CloudEXPO Silicon Valley, June 24-26, 2019, Digital Transformation (DX) is a major focus with expanded DevOpsSUMMIT and FinTechEXPO programs within the DXWorldEXPO agenda. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throug...
After years of investments and acquisitions, CloudBlue was created with the goal of building the world's only hyperscale digital platform with an increasingly infinite ecosystem and proven go-to-market services. The result? An unmatched platform that helps customers streamline cloud operations, save time and money, and revolutionize their businesses overnight. Today, the platform operates in more than 45 countries and powers more than 200 of the world's largest cloud marketplaces, managing mo...
The platform combines the strengths of Singtel's extensive, intelligent network capabilities with Microsoft's cloud expertise to create a unique solution that sets new standards for IoT applications," said Mr Diomedes Kastanis, Head of IoT at Singtel. "Our solution provides speed, transparency and flexibility, paving the way for a more pervasive use of IoT to accelerate enterprises' digitalisation efforts. AI-powered intelligent connectivity over Microsoft Azure will be the fastest connected pat...
Apptio fuels digital business transformation. Technology leaders use Apptio's machine learning to analyze and plan their technology spend so they can invest in products that increase the speed of business and deliver innovation. With Apptio, they translate raw costs, utilization, and billing data into business-centric views that help their organization optimize spending, plan strategically, and drive digital strategy that funds growth of the business. Technology leaders can gather instant recomm...
At CloudEXPO Silicon Valley, June 24-26, 2019, Digital Transformation (DX) is a major focus with expanded DevOpsSUMMIT and FinTechEXPO programs within the DXWorldEXPO agenda. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throug...
As you know, enterprise IT conversation over the past year have often centered upon the open-source Kubernetes container orchestration system. In fact, Kubernetes has emerged as the key technology -- and even primary platform -- of cloud migrations for a wide variety of organizations. Kubernetes is critical to forward-looking enterprises that continue to push their IT infrastructures toward maximum functionality, scalability, and flexibility. As they do so, IT professionals are also embr...
CloudEXPO has been the M&A capital for Cloud companies for more than a decade with memorable acquisition news stories which came out of CloudEXPO expo floor. DevOpsSUMMIT New York faculty member Greg Bledsoe shared his views on IBM's Red Hat acquisition live from NASDAQ floor. Acquisition news was announced during CloudEXPO New York which took place November 12-13, 2019 in New York City.
In an age of borderless networks, security for the cloud and security for the corporate network can no longer be separated. Security teams are now presented with the challenge of monitoring and controlling access to these cloud environments, at the same time that developers quickly spin up new cloud instances and executives push forwards new initiatives. The vulnerabilities created by migration to the cloud, such as misconfigurations and compromised credentials, require that security teams t...
The graph represents a network of 1,329 Twitter users whose recent tweets contained "#DevOps", or who were replied to or mentioned in those tweets, taken from a data set limited to a maximum of 18,000 tweets. The network was obtained from Twitter on Thursday, 10 January 2019 at 23:50 UTC. The tweets in the network were tweeted over the 7-hour, 6-minute period from Thursday, 10 January 2019 at 16:29 UTC to Thursday, 10 January 2019 at 23:36 UTC. Additional tweets that were mentioned in this...