[sc34wg3] Draft Reference Model

[Sam Hunting]

Wait!

I think there are two real issues here:

(1) Clause 3.5.1.3.1.2 of the RM reads "The node serves as the A endpoint
of two or more AC arcs." However, the node at left in the drawing
(demanded by "a1" in the markup) has only one AC arc, and therefore by the
RM as it stands is not well formed.

Does clause 3.5.1.3.1.2 need to change "two" to "one"?

(2) Is the best/only way to model the prose statement "Hot and cold are
opposites" an assertion with a single role player that represents the set
{"hot","cold"}

I say wait! because having some angle brackets before us, it will be all
too tempting to get into an argument about syntax. That may be an issue,
but I think issues (1) and (2) raised above are more important -- for the
purposes of this thread, perhaps we could agree that *some* angle brackets
could generate this graph (assuming it to be well-formed) under the
constaints laid down in clause 5.





On Mon, 18 Nov 2002, Jan Algermissen wrote:

> Lars Marius Garshol wrote:
> > 
> > * Jan Algermissen
> > |
> > | Example:
> > |
> > | "'Hot' and 'cold' are opposites"
> > |
> > | This would be modeled in the graph like this:
> > |
> > |
> > |                                x2
> > |                               /
> > |                              C-----R2
> > |                             /
> > |        T1                  A-----T2
> > |        |                  /
> > |        |       R1        C-----R3
> > |        |       |        /
> > |        A-------C-------x1
> > |                         \
> > |                          C-----R3
> > |                           \
> > |                            A-----T2
> > |                             \
> > |                              C-----R2
> > |                               \
> > |                                x3
> > |
> > |
> > | The nodes above represent the following subjects:
> > |
> > | T1: the assertion type 'at-opposites'
> > | R1: the role 'role-opposite'
> > | x1: the players of the role-opposite  ("The Opposites")
> > | R2: the role 'role-setMember'
> > | R3: the role 'role-set'
> > | T2: the assertion type 'at-set-setMember'
> > | x2: 'hot'
> > | x3: 'cold'
> > 
> > This was rather difficult to follow. Could you show what this would
> > look like in XTM syntax?
> 
> Here it is:
> 
> <assertion id="a1">
>   <instanceOf>
>     <topicRef xlink:href="#at-opposites" />
>   </instanceOf>
>   <member>
>     <roleSpec>
>       <topicRef xlink:href="#role-opposite" />
>     </roleSpec>
>     <topicRef xlink:href="#cold" />
>     <topicRef xlink:href="#hot" />
>   </member>
> </assertion>
> 
> Well, or like this:
> 
> <assertion id="a2">
>   <instanceOf>
>     <topicRef xlink:href="#at-opposites" />
>   </instanceOf>
>   <member>
>     <roleSpec>
>       <topicRef xlink:href="#role-opposite" />
>     </roleSpec>
>     <topicRef xlink:href="#hot" />
>   </member>
>   <member>
>     <roleSpec>
>       <topicRef xlink:href="#role-opposite" />
>     </roleSpec>
>     <topicRef xlink:href="#cold" />
>   </member>
> </assertion>
> 
> Jan
> > 
> > --
> > Lars Marius Garshol, Ontopian         <URL: http://www.ontopia.net >
> > ISO SC34/WG3, OASIS GeoLang TC        <URL: http://www.garshol.priv.no >
> > 
> > _______________________________________________
> > sc34wg3 mailing list
> > sc34wg3@isotopicmaps.org
> > http://www.isotopicmaps.org/mailman/listinfo/sc34wg3
> 
> 

Sam Hunting
eTopicality, Inc.

---------------------------------------------------------------------------
"Turn your searching experience into a finding experience."(tm)

Topic map consulting and training: www.etopicality.com
Free open source topic map tools:  www.gooseworks.org

XML Topic Maps: Creating and Using Topic Maps for the Web.
Addison-Wesley, ISBN 0-201-74960-2.
---------------------------------------------------------------------------