RE: [xtm-wg] [xtm-cms] Re: XML Conceptual Model Report

["Graham Moore" <gdm@stepuk.com>]

Hi Luis,

Thanks for the comments. With regard to role we decided also that role is
not correct here and have changed it back to end. We have also made good
progress with the defintion and understanding of what resources are and how
they are accessed.

DRM and myself had a VERY good meeting at Shell yesterday with Chris Angus
and Matthew west and made staggering progress in refining the model.

I am updating the diagrams and some prose today, chris is adding more prose
over the weekend. So there will be a posting with these refinements on
monday.

cheers

graham

> -----Original Message-----
> From: sentto-1553146-724-973206292-gdm=stepuk.com@returns.onelist.com
> [mailto:sentto-1553146-724-973206292-gdm=stepuk.com@returns.on
> elist.com]
> On Behalf Of Luis J. Martinez
> Sent: 02 November 2000 23:10
> To: xtm-wg@egroups.com
> Subject: [xtm-wg] [xtm-cms] Re: XML Conceptual Model Report
>
>
>
> Great job on the model report. I think we are doing great progress.
> I have a few comments:
>
> Class Hierarchy:
>
> To me a link have a linkend instead of a role. The role is more a
> property like type and scope. Also, I see TopicAssociation being
> another derivation of Link like all others TopicOccur, TopicName,
> Scope, etc... TopicAssoc is a specialized type of Link with multiple
> Topics. TopicOccur is a specialized type of Link with a Topic and a
> Resource. If TopicOccur has different constraints and nothing
> in common
> with TopicAssoc, why should TopicOccur be a specialization of
> TopicAssoc?
>
> Identity:
>
> Identity looks to me like a type of Occurrence.
>
> Occurrence:
>
> I think TopicOccurence is missing the other end containing the Topic.
> On the diagram, it only contains OccurrenceRole. I am thinking that
> some of the derivation of Link can be self anchors since a Link is a
> Topic. More below about self anchors.
>
> Also, a ResourcedTopic should reference a ResourceObject with the
> Locator just being the method to resolve to the object. That way the
> model shows the relationship between Topics and the "real world". By
> topicmaps knowing explicitly about the "real" resource objects, it is
> possible to find out about the topicmap from resources themselves. The
> BOS would be the list of ResourceObjects.
>
> Self Anchors:
>
> I think that Occurrence, Scope, Type, and Name links can be self
> anchors because Links are Topics. When creating an Occurrence, a Topic
> is linked to a Resource. So, you have a the Topic role "associated" to
> a Resource, and the TopicOccurence it self as a Topic "associated" to
> the Resource. There are two Topic existing in the same structure that
> could be the same thing.
>
> Best regards,
>
> Luis
>
> -------------------------- eGroups Sponsor
> -------------------------~-~>
> Create your business web site your way now at Bigstep.com.
> It's the fast, easy way to get online, to promote your business,
> and to sell your products and services. Try Bigstep.com now.
> http://click.egroups.com/1/9183/4/_/337252/_/973206292/
> --------------------------------------------------------------
> -------_->
>
> To Post a message, send it to:   xtm-wg@eGroups.com
>
> To Unsubscribe, send a blank message to:
> xtm-wg-unsubscribe@eGroups.com
>
>
> ______________________________________________________________
> __________
> This message has been checked for all known viruses, by Star
> Internet,
> delivered through the MessageLabs Virus Control Centre.
> For further information visit:
> http://www.star.net.uk/stats.asp
>
>


________________________________________________________________________
This message has been checked for all known viruses, by Star Internet, 
delivered through the MessageLabs Virus Control Centre. 
For further information visit:
http://www.star.net.uk/stats.asp


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/4/_/337252/_/973242085/
---------------------------------------------------------------------_->

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

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