• From: "Len Bullard" <Len.Bullard@s...>
• To: "Costello, Roger L." <costello@m...>,<xml-dev@l...>
• Date: Tue, 3 Jul 2012 11:00:47 -0500

There may not be a "best" way.  How is the application space being
communicated to you?  Are you being given documents or are you
converting, for example, relational database(s)?   Are you interviewing
end users and then creating description documents? Are you
using/receiving all of the above?

The means of description invariably determines the initial approach
because it prescribes the domain.   One of the worst experiences I've
had involved bringing a lot of end users into a room and having them
describe the domains.  They tend to tell you what they want and not
necessarily what they need or have.  And they will not always agree even
when they do (they don't know they are saying the same thing because
they have competing vocabularies from competing organizations and it's
up to you to identify synonyms).  Look at your own description:

"The count of the number of aircraft at each airport"

First, that is a redundant description (count and number).

Are you calculating the count of identified aircraft and embedding it
somewhere?  Do you have to sort them by type (C130 or F22) and obtain a
number by type?  Do you sort them by class (rotary vs fixed wing)?  By
kind (jet vs prop, prop vs turbo prop)?  IOW, what do you have to know
about aircraft as objects/properties and how will that determine your
approach to counting?

A good idea is to identify the highest or most empowered authority
because you will need a sanity checker or tie breaker.

Len

-----Original Message-----
From: Costello, Roger L. [mailto:costello@m...] 
Sent: Tuesday, July 03, 2012 7:44 AM
To: xml-dev@l...
Subject:  What is the best way to approach the structuring of
inventory data?

Hi Folks,

I am starting work on defining an XML vocabulary for some inventory
data. 

My inventory includes data such as the count of the number of aircraft
at each airport, the count of the number aircraft ground refuelers at
each airport, and so forth.

What is the best way to proceed?

My thinking is that the first step should be to create a taxonomy. Then
define a structure which reflects that taxonomy.

Is that the best way to proceed?

Do you have experience with structuring inventory data? If so, how did
you proceed?

/Roger

• Follow-Ups:
  • RE: What is the best way to approach the structuring of inventorydata?
    • From: "Graham Hannington" <graham_hannington@f...>
  • Re: What is the best way to approach the structuring ofinventory data?
    • From: Michael Kay <mike@s...>

• References:
  • What is the best way to approach the structuring of inventory data?
    • From: "Costello, Roger L." <costello@m...>