EM Reference Information Model SC

Thanks Scott, As near as I can reconstruct it, about a year ago when I first started down the path of attempting to unify the EDXL Family, I somehow got it into my head that remarks were actually based on EDXLStringType. Perhaps that was due to the fact that EDXLStringType is used numerous times in EDXLSitRep-v1.0.xsd where remarks is also used a few times. Hence my concern with preserving whitespace. It wasn't until this morning as I went through my old materials that I figured that out. It was just one of those things that stuck in my head. My apologies to all. However, it does leave us with two elements that are essentially identical in structure and purpose. This begs the question of whether we should settle on one or explicitly make a difference between comment(s) and remarks. Cheers, Rex On 1/16/2018 10:06 PM, Scott M. Robertson wrote: Since I wasn't involved at the time, I am unclear on why there is a concern about preserving white space in comment(s) and remarks. By default, xs:string (the underlying basis for the comment and remarks elements in HAVE) preserve white space. Adding the whiteSpace attribute as preserve to xs:string doesn't do much as that is the default value for whiteSpace in xs:string. There are XML data types which do compact white space to different degrees: * xs:token - used by EDXLStringType and, by extension, ParameterValueType in extension.parameter.value; * xs:normalizedString - used extensively in xPIL, xNL, and xAL data types; * and other xs: data types which I did not find in the schema set. Maybe I am missing the point. Is there a concern that various comments will be stripped of white space? In HAVE, at least, that does not appear to be the case. -------- Scott M Robertson, PharmD, RPh, FHL7 Principal Technology Consultant Kaiser Permanente KP Health IT Strategy & Policy Pasadena / Torrance, CA 310-200-0231 (office) --------- kp.org/thrive <http://kp.org/thrive> NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 Virus-free. www.avast.com

Not entirely identical, depending on how finally resolve things. As included in edxl-have-v2.0.xsd comment is limited to 1024 while remarks has no limit, and that may be enough of a difference for general EDXL purposes. Cheers, Rex On 1/17/2018 9:47 AM, rexbroo wrote: Thanks Scott, As near as I can reconstruct it, about a year ago when I first started down the path of attempting to unify the EDXL Family, I somehow got it into my head that remarks were actually based on EDXLStringType. Perhaps that was due to the fact that EDXLStringType is used numerous times in EDXLSitRep-v1.0.xsd where remarks is also used a few times. Hence my concern with preserving whitespace. It wasn't until this morning as I went through my old materials that I figured that out. It was just one of those things that stuck in my head. My apologies to all. However, it does leave us with two elements that are essentially identical in structure and purpose. This begs the question of whether we should settle on one or explicitly make a difference between comment(s) and remarks. Cheers, Rex On 1/16/2018 10:06 PM, Scott M. Robertson wrote: Since I wasn't involved at the time, I am unclear on why there is a concern about preserving white space in comment(s) and remarks. By default, xs:string (the underlying basis for the comment and remarks elements in HAVE) preserve white space. Adding the whiteSpace attribute as preserve to xs:string doesn't do much as that is the default value for whiteSpace in xs:string. There are XML data types which do compact white space to different degrees: * xs:token - used by EDXLStringType and, by extension, ParameterValueType in extension.parameter.value; * xs:normalizedString - used extensively in xPIL, xNL, and xAL data types; * and other xs: data types which I did not find in the schema set. Maybe I am missing the point. Is there a concern that various comments will be stripped of white space? In HAVE, at least, that does not appear to be the case. -------- Scott M Robertson, PharmD, RPh, FHL7 Principal Technology Consultant Kaiser Permanente KP Health IT Strategy & Policy Pasadena / Torrance, CA 310-200-0231 (office) --------- kp.org/thrive <http://kp.org/thrive> NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 Virus-free. www.avast.com -- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670