OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-csc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Fwd: [ubl-dev] Problems on Translating UBL XSD Schema into RelaxNG (2/6)]


  Not sure if this overlaps scs (ndr, cm?).  Who could best respond to this?
Thanks,
-Anne

-------- Original Message --------
Subject: [ubl-dev] Problems on Translating UBL XSD Schema into Relax NG 
(2/6)
Date: Mon, 02 Feb 2004 18:24:25 +0900
From: Hiroshi Naito <naitoh@is.oit.ac.jp>
To: ubl-dev@lists.oasis-open.org



Hi,

I send the report 2/6 about Problems on Translating UBL XSD 
Schema into Relax NG. I hope to get your advice and comment.

Please see the following page to understand Relax NG features.

http://www.xml.com/pub/a/2002/01/23/relaxng.html

-------------------------------------------------------------
2. Distinguish between pattern names for elements and types

2.1 The UBL Schema Description using XSD
 With UBL XSD Schema, names of elements and types are
separately managed with symbol space, so a element can be
defined along with a type which has a same name with the
element. 

 In most cases, elements and types in UBL XSD schemas have
different names, only except for NumericType and CodeType .

Codes from common/UBL-CoreComponentTypes-1.0-beta.xsd
  
  
    
  

Codes from common/UBL-RepresentationTerms-1.0-beta.xsd
  
  
    
      
    
  

2.2 The UBL Schema Description using Relax NG
1) Problem
 With Relax NG, as explained at 1.1, named patterns
corresponding to UBL XSD elements and types are defined using
 elements in a uniform way, then names for the
patterns element must be different to each other. But names
of elements and types for NumericType and CodeType are same,
so if pattern names for elements and types of NumericType and 
CodeType were generated according as the rule at 1.2,
syntax errors would be occurred.

2) Solution
 In order to distinguish these pattern names for elements and
types, a additional string "-element" is added to the names
for these elements, such as "ubl-cct-NumericType-element" and
"ubl-rt-CodeType-element".

Generated Codes in UBL-CoreComponentTypes-1.0-beta.rng
  
      
          
      
  
  
      
  

Generated Codes in UBL-RepresentationTerms-1.0-beta.rng
  
      
          
      
  
  
      
  

2.3 Proposition to change UBL XSD schema
 If XSD name for element "NumericType" were changed to
"Numeric" and XSD name for element "CodeType" were changed to
"Code", there would be no need for special naming rule which
was applied for "NumericType" and "Numeric" explained above.

Proposed Codes for common/UBL-CoreComponentTypes-1.0-beta.xsd
  
  
    
  

Proposed Codes for common/UBL-RepresentationTerms-1.0-beta.xsd
  
  
    
      
    
  

 There is a another "CodeType" Type in CoreComponentTypes
schema defined as following, but this is not referenced in
other schemas. Why is types in Codelists derived not from
cct:CodeType, but from rt:CodeType?

Codes from common/UBL-CoreComponentTypes-1.0-beta.xsd
  
  
  
    
      
        
        
        
        
        
        
        
        
        
      
    
  
-------------------------------------------------------------

Thanks


-----
Hiroshi Naito, Osaka Institute of Technology 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]