RE: [4774] Schema binding issue description - please review usecases

You are correct on 4.1

4.3 covers the situation you mention ( definition file with no 
schemaLocation attribute specified ) but it doesn't stop here. 
SchemaLocation is also an optional attribute for xs:import  so this is 
another case where schema location is not made available within the 
attached document. The point here is that we can't assume there is 
dependable schema location information within the SMLIF documents that can 
be used for associating instances with corresponding definition documents. 



Thank you,
Valentina Popescu
IBM Toronto Labs
Phone:  (905)413-2412         (tie-line  969)
Fax: (905) 413-4850




"Smith, Virginia (HP Software)" <virginia.smith@hp.com> 
Sent by: public-sml-request@w3.org
08/24/2007 04:36 PM

To
<public-sml@w3.org>
cc

Subject
RE: [4774] Schema binding issue description - please review usecases






So constraint 4.1 states that we can't require the SML-IF producer to 
include the schema file in the SML-IF document - so a definition document 
may be located elsewhere outside the model. 
 
And constraint 4.3 says that, even if the producer does include the schema 
in the SML-IF document, the schema may be written such that no 
schemaLocation 'hints' are provided. Even if the schemaLocations are 
included, the consumer, when validating the model instance documents, may 
not even use these location hints.
 
Do I have that right?
 
--
ginny

From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On 
Behalf Of Valentina Popescu
Sent: Thursday, August 23, 2007 8:45 PM
To: public-sml@w3.org
Subject: RE: [4774] Schema binding issue description - please review 
usecases


Hi Ginny 

What I am trying to say in 4.3 is that a producer of an SMLIF file may 
just package existing schema documents ( he is not the author of those 
documents ) so he cannot control what schema options are used within those 
files. In other words, we have to assume that SMLIF definition files may 
be written in any way allowed by the schema spec, for example using 
import, include statements with or without schemaLocation being specified, 
and so on 


Schema assessment and schema validation represents the same thing; 'schema 
assessment' is a more sophisticated wording for schema validation. I am 
pretty sure Sandy or Michael can elaborate more on this if necessary :)

Thank you,
Valentina Popescu
IBM Toronto Labs
Phone:  (905)413-2412         (tie-line  969)
Fax: (905) 413-4850



"Smith, Virginia (HP Software)" <virginia.smith@hp.com> 
08/23/2007 09:48 PM 


To
Valentina Popescu/Toronto/IBM@IBMCA, <public-sml@w3.org> 
cc

Subject
RE: [4774] Schema binding issue description - please review usecases








Valentina, 
  
I'm not quite sure what Constraint 4.3 is intending to say. Can you 
clarify this? 
  
Also, is schema assessment the same as schema validation? 
  
-- 
ginny 
 
---------------------
Virginia Smith
HP Software / BTO R&D
916-785-9940
8000 Foothills Blvd | Roseville | CA 95747
www.hp.com/software 

From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On 
Behalf Of Valentina Popescu
Sent: Thursday, August 23, 2007 2:00 PM
To: public-sml@w3.org
Subject: [4774] Schema binding issue description - please review usecases


Hi everybody 

As discussed in today's call, I will make sure the proposal for the schema 
binding issue will be made available on the sml public list no later then 
end of day tomorrow so that you have time to read it and have comments 
ready by the f2f next week. 

If at all possible I would like you to review the attached document below 
describing the requirements and constraints related to this issue and see 
if there are any usecases not covered that you may care about. 

Thank you,
Valentina Popescu
IBM Toronto Labs
Phone:  (905)413-2412         (tie-line  969)
Fax: (905) 413-4850


Sandy Gao/Toronto/IBM@IBMCA 
Sent by: public-sml-request@w3.org 
08/21/2007 10:37 PM 


To
public-sml@w3.org 
cc

Subject
[w3c sml] [4774] Schema binding issue description











Team, 

This is to (partially) complete action 113 (
http://www.w3.org/2005/06/tracker/sml/actions/113), on behalf of 
Valentina, who's occupied by other tasks. 

The attached is a more detailed description of bug 4774 (
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4774). Note that this is 
only to describe the problem. Proposal(s) will follow. It helps for people 
to get familiar with the background information and think about ways to 
resolve it independently, before overwhelmed by proposal(s). 



Thanks,
Sandy Gao
XML Technologies, IBM Canada
Editor, W3C XML Schema WG
Member, W3C SML WG
(1-905) 413-3255 T/L 969-3255