[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: EDXL_DE discussion points
Discussion Items for tomorrow (er - later today): First, items open on the issues list, then: A. (Dave) Should Section 1.6 have references to ISO-8601 format for DateTime, ISO 3166-1 and 2 and UN/LOCODE used in the targetArea container element? B. (Dave) Update definition in <distributionType>: Could an update message only augment with additional information. I see this especially if a new <contentObject> was added or new elements were added to existing <namespacedXMLContent> and resent. SUGGESTION: (Michelle) Modify from "Updated information superseding a previous message" to "Updated information superseding or augmenting a previous message" C. (Dave) Every element with uses the type "list, value pair" would be more accurately stated as C1. List and associated Value(s). NOTE: Michelle took the initiative to just do this. Reverse if needful. C2. Definition of 1. This could read "The list, and associated value(s) is in the form NOTE: Michelle took the initiative to just do this. Reverse if needful. C3. Definition of 2. This could read "Multiple instances of the <valueListUrn>, and associated <value> (s) MAY occur within a single <container element>" NOTE: (Michelle) This is not what the schema says. There can only be one instance of a list and associated value(s) within a container element. However, there can be multiple container elements, each containing another list and associated value(s). D. (Dave) In Section 3.2.3: Should add a sentence "Additional elements (metadata) used for specific distribution of the <contentObject> payload or hints for processing the payload are also present in the <contentObject> container element." NOTE: Michelle took the initiative to just do this. She also altered the existing text to fit better with the Schema documentation. Reverse if needful. E. (Dave) Based on the definition above content description, size, digest elements are all specific to uri, and defRefUri and may be better in the choice. NOTE: Likely part of the Issue 3 discussion F. (Dave) Reopen <location> in <contentObject> discussion.