View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000278510000-006: MappingsSpecpublic2014-05-06 17:492014-10-16 11:30
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Target Version1.03Fixed in Version1.03 
Summary0002785: base64 encoding for DataTypeDescription needs to be accurately documented
Description

We discussed Michel’s issue decoding and interpreting the Data Type Dictionary value in the Part 5 Nodeset file.

The last sentence in Part 6, Annex E gives this clue:

“This is the DataTypeDescription Node for the DataTypeDescription declared above. The XML Schema document is a UTF-8 document stored as a base64 string. This allows clients to read the schema for the”

This sentence is not complete and it needs to accurately state (via RFC reference?) what the detailed encoding rules are

We determine from the code in the model compiler that the base64 string is created using the .NET Convert.ToBase64String method. Whatever standard this method uses needs to be spelled out in Annex E.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2014-10-09 05:36

administrator   ~0005534

Fixed paragraph.

Jim Luth

2014-10-16 11:30

administrator   ~0005562

Agreed to changes in Carros meeting.

Issue History

Date Modified Username Field Change
2014-05-06 17:49 Jim Luth New Issue
2014-05-06 17:49 Jim Luth Status new => assigned
2014-05-06 17:49 Jim Luth Assigned To => Randy Armstrong
2014-08-19 17:30 Jim Luth Category (No Category) => Spec
2014-08-19 17:30 Jim Luth Target Version => 1.03
2014-10-09 05:36 Randy Armstrong Note Added: 0005534
2014-10-09 05:36 Randy Armstrong Status assigned => resolved
2014-10-09 05:36 Randy Armstrong Resolution open => fixed
2014-10-16 11:30 Jim Luth Note Added: 0005562
2014-10-16 11:30 Jim Luth Status resolved => closed
2014-10-16 11:30 Jim Luth Fixed in Version => 1.03