OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Help with terms for kind of schema I'm building

[ Lists Home | Date Index | Thread Index ]
  • To: "Karr, David" <david.karr@wamu.net>, <xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] Help with terms for kind of schema I'm building
  • From: "Lindsey, Jack" <Jack.Lindsey@cra-arc.gc.ca>
  • Date: Tue, 18 Jul 2006 18:07:20 -0400
  • Thread-index: AcaqrP+ZTpdsZyLeRcGG9OAelwYLEQACVqkA
  • Thread-topic: Help with terms for kind of schema I'm building

Attribute-Value Pairs?


Entity-Attribute-Value (EAV) ?


This one mentions XML.  In database circles this is sarcastically known as "row modelling".

Perhaps generic EAV schema versus explicit semantic schema?

Good luck on your journey through a world of pain!

Cheers	Jack Lindsey

-----Original Message-----
From: Karr, David [mailto:david.karr@wamu.net]
Sent: 18 Jul, 2006 16:59
To: xml-dev@lists.xml.org
Subject: [xml-dev] Help with terms for kind of schema I'm building

I'm trying to figure out appropriate terms to describe the kind of
schema I'm trying to build (and related terms).  Each time I have to
talk about this, I wave my hands a bit.  I'd like to find better terms
to describe this, that are "in the literature", as they say.

We have a downstream service that uses what I would call an
"application-specific" schema, simply that the types and elements are
named according to the semantics of what the information represents.  In
other words, a perfectly normal application schema.

I have to build a web service that interfaces with this service.  The
schema for my service should provide most of the information in the
other schema, although we're going to get some of the pieces for the
downstream service from other sources.  I've been told that we're going
to need a lot of flexibility in the messages matching this schema.  A
new "schema" has to be usable in minutes, not the days and weeks that
changing files in production in a bank would require.

So, I figure the best way to deal with this is to "dumb down" my service
schema, so instead of having a set of application-specific element
names, it will just be a list of key-value pairs.  I've referred to this
as "non-type-safe", but that isn't quite right.  Obviously, there are
specific disadvantages to this type of schema (the term of which I'm
looking for here), but it will probably be the best compromise for my

Again, I'm not looking for a critique of this approach, just useful
vocabulary to describe what I'm building, and also perhaps an opposite
term to describe my downstream service schema.

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS