[sc34wg3] TMCL Requirements

[Patrick Durusau]

Graham, Mary,

Thanks for the additional insight!

So I take it that TMCL does specify the application of constraints but 
when such constraints are to be applied, is up to the user?

What I found misleading was not specifying "when," which I took to mean 
some other mechanisms was required in addition to TMCL. What was meant, 
if I am reading your and Mary's replies correctly, was to indicate the 
application of any constraint specifiable by TMCL is up to the user. But 
if it is applied, that is done using TMCL.

See everyone in London!

Patrick



Graham Moore wrote:

>Hi Patrick,
>
>The intention here was also to indicate that people could apply the
>constraints at any time, on import, before export, in real time etc. We
>werent going to say when this had to happen.
>
>gra
>
>--------------------
>
>Graham Moore, Ontopian               <URL: http://www.ontopia.net >
>GSM: +44 (0) 7769658611             moore@ontopia.net
>
>----- Original Message -----
>From: "Mary Nishikawa" <nisikawa@fuchinobe.oilfield.slb.com>
>To: <sc34wg3@isotopicmaps.org>
>Sent: Wednesday, April 30, 2003 2:45 AM
>Subject: Re: [sc34wg3] TMCL Requirements
>
>
>  
>
>>Hi Partick,
>>
>>Glad that you are reviewing this now. This needs to be elaborating on, I
>>    
>>
>agree.
>  
>
>>Non requirements are for saying, "Of course, we would never specify that!"
>>This is stuff that can seem obvious, but sometimes needs to be put in
>>writing nevertheless.
>>
>>*Patrick
>>    
>>
>>>I found the Non-Requirement for TMCL of:
>>>
>>>       4.1.1 When these constraints are applied
>>>
>>>rather odd. I am assuming that I am mis-reading the intent of the text
>>>since I would think a selector would choose when a constraint is applied.
>>>Or does it mean that the selector chooses the where the constraint will
>>>      
>>>
>be
>  
>
>>>applied and something else applies the constraint?
>>>      
>>>
>>Behind the choice of which selectors  or restrictions to use or when to
>>use then, is a user.
>>
>>The language will not tell users of the TMCL when they should  or should
>>not constrain one TM contruct or another to suit a particular purpose. We
>>are not a data typing/ data constraining police. For example we will not
>>specify that the users are required  to use the xml schema built in
>>datatype "date"for all instances of birthdates used in their topic maps.
>>
>>Goverment bodies/corporations may want to impose these kinds of rules, but
>>this is not in our scope.
>>
>>This is what I meant when I wrote it. If adding this helps, I will do so.
>>    
>>
>Thanks.
>  
>
>>I think we will be spending most of our time looking at the requirements
>>that can be agreed to, and others that we need to raise issues for.  We
>>are all leaving for London soon, so please bring your list. I probably
>>will not be able to respond after today because of trip preparations.
>>
>>Cheers,
>>Mary
>>
>>_______________________________________________
>>sc34wg3 mailing list
>>sc34wg3@isotopicmaps.org
>>http://www.isotopicmaps.org/mailman/listinfo/sc34wg3
>>
>>    
>>
>
>_______________________________________________
>sc34wg3 mailing list
>sc34wg3@isotopicmaps.org
>http://www.isotopicmaps.org/mailman/listinfo/sc34wg3
>
>  
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu
Co-Editor, ISO Reference Model for Topic Maps