Quantcast
Channel: edxlsharp Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 20

Closed Issue: More tutorial documentation needed [15449]

$
0
0
I'm working with this library for the first time, and interested in TEP, but suspect that many of my questions will be of broad interest. Here's what I'd like to see at the outset, and didn't find in either source or binary distro:
 
- Example when reading data of handoff from EDXL wrapper parsing to specific library parsing (TEP in my case)
- Is there a function that will detect various objects (HAVE, TEP, non-standard) within the EDXL wrapper, and help route to the proper sub-parser?
- Are the given TEP enumerations normative, or merely examples, and if the latter, can I override them in some way short of changing the library source code?
- I'd like my outgoing TEP message to include the name of my app, not just your library. Any way to do this short of changing source code?
- Example of reading/writing ValueList items. How does SetContentKeywords help?
- Example of reading/writing GeoOASISWhere data, e.g., for TEP.Location. I'm particularly interested in pos data (latitude, longitude), but other examples of location specification would also be good.
- Can I get away with this (which compiles OK):
XElement insurance = XElement.Parse("insurance.xml");
tep.PatientInfo.InsuranceInfo.Add(insurance);
or do I have to do this:
ContentObject insobj = new ContentObject();
insobj.XMLContent = new XMLContentType();
XElement insurance = XElement.Parse("insurance.xml");
insobj.XMLContent.AddEmbeddedXML(insurance);
tep.PatientInfo.InsuranceInfo.Add(insobj);
- Examples of use of Validate, ValidateToSchema, SchemaErrorCallback, ToGeoRSS.

Viewing all articles
Browse latest Browse all 20

Trending Articles