← Prev in month ← Prev in thread
Next in thread → Next in month →

4pm EDT - HAVE SC

From
Darrell O'Donnell <>
Date
2013-05-28T18:52:22+00:00
ID
CACeiFV=pDjJVCDBDg3h88++Y88BtuAMMeKBp=kRQhu=
Thread
4pm EDT - HAVE SC
Folks - I trust you had a great long weekend south of the border. I have made some good progress on the schema (attached) but I have two issues:

I am not quite done (more work than I had thought)

I have SVN problems locally so can't check the code in. I'll get that resolved pretty quickly though.

I look forward to discussing the changes that I have made to date (listed below). I will discuss the items that I am still working on as well.

cheers,

Darrell

NOTES FROM CHANGES/WORK IN PROGRESS:

QUESTIONS:

Why do we used EDXLStringType instead of the basic xs:string? What possible value does this add (i.e. changing something as fundamental as an xs:string would have wide impact upstream)? To me this looks like it is good where we have something that is really tokenized, but is it really a replacement for xs:string?

CHANGES:

moved Facility ID/ParentID to be an attribute of FacilityType (was FacilityType/information/facilityID… - too deep to be obvious or useful)

moved to FacilityType attribute (was FacilityType/information/facilityID and parentFacilityID )

used  xs:ID and xs:IDREF for facilityID and parentFacility

moved FacilityType/facilityKind to use a "kind" attribute of FacilityType. Updated FacilityKindType to be a restriction of EDXLStringType.

moved FacilityType/information/name to FacilityType/name (was ambiguous at that depth).

deleted FacilityType/information/facilityProfile - there was a note wondering if this was a HAVE 1.0 layover (wasn't) and it wasn't used.

moved FacilityType/information/facilityDetails to FacilityType/organizationInformation (other name didn't provide much in the way of telling the reader what it was).

created FacilityType/location element to hold location information (geospatial info)

removed (after above) FacilityType/information as it contained nothing of value other than geospatial, which has been moved up. This has reduced complexity and improved readability

renamed ResourceStatusType to ResourceInformationType - this name was ambiguous (contains status, and list of resource needs/offers).

moved ResourceInformationType/resources/resourcesInformationText up one level - was in wrong place.

ActivityInPeriodType - changed untyped counts to use xs:int (admissions, discharges, deaths)

FacilityType/activityInPeriod - changed cardinality from 0…1 to 0…n (may have multiple past reports depending on how the HAVE provider want's to report (e.g. daily, weekly, monthly - or all for longer-term trends.)

Attachment:
EDXL-HAVE-SC-SchemaDoc-2013-05-28.pdf

Description: Adobe PDF document

Attachment:
edxl-have-v2.0-wd.xsd

Description: Binary data
← Prev in month ← Prev in thread
Next in thread → Next in month →