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

 


Help: OASIS Mailing Lists Help | MarkMail Help

topicmaps-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [xtm-wg] The Topic Naming Constraint



Steve,

thank you very much for your comments.

* Steven R. Newcomb
| [Geir Ove Gronmo:]
| 
| > First of all I'd like to say that I wholeheartedly agree with Lars
| > Marius on this matter. The Topic Naming Constraint is [extremely]
| > painful and too awkward - in my eyes it is a real show-stopper.
| 
| > I'll try to explain what I think is the problem with draconian Topic
| > Naming Constraint enforcement, which the standard(s) at this point
| > requires from an XTM processor. A conformant XTM processor has to
| > enforce these constraint, e.g. there cannot be _any_ exceptions if
| > you'd like to claim that your processor is conformant.
| 
| > I see the usefulness of being able to do automatic namespace-based
| > merges. This is extremely useful, but unfortunately the problem is
| > that people (myself included) believe that base names are intended for
| > labelling purposes, not for identification.
| 
| I'm baffled by your argument, Geir Ove.  You seem to be saying that we
| should do away with XTM's ability to support string-match-based topic
| merging because you don't agree that that is the purpose of baseName
| elements.

No! On the contrary it is so that I would like to introduce it to the
standard because as the current standard stands there is _no_ such
thing. Base names are defined for _labelling purposes_. The
specification says:

[Section 2.2.2.1]

"A base name is the base form of a topic name; it is always a
string. When an application chooses to use a particular topic name to
label a topic, the base name provides the string for the application to
use unless a variant exists that is deemed to be more apposite in the
processing context."

There are several other examples. Try searching for "label" and "ident"
yourself, and you'll see that this is so.

The specification mentions the TNC in several places, but NEVER (ever)
explains WHY it exist - and it NEVER mentions it in combination with
the word _identification_!

Geir O.

P.S. I'll try to answer the rest of your comments asap, there's quite a
few of them. :)


------------------------ Yahoo! Groups Sponsor ---------------------~-~>
eGroups is now Yahoo! Groups
Click here for more details
http://us.click.yahoo.com/kWP7PD/pYNCAA/4ihDAA/2n6YlB/TM
---------------------------------------------------------------------_->

To Post a message, send it to:   xtm-wg@eGroups.com

To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC