[OASIS Issue Tracker] (UBL-39) EstimatedTiming cardinality (0..1) in 'TenderingTerms' in relation to RecurringProcurementIndicator

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63108#comment-63108 ] 

Ken Holman commented on UBL-39:
-------------------------------

Available in: artefacts-ubl-2.2-csd01wd06-20160808-1240z.zip

https://www.oasis-open.org/committees/document.php?document_id=58668 


> EstimatedTiming cardinality (0..1) in 'TenderingTerms' in relation to RecurringProcurementIndicator
> ---------------------------------------------------------------------------------------------------
>
>                 Key: UBL-39
>                 URL: https://issues.oasis-open.org/browse/UBL-39
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: New Feature
>          Components: Artefacts
>         Environment: UBL Library
>            Reporter: Oriol Bausa Peris
>            Assignee: Oriol Bausa Peris
>
> Reasoning: The "Estimated time for further notices to be published" is mapped to "Contract notice/FrequencyPeriod/Description which is at the other end of the XSD and not directly attached to the recurring procurement indicator (to which the estimated timeing refers).  By creating it in the Tendering terms this will make things clearer and less messy.
>  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)