[sc34wg3] RE: [tmcl-wg] RE: New version of TMCL Requirements, use cases and specification (Dmitry)

sc34wg3@isotopicmaps.org sc34wg3@isotopicmaps.org
Tue, 2 Nov 2004 09:02:13 +0100


This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C0B2.43287E69
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Thanks for the feedback and comments.
=20
In the first example the intent was to epress that exactly and only the =
roles described were allowed but in the second it is saying that these =
two roles must be present BUT that other roles, either of the same type =
or different types may be present.=20
=20
So in one sense it is about the cardinality of the roles but it is also =
about the ability to have ANY other kind of role in there for which, =
potentially, no additional constraints are defined. You could define it =
as two roles that are non-optional and have a specific type and N roles =
of N cardinality with no type constraint. But I think that is for the =
standard to define, whereas the focus of the UC document is to illicit a =
feel for the nature of the way topicmaps can be constrained.
=20
So, I do not think you are wrong but the nature of this UC document is =
not to capture the generic patterns but more to scope smaller idioms; =
with that in mind I think the two cases are seperately valid.
=20
regards,=20
=20
Graham

________________________________

From: tmcl-wg-admin@isotopicmaps.org on behalf of Giovani Librelotto
Sent: Mon 01/11/2004 20:28
To: tmcl-wg@isotopicmaps.org
Cc: sc34wg3@isotopicmaps.org
Subject: [tmcl-wg] RE: New version of TMCL Requirements, use cases and =
specification (Dmitry)




Hello there,

In new version of TMCL Requirements and Use Cases <URL:
http://www.jtc1sc34.org/repository/0548.htm>, section 4.1.1.U3 (Valid
subject indicator), which is the difference between the items 'a' and =
'b'?
For me, both define the cardinality of subject indicator, so it's the =
same
kind of constraint. Am I wrong?
Best regards,

------------------------------------
Giovani Rubert Librelotto
Ph.D. Student - Informatics Department
Universidade do Minho
Braga - Portugal
grl@di.uminho.pt


> -----Original Message-----
> From: tmcl-wg-admin@isotopicmaps.org
> [mailto:tmcl-wg-admin@isotopicmaps.org] On Behalf Of
> tmcl-wg-request@isotopicmaps.org
> Sent: segunda-feira, 25 de Outubro de 2004 11:31
> To: tmcl-wg@isotopicmaps.org
> Subject: tmcl-wg digest, Vol 1 #77 - 1 msg
>
> Send tmcl-wg mailing list submissions to
>       tmcl-wg@isotopicmaps.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://www.isotopicmaps.org/mailman/listinfo/tmcl-wg
> or, via email, send a message with subject or body 'help' to
>       tmcl-wg-request@isotopicmaps.org
>
> You can reach the person managing the list at
>       tmcl-wg-admin@isotopicmaps.org
>
> When replying, please edit your Subject line so it is more
> specific than "Re: Contents of tmcl-wg digest..."
>
>
> Today's Topics:
>
>    1. New version of TMCL Requirements, use cases and
> specification (Dmitry)
>
> --__--__--
>
> Message: 1
> To: sc34wg3@isotopicmaps.org, tmcl-wg@isotopicmaps.org
> From: Dmitry <dmitryv@cogeco.ca>
> Date: Sun, 24 Oct 2004 13:14:53 -0400
> Subject: [tmcl-wg] New version of TMCL Requirements, use
> cases and specification
>
> New version of TMCL Requirements and Use Cases
>
> http://www.jtc1sc34.org/repository/0548.htm
>
> and TMCL specification (first draft)
>
> http://www.jtc1sc34.org/repository/0549.htm
>
> from TMCL editors: Dmitry Bogachev, Graham Moore, and Mary Nishikawa,
>
> available for review and comments.
>
>
>
> --__--__--
>
> _______________________________________________
> tmcl-wg mailing list
> tmcl-wg@isotopicmaps.org
> http://www.isotopicmaps.org/mailman/listinfo/tmcl-wg
>
>
> End of tmcl-wg Digest



------_=_NextPart_001_01C4C0B2.43287E69
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7232.7">=0A=
<TITLE>[tmcl-wg] RE: New version of TMCL Requirements, use cases and =
specification (Dmitry)</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText22568 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Hi,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks for the feedback and =0A=
comments.</FONT></DIV></FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>In the first example the =
intent was to =0A=
epress that exactly and only the roles described were allowed but in the =
second =0A=
it is saying that these two roles must be present BUT that other roles, =
either =0A=
of the same type or different types may be present. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So in one sense it is about =
the cardinality =0A=
of the roles but it is also about the ability to have ANY other kind of =
role in =0A=
there for which, potentially, no additional constraints are defined. You =
could =0A=
define it as two roles that are non-optional and have a specific type =
and N =0A=
roles of N cardinality with no type constraint. But I think&nbsp;that is =
for the =0A=
standard to define, whereas the focus of the UC document is to illicit a =
feel =0A=
for the nature of the way topicmaps can be constrained.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So, I do not think you are =
wrong but the =0A=
nature of this UC document&nbsp;is not to capture the generic patterns =
but more =0A=
to scope smaller idioms; with that in mind I think the two cases are =
seperately =0A=
valid.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>regards, </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Graham</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> tmcl-wg-admin@isotopicmaps.org =
on behalf =0A=
of Giovani Librelotto<BR><B>Sent:</B> Mon 01/11/2004 20:28<BR><B>To:</B> =0A=
tmcl-wg@isotopicmaps.org<BR><B>Cc:</B> =0A=
sc34wg3@isotopicmaps.org<BR><B>Subject:</B> [tmcl-wg] RE: New version of =
TMCL =0A=
Requirements, use cases and specification (Dmitry)<BR></FONT><BR></DIV>=0A=
<DIV><BR>=0A=
<P><FONT size=3D2>Hello there,<BR><BR>In new version of TMCL =
Requirements and Use =0A=
Cases &lt;URL:<BR><A =0A=
href=3D"http://www.jtc1sc34.org/repository/0548.htm">http://www.jtc1sc34.=
org/repository/0548.htm</A>&gt;, =0A=
section 4.1.1.U3 (Valid<BR>subject indicator), which is the difference =
between =0A=
the items 'a' and 'b'?<BR>For me, both define the cardinality of subject =0A=
indicator, so it's the same<BR>kind of constraint. Am I wrong?<BR>Best =0A=
regards,<BR><BR>------------------------------------<BR>Giovani Rubert =0A=
Librelotto<BR>Ph.D. Student - Informatics Department<BR>Universidade do =0A=
Minho<BR>Braga - Portugal<BR>grl@di.uminho.pt<BR><BR><BR>&gt; =
-----Original =0A=
Message-----<BR>&gt; From: tmcl-wg-admin@isotopicmaps.org<BR>&gt; [<A =0A=
href=3D"mailto:tmcl-wg-admin@isotopicmaps.org">mailto:tmcl-wg-admin@isoto=
picmaps.org</A>] =0A=
On Behalf Of<BR>&gt; tmcl-wg-request@isotopicmaps.org<BR>&gt; Sent: =0A=
segunda-feira, 25 de Outubro de 2004 11:31<BR>&gt; To: =0A=
tmcl-wg@isotopicmaps.org<BR>&gt; Subject: tmcl-wg digest, Vol 1 #77 - 1 =0A=
msg<BR>&gt;<BR>&gt; Send tmcl-wg mailing list submissions to<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tmcl-wg@isotopicmaps.org<BR>&gt;<BR>&gt; =
To =0A=
subscribe or unsubscribe via the World Wide Web, visit<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =0A=
href=3D"http://www.isotopicmaps.org/mailman/listinfo/tmcl-wg">http://www.=
isotopicmaps.org/mailman/listinfo/tmcl-wg</A><BR>&gt; =0A=
or, via email, send a message with subject or body 'help' to<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
tmcl-wg-request@isotopicmaps.org<BR>&gt;<BR>&gt; =0A=
You can reach the person managing the list at<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
tmcl-wg-admin@isotopicmaps.org<BR>&gt;<BR>&gt; =0A=
When replying, please edit your Subject line so it is more<BR>&gt; =
specific than =0A=
"Re: Contents of tmcl-wg digest..."<BR>&gt;<BR>&gt;<BR>&gt; Today's =0A=
Topics:<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp; 1. New version of TMCL =
Requirements, =0A=
use cases and<BR>&gt; specification (Dmitry)<BR>&gt;<BR>&gt; =0A=
--__--__--<BR>&gt;<BR>&gt; Message: 1<BR>&gt; To: =
sc34wg3@isotopicmaps.org, =0A=
tmcl-wg@isotopicmaps.org<BR>&gt; From: Dmitry =
&lt;dmitryv@cogeco.ca&gt;<BR>&gt; =0A=
Date: Sun, 24 Oct 2004 13:14:53 -0400<BR>&gt; Subject: [tmcl-wg] New =
version of =0A=
TMCL Requirements, use<BR>&gt; cases and specification<BR>&gt;<BR>&gt; =
New =0A=
version of TMCL Requirements and Use Cases<BR>&gt;<BR>&gt; <A =0A=
href=3D"http://www.jtc1sc34.org/repository/0548.htm">http://www.jtc1sc34.=
org/repository/0548.htm</A><BR>&gt;<BR>&gt; =0A=
and TMCL specification (first draft)<BR>&gt;<BR>&gt; <A =0A=
href=3D"http://www.jtc1sc34.org/repository/0549.htm">http://www.jtc1sc34.=
org/repository/0549.htm</A><BR>&gt;<BR>&gt; =0A=
from TMCL editors: Dmitry Bogachev, Graham Moore, and Mary =0A=
Nishikawa,<BR>&gt;<BR>&gt; available for review and =0A=
comments.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; --__--__--<BR>&gt;<BR>&gt; =0A=
_______________________________________________<BR>&gt; tmcl-wg mailing =0A=
list<BR>&gt; tmcl-wg@isotopicmaps.org<BR>&gt; <A =0A=
href=3D"http://www.isotopicmaps.org/mailman/listinfo/tmcl-wg">http://www.=
isotopicmaps.org/mailman/listinfo/tmcl-wg</A><BR>&gt;<BR>&gt;<BR>&gt; =0A=
End of tmcl-wg Digest<BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C4C0B2.43287E69--