DDEX Data Dictionary, 2020-07-30

A

B

C

D

E

F

G

H

I

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

All

Intro

ddexC:EventDate

A message term for mc-us-lod:LoDMessage, mc-us-lod:LoDConfirmationMessage.

A Composite containing details of the Date and Place of an Event.

Component Structure
Components	Name	Description of Element Role	Cardinality	Data Type
	IsApproximate	The Flag indicating whether the reported Date is approximate (=true) or exact (=false). This is represented in an XML schema as an XML Attribute.	0-1	Boolean (xs:boolean)
	IsBefore	The Flag indicating whether the Event being described occurred sometime before the reported Date (=true) or not (=false). This is represented in an XML schema as an XML Attribute.	0-1	Boolean (xs:boolean)
	IsAfter	The Flag indicating whether the Event being described occurred sometime after the reported Date (=true) or not (=false). This is represented in an XML schema as an XML Attribute.	0-1	Boolean (xs:boolean)
	ApplicableTerritoryCode	The Territory in which the Event occurred. This is represented in an XML schema as an XML Attribute. The use of ISO TerritoryCodes (or the term 'Worldwide') is strongly encouraged; TIS TerritoryCodes should only be used if both MessageSender and MessageRecipient are familiar with this standard.	0-1	avs:AllTerritoryCode
	LocationDescription	A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.	0-1	String (xs:string)
	LanguageAndScriptCode	The Language and script for the LocationDescription as defined in IETF RfC 5646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-script][-region][-variant]. This is represented in an XML schema as an XML Attribute.	0-1	String (xs:string)
Is Member of Composites	Composite Name	Description of Element Role	Cardinality	Label of Element in Composite	Further Reading
	mwnl:ConditionWithSupplementalDocument	The EffectiveTransferDate for which the Condition is valid.	1	EffectiveTransferDate
	ddexC:Period	A Composite containing details of the Date and Place of an Event that marks the beginning of the Period (in ISO 8601 format: YYYY-MM-DD). The StartDate must be no later than the EndDate if both are provided.	0-1	StartDate
	mc-notif:Release	A Composite containing details of the Date and Place of the Event in which the Release was or will be first made available for Usage in its current form, whether for physical or electronic/online distribution (in ISO 8601 format: YYYY[-MM[-DD]]).	0-1	ReleaseDate
	mc-us-lod:ReleaseForConfirmation	A Composite containing details of the Date and Place of the Event in which the Release was or will be first made available for Usage in its current form, whether for physical or electronic/online distribution (in ISO 8601 format: YYYY[-MM[-DD]]).	0-1	ReleaseDate
	ddexC:ValidityPeriod	A Composite containing details of the Date and Place of an Event that marks the beginning of the Period (in ISO 8601 format: YYYY-MM-DD). The StartDate must be no later than the EndDate if both are provided.	0-1	StartDate

Relationships
Has Components From	IsoDate	A Date represented in ISO 8601 format: YYYY[-MM[-DD]].

© 2006-2020 Digital Data Exchange, LLC (DDEX)