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] XTM 1.0 AG Review Specification


Hi, I don't mean to intrude on all of the great work that the AG is doing
but I had some questions/comments on the specification that I was hoping I
could share.

Since the content model of <topic> includes "instanceOf*", I'm assuming that
topics can be instances of multiple classes? Why can't occurrences and
associations? If they could then you could restrict <instanceOf> to
appearing only once but allow its content to contain multiple <topicRef>s or
<subjectIndicatorRef>s.

>From an aesthetic point of view, <baseNameString> just looks funny. Why not
<name><baseName>My Base Name</baseName></name> instead? This seems more
applicable since <baseName> also contains <variant> elements which are
alternate names and not really part of the base name.

If I want a set of variant names to be applicable across different scopes,
do they have to be repeated in the <baseName> element that contains each of
these scopes? Or are the variant names declared in the unconstrained scope
used as a fallback when no matching parameters are found in a specific
scope?

The first example in section 3.7.3 (<variant> Element) is rather perplexing.
Are the two topics part of the same document? If I'm not mistaken, the
second topic (with the id of "sort") is meant to be merged with the official
"sort" published subject indicator based on its sole subjectIndicatorRef.
The offical "sort" includes an equivalent subjectIndicatorRef so the two
topics are deemed to have the same subject, correct? Why didn't the example
refer to the offical "sort" directly? Are the core PSIs automatically merged
with every topic map?

By the way, core.xtm, language.xtm, and country.xtm are undisplayable with
Internet Explorer. It's complaining about an undeclared xlink namespace
prefix. I don't know why it's not getting it from the DTD (where it's
declared as #FIXED) but it would be nice if that could be added.

Why <roleSpec> and not just <role>?

Typo in F.2.4: "considrer".

Since you've created topics for language and country codes will you also be
publishing PSIs for the various MIME media types as well?

Thanks for your time and the fantastic spec,
Jason.


------------------------ Yahoo! Groups Sponsor ---------------------~-~>
eGroups is now Yahoo! Groups
Click here for more details
http://click.egroups.com/1/11231/0/_/337252/_/981867241/
---------------------------------------------------------------------_->

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

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



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


Powered by eList eXpress LLC