Re: [ubl-psc] Status of final deliverables

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2012-02-04 11:20 +0100, Arianna Brutti wrote:
> this mail to inform you that I implemented the pending issues (14, 
> 20, 37, 49 on the enclosed IssueList).
>
> Please note that:
>
> - the ubl-psc final approving on these issues is still missing; on 
> Monday, the psc is going to have a meeting, so some small changes 
> could be neeed.
>
> - while I was creating the ReceiptAdviceTypeCode (issue 49), 
> something of wrong happened in eDoCreator; so, I was able to add the 
> BBIE to ReceiptAdvice, as planned, but it doesn't have a 
> QualifiedDataType, as expected.
> Ken, maybe you know as the problem can be resolved, otherwise I'll 
> ask for helping to eDoCreator staff.

Just to practice preparing for Monday, I've just done a preliminary 
export and I note that eDoCreator is creating an improper UBL element 
name for the new ReceiptAdviceTypeCode by duplicating the word "Code" 
at the end, because of the way the components are specified:

  <ReceiptAdviceTypeCodeCode>

I think, Arianna, that you need to specify the Property Term 
Possessive Noun to be, simply, "Receipt Advice Type" and not "Receipt 
Advice Type Code", and the Property Term Primary Noun to be "Code" 
and not absent.

That should produce the correct element name.

. . . . . . . . . Ken

p.s. I haven't yet run a full model check ... I just wanted to bring 
this to your attention separately because of its importance


--
Contact us for world-wide XML consulting and instructor-led training
Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h
Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/o/
G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com
Google+ profile: https://plus.google.com/116832879756988317389/about
Legal business disclaimers:    http://www.CraneSoftwrights.com/legal