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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-pre-award message

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


Subject: Answer Pre-award draft 1.7 ready to play with


Thank you Ken

Let us not change to something with Hash if it OK with you the label MessageFormat is better than Hash.

It can either be:

<cbc:MessageFormat>cms</cbc:MessageFormat>

Or:

<cbc:MessageFormat>1.2.840.113549.1.9.16.0.1</cbc:MessageFormat>

So the instances are correct except for the sha1.

Best Regards
Ole


-----Oprindelig meddelelse-----
Fra: ubl-pre-award@lists.oasis-open.org [mailto:ubl-pre-award@lists.oasis-open.org] På vegne af G. Ken Holman
Sendt: 30. maj 2016 03:40
Til: UBL Pre-award Procurement Subcommittee
Emne: [ubl-pre-award] Pre-award draft 1.7 ready to play with

Fellow UBL Pre-award Procurement SC members,

I've taken a snapshot of the "end of Sunday" working model off of 
Google and put it into Kavi here:

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

It is labeled 1.7 for test purposes.  Complete schemas are included, 
continuing to use the test namespaces.

I question the label "MessageFormat" that was given to me.  The value 
"sha1" would be interpreted as a type of hash ... would the element 
name <cbc:MessageHashTypeID> be a better name?  Is there a better 
word that "Message" or is that the scope?  Where have we used the 
word "Message" before?

I've added two test instances to the xml/ directory to illustrate my 
proposed structuring for the encryption information.

I've hacked the existing test instance to accommodate changes to the 
model since the last version.

I've incorporated support for the OID abbreviation and equivalence.

The Pre-award-Model-Analysis-1.7.html file includes a comparison to 
UBL 2.1 to show what items have been changed and added.  This would 
be used in our proposal to the Technical Committee as a summary of 
what needs to be changed from the SC perspective.

I have disengaged the NDR rule that ABIEs in the common library be 
sorted so that the changes are grouped together:  the first batch 
following "Criterion" and the second batch following "TenderPreparation".

. . . . . . . . Ken

--
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK |
Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/o/ |
G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com |
Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts |
Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal |


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


---------------------------------------------------------------------
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 



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