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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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

Subject: Re: [ubl] Partial UBL 1.0 build (11 April)- use of <<import>> inFigure 2 Schema Dependencies

Anne Hendry wrote:

6.4 Schema Dependencies

- Figure 2 shows '<< import >>' for all the schemas except the CCP.
  Shouldn't the lines going into this module show an << import >>
  as well?

to which Mark Crawford replied:

NDR requires all schema modules (other than internal schema modules) to be in their own namespace.  Assuming we followed that rule, then CCP must also be an import.  (BTW, UN/CEFACT will not use the CCP module).
i am not sure i inderstand mark's comment but the diagram is showing that all schema modules are dependent on the CCP schema. all these dependencies imply import in the schema sense. the label <<import>> is actually a UML property stereotype - not necessarily meaning schema import - but it gets over the intention.  so it is my mistake, they should either all be labelled or none should be.  please find attached a revised copy (Jon, also note the "ize" spelling missed out in the last build.)

BTW The CCP schema imports none (it is independent of the other modules). This is the reason why Marty makes the comment about the 'unstripped' code list schema being independent - it is because it only imports the CCP and CCP is only needed if you have annotation documentation.
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

JPEG image

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