[
Lists Home |
Date Index |
Thread Index
]
Roger,
I would point out that OASIS has several TC's that have been working very
hard on this problem for more than a couple of years now.
OASIS is also running a Symposium in April 2005 in New Orleans on this
very topic area.
Can I suggest that instead of re-inventing the wheel - that you look to
use what
is already available. Let me give you a quick check list here to the
OASIS work:
1) Address vocabulary alignment - OASIS CIQ TC and the UPU work.
2) Systematic approach - CEFACT CCTS work and the implementation
in OASIS UBL TC. The OASIS BCM TC work on vocabularies.
3) Registry tools for storing artifacts such as nouns - ebXML Registry - and
see the work NIST is doing with HL7 RIM for formalized approach to
information representation in a CoI domain - namely HL7.
4) Noun representations - OASIS CAM TC and Registry SCM committee
work - open means to capture runtime executable semantic rules in
syntax such as XSD, RELAX, CAM, XSLT,et al for re-usable nouns
(in CCTS parlance these are CC, BIE, ABIE, ACC, etc).
5) Formalized content assembly and validation services using XML
scripts and
founded on simply existing W3C specifications - XML 1.1, XPath 1.0 -
OASIS Content Assembly Mechanism (CAM) TC and the jCAM
implementation.
6) OASIS BPSS TC work on V2 - which includes ability to manage
business context as part of the business process models (critical for
providing context to information as part of the systematic approach to
knoweledge exchange.
There are also several projects being done today that are bringing
together all
this OASIS work - notably the UK Gov Registry work, the UN/CEFACT
decision to standardize on ebXML Registry V3.0 as the foundation for
their global federated registries, and the HL7 work I noted above. Also
noteworthy is the work the EU funded ARTEMIS project is doing too in
collaboration with several OASIS TCs.
Cheers, DW
======================================================
Roger L. Costello wrote:
>Note: This is a continuation of the thread:
>
> XML Vocabularies for Large Systems - 3 Philosophically Different
>Approaches
>
>I have changed the title to reflect the narrowed focus.
>
>GOAL
>
>My goal is for us (the xml-dev group) to collectively define a systematic
>approach to using simple XML vocabularies to implement large (complex)
>systems.
>
>Yesterday Len and Peter outlined two strategies. I would like to flesh out
>their ideas.
>
>TWO SIMPLE VOCABULARIES
>
>Let's consider a concrete example. Suppose that the following two simple
>vocabularies have been created:
>
>1. Postal Address Vocabulary:
>
> <PostalAddress>, <Addressee>, <Street>, <City>, <State>, <Zipcode>
>
>2. Book Vocabulary:
>
> <Book>, <Title>, <Author>, <Date>, <ISBN>, <Publisher>
>
>CHALLENGE
>
>Imagine that a large system requires an Invoice XML vocabulary for a Book
>purchase. How can the above simple XML vocabularies be used to implement
>this Invoice vocabulary?
>
>Here is an example of an Invoice:
>
><Invoice>
> <PostalAddress id="RLC">
> <Addressee>Roger L. Costello</Addressee>
> <Street>38 Boylston St.</Street>
> <City>Boston</City>
> <State>MA</State>
> <Zipcode>01320</Zipcode>
> </PostalAddress>
> <Book id="Bach">
> <Title>Illusions</Title>
> <Author>Richard Bach</Author>
> <Date>1977</Date>
> <ISBN>0-440-34319-4</ISBN>
> <Publisher>Dell Publishing Co.</Publisher>
> </Book>
></Invoice>
>
>THE LEN BULLARD APPROACH
>
>The approach that Len suggested was to use a "metadata framework" which ties
>together the simple vocabularies. Let me try to make concrete Len's
>suggested approach using the above Invoice example.
>
>First, use the simple vocabularies to provide the basic information:
>
><PostalAddress id="RLC">
> <Addressee>Roger L. Costello</Addressee>
> <Street>38 Boylston St.</Street>
> <City>Boston</City>
> <State>MA</State>
> <Zipcode>01320</Zipcode>
></PostalAddress>
>
><Book id="Bach">
> <Title>Illusions</Title>
> <Author>Richard Bach</Author>
> <Date>1977</Date>
> <ISBN>0-440-34319-4</ISBN>
> <Publisher>Dell Publishing Co.</Publisher>
></Book>
>
>Second, create a "metadata framework" which brings cohesion to the simple
>vocabularies:
>
><Invoice>
> <PurchasedBy href="RLC"/>
> <PurchasedItem type="book" href="Bach"/>
></Invoice>
>
>Len noted that Topic Maps might be used as the metadata framework.
>
>Len, have I characterized your ideas correctly?
>
>THE PETER HUNSBERGER APPROACH
>
>In the above Invoice example tags that are specific to postal addresses and
>books were used. A disadvantage is that many domain-specific simple
>vocabularies must be created.
>
>Peter's approach is to provide a "generic set of tags", coupled with a rich
>set of ways to relate the generic tags.
>
>Below I have attempted to define the Invoice using generic tags coupled with
>"relationship tags". Obviously I don't know what I am doing. Peter, would
>you fix this please?
>
><Collection id="RLC">
> <Object>Roger L. Costello</Object>
> <Object>38 Boylston St.</Object>
> <Object>Boston</Object>
> <Object>MA</Object>
> <Object>01320</Object>
></Collection>
>
><Collection id="Bach">
> <Object>Illusions</Object>
> <Object>Richard Bach</Object>
> <Object>1977</Object>
> <Object>0-440-34319-4</Object>
> <Object>Dell Publishing Co.</Object>
></Collection>
>
><Collection>
> <Object href="RLC"/>
> <Relation>Purchased By</Relation>
> <Object href="Bach">
></Collection>
>
>What do you (xml-dev'ers) think about all this? Can you think of other
>approaches? /Roger
>
>
>
>
>-----------------------------------------------------------------
>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>
>
>
>
|
