[INFOD-WG] Property constraints example

[Fisher, SM (Steve)]

Dieter,

I see our spec has finally been made public

Please see below ...

> -----Original Message-----
> From: Dieter Gawlick [mailto:dieter.gawlick at oracle.com] 
> Sent: 06 July 2007 19:32
> To: Fisher, SM (Steve)
> Cc: infod-wg at ggf.org
> Subject: Re: Property constraints example
> 
> Steve,
> 
> In the car buyer/dealer use case I assumed that the names of 
> the vocabularies are unique - just to make it more readable. 
> In this case you don't need an EPR. Obviously, if vocabulary 
> names are not unique the constraint has to use an EPR as 
> vocabulary identifier; I don't think that we have to discuss 
> this in the specification but the use case should be more 
> explicit - the specifications point to the use cases. Please 
> add a comment and I will extend the text.

I think we should always have the EPRs to make things explicit otherwise
the registry has no way of finding the vocabulary as the EPR is the
*only* handle. We have already said that the names are not guaranteed to
be unique.

So in this case when we add the EPR of the property vocabulary we have
an explict dependency and there is no problem with handling the "disable
new" deletion of that vocabulary. The original question was how to
handle "disable new" on an instance of a property vocabulary. Do we have
such an example in the use case documet?

> Distance functions are well established for managing spatial 
> data. If you like, I could add a note.

I think we said the queries were Xqueries/XPath - I presume there is a
way of defining functions unambiguously within their own name space. In
this case do you mean the great circle distance between 2 points defined
by latitude and longitude - and what are the units? Distance does mean
something in Xquery but it is nothing to do with geospatial distances!
We  don't want application specific intelligence in the registry
otherwise we lose portability.

Steve


> 
> Dieter
> 
> Fisher, SM (Steve) wrote: 
> 
> 	Dieter,
> 	
> 	I have started going through the use cases - in 
> particular trying to
> 	understand how to handle "disable new".
> 	
> 	I find there is no example of a property constraint in 
> the first use
> 	case. The first examples I see are on page 34 where we 
> have: for the Car
> 	Dealer
> 	
> 	<infod:PropertyConstraint>
> 	     Car_Buyer (Distance < 30 miles) and CR > 4) 
> 	</infod:PropertyConstraint> 
> 	
> 	On page 35 in Registration of Car Buyer as Consumer we have:
> 	
> 	<infod:PropertyConstraint>
> 	     Car_Dealer (Dealer: Years in business > 10 years, 
> BBB rating > 3,
> 	Service rating > 10) </infod:PropertyConstraint>
> 	
> 	On page 36 in Car Buyer adds Subscription we have:
> 	
> 	<infod:PropertyConstraint> 
> 	     Distance (CarCommunityDealerVocabEPR.Location,  
> 	 
> 	
> http://www.carcommunity.com/CCInfoDRegistry/CarBuyerr/Susan_Ma
> ria_Callas
> 	) < 25
> 	</infod:PropertyConstraint>  
> 	
> 	With the first two, how is the system expected to know 
> what a Car_Buyer
> 	and Car_Dealer is. Surely we need the EPR of a property 
> vocabulary
> 	somewhere - then we have the explicit dependency upon 
> the property
> 	vocabulary.
> 	
> 	For the last one - where is the function distance 
> defined, how does the
> 	URL return coordinates and in what frame and units?
> 	
> 	Steve
> 	  
> 
> 
> -- 
> 
> 
> Oracle Email Signature Logo
> Dieter Gawlick | Architect | 650.506.8706
> Oracle Server Technologies
> 500 Oracle Parkway | Redwood Shores, CA 94065 
>