Ralph Poole's Weblog
Everyone into the deep clear pool.

MY SITE LINKS






MY BOOKMARKS




ARCHIVES








KNOWLEDGE LINKS






Subscribe to "Ralph Poole's Weblog" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 

 

Tuesday, March 11, 2003
 

First impression of XML in Office 2003.

Today at Q42 Laurens looked into Microsoft Office 2003 beta 2. After reading John Udell's article about InfoPath we thought Microsoft migth have caught up with Xopus. Thankfully this does not seem to be the case:

  • Infopath 2003 uses its own templating language. It can only export to XSLT.
  • In Word 2003 you can edit a raw XML file and save it. You can also apply an XSLT transformation and edit the styled result, but you can no longer save the XML data separately after that.

Office 2003 is actually a good developer tool to use with Xopus. Infopath is a nice editor for data schemas and data views. The schemas and views can then be used with Xopus to edit XML online in the browser.

[Sjoerd Visscher's weblog]

I have sent for my copy of the Office 2003 beta, I also am an xopus fan.    So I will write my reactions when I see the software.  However, I am certainly not as technical as Sjoerd.


5:17:58 PM   comment []>  

Kapor's Honorable Exit from Groove. New York Times: Software Pioneer Quits Board of Groove. Mitchell D. Kapor, a personal computer industry software pioneer and a... [Dan Gillmor's eJournal]  

I have mixed feelings about whether I agree with Kapor's decision, but I really respect him for doing leaving.  Groove is a great tool and I can understand why people in the Government are using it.   I hope that this effort will not limit our privacy or freedom.   It is really hard in this economic environment to decide who your clients will be and to choose not to sell to the government.  In fact, increasingly, the government, is the only customer buying IT solutions.   Big problem.


5:14:56 PM   comment []>  

This excellent overview was contributed by Woody Pidcock of the Boeing company. Many organizations and companies are struggling with these terms and the ideas behind them; this set of definitions will help to clarify.  It was published at Metamodel.com.



I will answer this question one step at a time. To keep this answer focused on the question, I will use other concepts that I will not define here. If this generates additional questions, feel free to comment on this post.

A controlled vocabulary is a list of terms that have been enumerated explicitly. This list is controlled by and is available from a controlled vocabulary registration authority. All terms in a controlled vocabulary should have an unambiguous, non-redundant definition. This is a design goal that may not be true in practice. It depends on how strict the controlled vocabulary registration authority is regarding registration of terms into a controlled vocabulary. At a minimum, the following two rules should be enforced:

  1. If the same term is commonly used to mean different concepts in different contexts, then its name is explicitly qualified to resolve this ambiguity.
  2. If multiple terms are used to mean the same thing, one of the terms is identified as the preferred term in the controlled vocabulary and the other terms are listed as synonyms or aliases.

A taxonomy is a collection of controlled vocabulary terms organized into a hierarchical structure. Each term in a taxonomy is in one or more parent-child relationships to other terms in the taxonomy. There may be different types of parent-child relationships in a taxonomy (e.g., whole-part, genus-species, type-instance), but good practice limits all parent-child relationships to a single parent to be of the same type. Some taxonomies allow poly-hierarchy, which means that a term can have multiple parents. This means that if a term appears in multiple places in a taxonomy, then it is the same term. Specifically, if a term has children in one place in a taxonomy, then it has the same children in every other place where it appears.

A thesaurus is a networked collection of controlled vocabulary terms. This means that a thesaurus uses associative relationships in addition to parent-child relationships. The expressiveness of the associative relationships in a thesaurus vary and can be as simple as “related to term” as in term A is related to term B.

People use the word ontology to mean different things, e.g. glossaries & data dictionaries, thesauri & taxonomies, schemas & data models, and formal ontologies & inference. A formal ontology is a controlled vocabulary expressed in an ontology representation language. This language has a grammar for using vocabulary terms to express something meaningful within a specified domain of interest. The grammar contains formal constraints (e.g., specifies what it means to be a well-formed statement, assertion, query, etc.) on how terms in the ontology’s controlled vocabulary can be used together.

People make commitments to use a specific controlled vocabulary or ontology for a domain of interest. Enforcement of an ontology’s grammar may be rigorous or lax. Frequently, the grammar for a "light-weight" ontology is not completely specified, i.e., it has implicit rules that are not explicitly documented.

A meta-model is an explicit model of the constructs and rules needed to build specific models within a domain of interest. A valid meta-model is an ontology, but not all ontologies are modeled explicitly as meta-models. A meta-model can be viewed from three different perspectives:

  1. as a set of building blocks and rules used to build models
  2. as a model of a domain of interest, and
  3. as an instance of another model.

When comparing meta-models to ontologies, we are talking about meta-models as models (perspective 2).

Note: Meta-modeling as a domain of interest can have its own ontology. For example, the CDIF Family of Standards, which contains the CDIF Meta-meta-model along with rules for modeling and extensibility and transfer format, is such an ontology. When modelers use a modeling tool to construct models, they are making a commitment to use the ontology implemented in the modeling tool. This model making ontology is usually called a meta-model, with “model making” as its domain of interest.

Bottom line: Taxonomies and Thesauri may relate terms in a controlled vocabulary via parent-child and associative relationships, but do not contain explicit grammar rules to constrain how to use controlled vocabulary terms to express (model) something meaningful within a domain of interest. A meta-model is an ontology used by modelers. People make commitments to use a specific controlled vocabulary or ontology for a domain of interest.


4:11:53 PM   comment []>  


Click here to visit the Radio UserLand website. © Copyright 2003 Ralph Poole.
Last update: 4/7/2003; 8:58:39 PM.
This theme is based on the SoundWaves (blue) Manila theme.
March 2003
Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          
Feb   Apr


Google

Listed on BlogShares


Blogroll Me!



<
? bostonites # >
>