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] Newly detected backward compatibility error - TransportContract


Ok Ken,

forget sub-contracts now, also it is not viable as this addition would
require a party too.

I vote for (A) as nomination and delivery date are common concepts to
transportation, constructions, ...

I really prefere we enhance the actual base Contract for these new info.

Roberto

> At 2010-07-22 16:27 +0200, Roberto Cisternino wrote:
>>I have a business question on this topic.
>>
>>For which reason we are going to use a specific "Transport Contract"
>> class
>>over the generic "Contract" class ?
>
> Yes, the answer to that is critical to the direction we choose to take.
>
>> From the information below I do not see a valid reason.  I mean the
>>following information seems to me still related to *any* contract and
>>sub-contract.
>>
>>So I would see a more simple solution where we just update the actual
>>cac:Contract by adding "NominationPeriod" and "ContractualDelivery" at
>> the
>>end of its structure.
>
> Yes, this is my proposed solution (A) to this problem.  All the more
> reason if they are not specific to transportation as I was worried they
> were.
>
> A note to the TSC:  the existing Contract has only optional
> constructs so it would seem that (A) would meet your users needs by
> leaving the "old" constructs absent and only using the new constructs
> you have defined.
>
>>Moreover I would suggest to add a Sub-Contract (0..n) too.
>
> Can we please leave that question to the response to PRD01?  I know
> it is a simple change but at this (very!) late stage to prepare PRD01
> for review I would like to restrict discussions only to things that
> at this moment are broken or unresolved.
>
> . . . . . . . . . . . Ken
>
>> > At 2010-07-18 22:02 -0400, I wrote:
>> >><cac:TransportContract> is obliged to contain at
>> >>least the old children, but it is allowed to
>> >>have new optional children.  I see three ways to fix this:
>> >>
>> >>(A) We could add the new items to the old
>> >><Contract> but they aren't related to contracts
>> >>in general, only to transportation
>> >>contracts.  But that isn't so bad since users
>> >>are already used to finding things in objects that they don't need.
>
>
>
> --
> XSLT/XQuery training:   after http://XMLPrague.cz 2011-03-28/04-01
> Vote for your XML training:   http://www.CraneSoftwrights.com/m/i/
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/m/
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/m/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>


-- 
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor

  Roberto Cisternino

  mobile: +39 328 2148123 begin_of_the_skype_highlighting              +39
328 2148123      end_of_the_skype_highlighting
  skype:  roberto.cisternino.ubl-itlsc

[UBL Technical Committee]
    http://www.oasis-open.org/committees/ubl

[UBL Online Community]
    http://ubl.xml.org

[UBL International Conferences]
    http://www.ublconference.org

[UBL Italian Localization Subcommittee]
    http://www.oasis-open.org/committees/ubl-itlsc

[Iniziativa divulgativa UBL Italia]
    http://www.ubl-italia.org




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