NewsItem

Element information

Namespace: http://iptc.org/std/NewsML/2003-10-10/

Properties: Local, Qualified

Content

Sequence [1..1]
1. Comment [0..*]
2. Catalog [0..1]
3. Identification [1..1] Identification information for the NewsItem.
4. NewsManagement [1..1] Information relevant to the management of a NewsItem. Multiple StatusWillChange introduced in version 1.1
5. Choice [0..1]
  - NewsComponent
  - Update [1..*] A modification to an existing NewsItem. This can be an insertion, replacement or deletion. Note that the Update element cannot be used to modify the NewsManagement or Identification element, or any of their descendants. Modifications to these parts of the NewsItem can be made by issuing the NewsItem under the current revision number, with only the Identification and NewsManagement elements present. These will replace the previous Identification and NewsManagement elements in their totality.
  - TopicSet

Attributes

Name	Occ	Type	Description	Notes
Duid	[0..1]	xsd:ID	Duid is a "Document-unique Identifier". It must satisfy the rules for XML ID attributes: it must only contain name characters, and it must start with a name-start character (not a digit). Its value must be unique within any NewsML document. Every NewsML element type has Duid as an optional attribute. Combined with the Identifier element, providing a value for the Duid of any element in a NewsML document makes the element globally identifiable. The Identifier element gives global identification to the document, and the Duid provides local identification for the element within the document.	from group localid
Euid	[0..1]	xsd:string	Euid is an "Element-unique Identifier". Its value must be unique among elements of the same element-type and having the same parent element. Use of Euid attribute makes it possible to identify any NewsML element within the context of its local branch of the NewsML document tree. This makes it possible to copy, or include by reference, subtrees into new combinations in ways that would break the uniqueness of Duids (thereby forcing new Duids to be allocated), but still being able to retain the identity of each element. If Euids are maintained at every level, it is possible to identify, for example "The ContentItem whose Euid is abc within the NewsComponent whose Euid is def". Such identification patterns would be preserved even after "pruning and grafting" of subtrees.	from group localid
xml:lang	[0..1]	Anonymous

Used in

Anonymous type of element NewsML
Type NewsComponentType (Element NewsComponent)

Sample instance

<NewsItem>
   <Comment>string</Comment>
   <Catalog>
      <Resource>
         <Urn>string</Urn>
         <Url>string</Url>
         <DefaultVocabularyFor Context="string"/>
      </Resource>
      <TopicUse Topic="string" Context="string"/>
   </Catalog>
   <Identification>
      <NewsIdentifier>
         <ProviderId>string</ProviderId>
         <DateId>string</DateId>
         <NewsItemId>string</NewsItemId>
         <RevisionId>1</RevisionId>
         <PublicIdentifier>string</PublicIdentifier>
      </NewsIdentifier>
      <NameLabel>string</NameLabel>
      <DateLabel>string</DateLabel>
      <Label>
         <LabelType FormalName="string"/>
         <LabelText>string</LabelText>
      </Label>
   </Identification>
   <NewsManagement>
      <NewsItemType FormalName="string"/>
      <FirstCreated>string</FirstCreated>
      <ThisRevisionCreated>string</ThisRevisionCreated>
      <Status FormalName="string"/>
      <StatusWillChange>
         <FutureStatus FormalName="string"/>
         <DateAndTime>string</DateAndTime>
      </StatusWillChange>
      <Urgency FormalName="string"/>
      <RevisionHistory Href="string"/>
      <DerivedFrom>
         <Comment>string</Comment>
      </DerivedFrom>
      <AssociatedWith>
         <Comment>string</Comment>
      </AssociatedWith>
      <Instruction FormalName="string">
         <RevisionStatus>...
         </RevisionStatus>
      </Instruction>
      <Property FormalName="string">
         <Property FormalName="string">...
         </Property>
      </Property>
   </NewsManagement>
   <NewsComponent>
      <Comment>string</Comment>
      <Catalog>
         <Resource>...
         </Resource>
         <TopicUse Topic="string" Context="string"/>
      </Catalog>
      <TopicSet FormalName="string">
         <Comment>string</Comment>
         <Catalog>...
         </Catalog>
         <TopicSetRef>...
         </TopicSetRef>
         <Topic>...
         </Topic>
      </TopicSet>
      <Role FormalName="string"/>
      <BasisForChoice>string</BasisForChoice>
      <NewsLines>
         <HeadLine>Any text, intermingled with:...
         </HeadLine>
         <SubHeadLine>Any text, intermingled with:...
         </SubHeadLine>
      </NewsLines>
      <AdministrativeMetadata>
         <Catalog>...
         </Catalog>
         <FileName>string</FileName>
         <SystemIdentifier>string</SystemIdentifier>
         <Provider>...
         </Provider>
         <Creator>...
         </Creator>
         <Source>...
         </Source>
         <Contributor>...
         </Contributor>
         <Property FormalName="string">...
         </Property>
      </AdministrativeMetadata>
      <RightsMetadata>
         <Catalog>...
         </Catalog>
         <Copyright>...
         </Copyright>
         <UsageRights>...
         </UsageRights>
         <Property FormalName="string">...
         </Property>
      </RightsMetadata>
      <DescriptiveMetadata>
         <Catalog>...
         </Catalog>
         <Language FormalName="string"/>
         <Genre FormalName="string"/>
         <SubjectCode>...
         </SubjectCode>
         <OfInterestTo FormalName="string">...
         </OfInterestTo>
         <DateLineDate>string</DateLineDate>
         <Location>...
         </Location>
         <TopicOccurrence/>
         <Property FormalName="string">...
         </Property>
      </DescriptiveMetadata>
      <Metadata>
         <Catalog>...
         </Catalog>
         <MetadataType FormalName="string"/>
         <Property FormalName="string">...
         </Property>
      </Metadata>
      <NewsItem>
         <Comment>string</Comment>
         <Catalog>...
         </Catalog>
         <Identification>...
         </Identification>
         <NewsManagement>...
         </NewsManagement>
         <NewsComponent>...
         </NewsComponent>
      </NewsItem>
   </NewsComponent>
</NewsItem>