NewsMLv1.0.dtd 78 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578
  1. <!--
  2. ===========================================
  3. NewsML Document Type Definition Version 1.0
  4. ===========================================
  5. International Press Telecommunications Council
  6. 6 October 2000
  7. Copyright (c) IPTC, 2000
  8. All rights reserved
  9. NewsML is a trademark of IPTC
  10. ======================================
  11. DO NOT REMOVE THESE LICENCE CONDITIONS
  12. ======================================
  13. LICENCE OF THE IPTC NewsML TRADEMARK TO NON-MEMBERS OF THE IPTC
  14. Use of the IPTC trademark shall be licensed by the IPTC ("the Licensor") to a
  15. Non-Member ("the Licensee") in consideration of the following obligations
  16. undertaken by the Licensee under the terms of this contract.
  17. 1. The Licensee recognises the Licensor as the sole owner of the intellectual
  18. property protected by the trademark.
  19. 2. The Licensee recognises that the Licensor has the right to grant licenses
  20. of the intellectual property protected by the trademark and has agreed to
  21. grant such a licence to the Licensee in the terms set out in this contract.
  22. 3. The Licensee shall not during the subsistence of this contract or at any
  23. future time register to use in its own name as proprietor any of the
  24. intellectual property protected by the trademark.
  25. 4. The Licensee shall not claim any right title or interest in the
  26. intellectual property or any part of it save as is granted by this contract.
  27. 5. The Licensee shall immediately call to the attention of the Licensor the use
  28. of any part of the intellectual property by any third party or any activity
  29. of any third party which might in the opinion of the Licensee amount to
  30. infringement of the rights protected by the trademark.
  31. 6. The Licensee shall not assign the benefit of this contract or grant any
  32. sub-licence without the prior written consent of the Licensor.
  33. 7. Use of the IPTC trademark is licensed only to those Licensees who comply
  34. with the requirements of the official published description of NewsML.
  35. 8. The Licensee promises to respect the integrity and quality standard of the
  36. trademark and shall refrain from all acts and omissions which threaten the
  37. integrity of the trademark as a mark of quality.
  38. 9. The Licensee shall communicate immediately to the IPTC any instances of
  39. actual or suspected misuse or non-compliance with the official published
  40. description of NewsML which come to the attention of the Licensee.
  41. 10. The Licensee shall, at the request of the IPTC Management Committee acting
  42. unanimously, accede to any reasonable request of the IPTC to inspect the
  43. address of the Licensee to verify compliance and each Licensee shall afford
  44. to the IPTC such assistance as is requested by the IPTC in response to the
  45. latter's reasonable enquiries in instances of suspected non-compliance with
  46. the official published description of NewsML requirements.
  47. The Licensee shall from time to time provide the IPTC with the full address of
  48. its place of business and that place will be deemed the Licensee's address.
  49. The IPTC reserves the right to terminate the use of the trademark by the
  50. Licensee at any time without notice or without the need to give reasons to the
  51. Licensee for such termination.
  52. This contract shall be governed and construed in accordance with the laws of
  53. England and Wales whose courts shall be courts of competent jurisdiction.
  54. -->
  55. <!--
  56. ================
  57. NOTE ON SPELLING
  58. ================
  59. NewsML element and attribute names use US-English spellings. With this
  60. exception, this DTD and its accompanying specification use British English
  61. spellings.
  62. -->
  63. <!--
  64. =============================
  65. PARAMETER ENTITY DECLARATIONS
  66. =============================
  67. -->
  68. <!--
  69. ================================================================================
  70. Attribute sets
  71. ================================================================================
  72. -->
  73. <!--
  74. ================================== assignment ==================================
  75. AssignedBy
  76. ==========
  77. An identifier for the party assigning a piece of metadata. This can be a
  78. string that designates the party informally (for example, a person's name),
  79. or a pointer in the form a fragment identifier consisting of a # character
  80. followed by the Duid of a Topic corresponding to the party.
  81. Importance
  82. ==========
  83. An indication of the importance the party assigning a piece of metadata
  84. attaches to it. The value of the Importance attribute is a formal name for a
  85. level of importance. Its meaning and permitted values are determined by a
  86. controlled vocabulary.
  87. Confidence
  88. ==========
  89. An indication of the confidence with which a piece of metadata has been
  90. assigned. The value of the Confidence attribute is a formal name for a
  91. degree of confidence. Its meaning and permitted values are determined by a
  92. controlled vocabulary.
  93. HowPresent
  94. ==========
  95. An indication of the way in which a piece of metadata applies. The value of
  96. the HowPresent attribute is a formal name for the way the metadata applies.
  97. Its meaning and permitted values are determined by a controlled vocabulary.
  98. DateAndTime
  99. ===========
  100. The date and (optionally) time at which a piece of metadata was assigned.
  101. Uses the format CCYYMMDDTHHMMSS{+or-}HHMM (century, year, month, day, time
  102. separator, hours, minutes, seconds, timezone separator, hours, minutes). If
  103. only the Date is needed, then the substring from T onwards may be omitted.
  104. This is the Basic Format defined by ISO 8601. CCYY is a 4-digit year number.
  105. MM is a 2-digit month number. DD is a 2-digit day number. T is the letter 'T'.
  106. HH is a 2-digit hour number (using a 24-hour clock). MM is a 2 digit minute
  107. number. (Note that midnight may be represented as 2400 or 240000 on the date
  108. of the day that is ending, or as 0000 or 000000 on the date of the day that is
  109. beginning.)
  110. {+or-} is the '+' character or the '-' character, and the following HHMM are
  111. hours and minutes of offset from Universal Co-ordinated Time (UTC) as defined
  112. by ISO 8601. If the time is being expressed in UTC, then the timezone offset
  113. may be '+0000' or '-0000'. If the time is behind UTC, the timezone separator
  114. is '-'. If the time is ahead of UTC the timezone separator is '+'.
  115. Example: 10:27 p.m. in New York on 31 December 2000 would be expressed as
  116. "20001231T222700-0500" as New York is five hours behind UTC in winter.
  117. At the same moment in London, the date and time would be expressed as
  118. time would be expressed as "20010101T032700+0000" or as , "20010101T00+0000", as
  119. in London, it is now 3:27 a.m. on 1 January 2001. At the same moment in Paris,
  120. the date and time would be expressed as "20010101T042700+0100", as Paris is one
  121. hour ahead of UTC in winter, and it is now 4:27 a.m. on 1 January 2001.
  122. ================================================================================
  123. -->
  124. <!ENTITY % assignment " AssignedBy CDATA #IMPLIED
  125. Importance CDATA #IMPLIED
  126. Confidence CDATA #IMPLIED
  127. HowPresent CDATA #IMPLIED
  128. DateAndTime CDATA #IMPLIED">
  129. <!--
  130. ================================= formalname ===================================
  131. FormalName
  132. ==========
  133. A string of characters whose meaning is determined by a controlled vocabulary.
  134. Vocabulary
  135. ==========
  136. The Vocabulary attribute, if present, provides a pointer to a TopicSet which is
  137. the controlled vocabulary that can be used to resolve the meaning of the
  138. FormalName. The value of the Vocabulary attribute is an http URL or a NewsML
  139. URN, or the # character followed by the value of the Duid attribute of the a
  140. TopicSet in the current document.
  141. If there is no Vocabulary attribute, then the controlled vocabulary to be used
  142. is located by the following algorithm:
  143. - Proceed to the parent of the current element.
  144. - If it has a Catalog element as its immediate child, see whether that Catalog
  145. contains a Resource element whose DefaultVocabularyFor child contains an XPath
  146. pattern that is matched by the current element. If so, then the controlled
  147. vocabulary is the resource identified by that Resource element.
  148. - If the parent does not meet the above condition, proceed to its parent and
  149. check the same condition.
  150. - Continue until a vocabulary is found, or no further parent elements are
  151. available because the root element has been reached and it too fails to meet
  152. the condition.
  153. If there is no Vocabulary attribute and the above algorithm fails to identify
  154. a resource that serves as the controlled vocabulary, there is an error, which
  155. the NewsML system may signal to the user.
  156. The NewsML system may also signal an error if a vocabulary is successfully
  157. identified, but it contains no item that matches the value of the FormalName
  158. whose meaning is sought.
  159. Scheme
  160. ======
  161. The Scheme attribute, if present, serves to distinguish which of possibly
  162. multiple naming schemes in the controlled vocabulary is the one that governs
  163. this FormalName. For a match to be obtained within the controlled vocabulary,
  164. the rule is that the FormalName and the Scheme must both match. If there is
  165. no Scheme attribute on the current element, the match will be to an item in
  166. the vocabulary that has the current formal name and no scheme. If there is a
  167. Scheme attribute on the current element, then both the formal name and the
  168. scheme in the controlled vocabulary must match.
  169. ================================================================================
  170. -->
  171. <!ENTITY % formalname " FormalName CDATA #REQUIRED
  172. Vocabulary CDATA #IMPLIED
  173. Scheme CDATA #IMPLIED">
  174. <!--
  175. =================================== localid ====================================
  176. Duid
  177. ====
  178. Duid is a "Document-unique Identifier". It must satisfy the rules for XML ID
  179. attributes: it must only contain name characters, and it must start with a
  180. name-start character (not a digit). Its value must be unique within any NewsML
  181. document.
  182. Every NewsML element type has Duid as an optional attribute. Combined with the
  183. Identifier element, providing a value for the Duid of any element in a NewsML
  184. document makes the element globally identifiable. The Identifier element gives
  185. global identification to the document, and the Duid provides local
  186. identification for the element within the document.
  187. Euid
  188. ====
  189. Euid is an "Element-unique Identifier". Its value must be unique among elements
  190. of the same element-type and having the same parent element.
  191. Use of Euid attribute makes it possible to identify any NewsML element within
  192. the context of its local branch of the NewsML document tree. This makes it
  193. possible to copy, or include by reference, subtrees into new combinations in
  194. ways that would break the uniqueness of Duids (thereby forcing new Duids to be
  195. allocated), but still being able to retain the identity of each element. If
  196. Euids are maintained at every level, it is possible to identify, for example
  197. "The ContentItem whose Euid is abc within the NewsComponent whose Euid is def".
  198. Such identification patterns would be preserved even after "pruning and
  199. grafting" of subtrees.
  200. ================================================================================
  201. -->
  202. <!ENTITY % localid " Duid ID #IMPLIED
  203. Euid CDATA #IMPLIED">
  204. <!--
  205. ================================================================================
  206. Content Models
  207. ================================================================================
  208. -->
  209. <!--
  210. ===================================== data =====================================
  211. Where data is included, it may be directly in the form of a DataContent element,
  212. or in the form of DataContent wrapped in an Encoding element, or by reference
  213. through an Href attribute, in which case neither a DataContent nor an Encoding
  214. element will be present.
  215. ================================================================================
  216. -->
  217. <!ENTITY % data " (Encoding
  218. | DataContent )?">
  219. <!--
  220. ==================================== party =====================================
  221. Person, organisation or company playing a specific role in the
  222. news workflow. The role being played is determined by the parent element. More
  223. information about it can be provided in the optional Comment subelements.
  224. ================================================================================
  225. -->
  226. <!ENTITY % party " (Comment*
  227. , Party+ )">
  228. <!--
  229. =========================
  230. ELEMENT TYPE DECLARATIONS
  231. =========================
  232. -->
  233. <!--
  234. ============================ AdministrativeMetadata ============================
  235. Information about the provenance of a NewsComponent.
  236. ================================================================================
  237. -->
  238. <!ELEMENT AdministrativeMetadata (Catalog? , FileName? , SystemIdentifier? , Provider? , Creator? , Source* , Contributor* , Property* )>
  239. <!ATTLIST AdministrativeMetadata %localid; >
  240. <!--
  241. ================================ AssociatedWith ================================
  242. A reference to a NewsItem with which this one is associated (for example, a
  243. series of articles, or a collection of photos, of which it is a part). The
  244. NewsItem attribute identifies the relevant NewsItem. Its value can be an
  245. http URL or a NewsML URN as described in the comment to PublicIdentifier. The
  246. Comment can be used to indicate the nature of the association.
  247. ================================================================================
  248. -->
  249. <!ELEMENT AssociatedWith (Comment* )>
  250. <!ATTLIST AssociatedWith %localid;
  251. NewsItem CDATA #IMPLIED >
  252. <!--
  253. ================================ BasisForChoice ================================
  254. The content of this element is an XPath statement or element-type name
  255. identifying information within each NewsComponent or ContentItem that can be
  256. used as a basis for choice between equivalent NewsComponents or ContentItems.
  257. The root of the XPath corresponds to the NewsComponent or ContentItem itself.
  258. The optional Rank attribute allows providers to place a numerical order on the
  259. importance they think should be attached to the different bases for choice.
  260. Smaller numbers represent higher importance.
  261. ================================================================================
  262. -->
  263. <!ELEMENT BasisForChoice (#PCDATA )>
  264. <!ATTLIST BasisForChoice %localid;
  265. Rank CDATA #IMPLIED >
  266. <!--
  267. ==================================== ByLine ====================================
  268. A natural-language statement of the author/creator information.
  269. ================================================================================
  270. -->
  271. <!ELEMENT ByLine (#PCDATA | Origin )*>
  272. <!ATTLIST ByLine %localid;
  273. xml:lang CDATA #IMPLIED >
  274. <!--
  275. =================================== Catalog ====================================
  276. A container for Resource and TopicUse elements. Resource elements map URNs to
  277. URLs and indicate default vocabularies which apply to the formal names of
  278. certain elements within the subtree that begins with the immediate parent of
  279. the Catalog element. TopicUse elements indicate where in the NewsML document
  280. certain Topics are used. The optional Href attribute provides a pointer to
  281. a Catalog element elsewhere in this or another document. Its value consists of
  282. a # character followed by the value of the Duid attribute of the referenced
  283. Catalog element and preceded, if the referenced Catalog is not in the current
  284. document, by an http URL or a NewsML URN identifying the document or NewsItem
  285. in which the Catalog appears. If the Href attribute is present on a Catalog
  286. element, then that element should be empty. If it contains subelements, the
  287. NewsML system may signal an error.
  288. ================================================================================
  289. -->
  290. <!ELEMENT Catalog (Resource* , TopicUse* )>
  291. <!ATTLIST Catalog %localid;
  292. Href CDATA #IMPLIED >
  293. <!--
  294. =============================== Characteristics ================================
  295. Information about the physical characteristics of a ContentItem.
  296. ================================================================================
  297. -->
  298. <!ELEMENT Characteristics (SizeInBytes? , Property* )>
  299. <!ATTLIST Characteristics %localid; >
  300. <!--
  301. =================================== Comment ====================================
  302. A natural-language description of, or statement about, the current element. The
  303. optional TranslationOf attribute is a pointer to another Comment element, of
  304. which this one is a direct translation.
  305. ================================================================================
  306. -->
  307. <!ELEMENT Comment (#PCDATA )>
  308. <!ATTLIST Comment %localid;
  309. xml:lang CDATA #IMPLIED
  310. TranslationOf IDREF #IMPLIED >
  311. <!--
  312. ================================= ContentItem ==================================
  313. A news object that carries or identifies content intended for presentation to
  314. humans.
  315. ================================================================================
  316. -->
  317. <!ELEMENT ContentItem (Comment* , Catalog? , MediaType? , Format? , MimeType? , Notation? , Characteristics? , %data; )>
  318. <!ATTLIST ContentItem %localid;
  319. Href CDATA #IMPLIED >
  320. <!--
  321. ================================= Contributor ==================================
  322. An individual and/or company or organisation that modified or enhanced a news
  323. object after its creation.
  324. ================================================================================
  325. -->
  326. <!ELEMENT Contributor (%party; )>
  327. <!ATTLIST Contributor %localid; >
  328. <!--
  329. ================================== Copyright ===================================
  330. The copyright that pertains to a news object.
  331. ================================================================================
  332. -->
  333. <!ELEMENT Copyright (Comment* , CopyrightHolder , CopyrightDate )>
  334. <!ATTLIST Copyright %localid;
  335. %assignment; >
  336. <!--
  337. ================================ CopyrightDate =================================
  338. A natural-language statement of the copyright date.
  339. ================================================================================
  340. -->
  341. <!ELEMENT CopyrightDate (#PCDATA | Origin )*>
  342. <!ATTLIST CopyrightDate %localid;
  343. xml:lang CDATA #IMPLIED >
  344. <!--
  345. =============================== CopyrightHolder ================================
  346. A natural-language statement indicating who owns the copyright.
  347. ================================================================================
  348. -->
  349. <!ELEMENT CopyrightHolder (#PCDATA | Origin )*>
  350. <!ATTLIST CopyrightHolder %localid;
  351. xml:lang CDATA #IMPLIED >
  352. <!--
  353. ================================ CopyrightLine =================================
  354. A natural-language statement of the copyright information.
  355. ================================================================================
  356. -->
  357. <!ELEMENT CopyrightLine (#PCDATA | Origin )*>
  358. <!ATTLIST CopyrightLine %localid;
  359. xml:lang CDATA #IMPLIED >
  360. <!--
  361. =================================== Creator ====================================
  362. An individual and/or company or organisation that created a news object.
  363. ================================================================================
  364. -->
  365. <!ELEMENT Creator (%party; )>
  366. <!ATTLIST Creator %localid; >
  367. <!--
  368. ================================== CreditLine ==================================
  369. A natural-language statement of credit information.
  370. ================================================================================
  371. -->
  372. <!ELEMENT CreditLine (#PCDATA | Origin )*>
  373. <!ATTLIST CreditLine %localid;
  374. xml:lang CDATA #IMPLIED >
  375. <!--
  376. ================================= DataContent ==================================
  377. The data that carries the content of a ContentItem.
  378. ================================================================================
  379. -->
  380. <!ELEMENT DataContent ANY>
  381. <!ATTLIST DataContent %localid; >
  382. <!--
  383. ================================= DateAndTime ==================================
  384. A formal representation of a date and, optionally, time, expressed in ISO 8601
  385. Basic Format, as described in the comment to the DateAndTime attribute within
  386. the assignment ENTITY declaration above.
  387. ================================================================================
  388. -->
  389. <!ELEMENT DateAndTime (#PCDATA )>
  390. <!ATTLIST DateAndTime %localid; >
  391. <!--
  392. ==================================== DateId ====================================
  393. A date identifier of a NewsItem in short ISO 8601 Basic Format (CCYYMMDD), as
  394. described in the comment to the DateAndTime attribute within the assignment
  395. ENTITY declaration above. The DateId is part of the formal identification of the
  396. NewsItem, and must remain the same through successive revisions of the same
  397. NewsItem.
  398. ================================================================================
  399. -->
  400. <!ELEMENT DateId (#PCDATA )>
  401. <!--
  402. ================================== DateLabel ===================================
  403. A string representation of a date or date and time, used by human users to help
  404. identify a NewsItem.
  405. ================================================================================
  406. -->
  407. <!ELEMENT DateLabel (#PCDATA )>
  408. <!ATTLIST DateLabel %localid; >
  409. <!--
  410. =================================== DateLine ===================================
  411. A natural-language statement of the date and/or place of creation.
  412. ================================================================================
  413. -->
  414. <!ELEMENT DateLine (#PCDATA | Origin )*>
  415. <!ATTLIST DateLine %localid;
  416. xml:lang CDATA #IMPLIED >
  417. <!--
  418. ============================ DefaultVocabularyFor ==============================
  419. An indication that the parent Resource provides the default vocabulary that
  420. determines the meanings and permitted values of the data occurring in a
  421. particular part of a NewsML document subtree. The Context attribute is an
  422. XPath statement identifying the data to which the default vocabulary applies.
  423. The optional Scheme attribute identifies the relevant naming scheme if the
  424. Resource contains more than one naming scheme. If the Resource is a NewsML
  425. TopicSet, then the meaning of the data identified by the Context is provided
  426. by the Topic whose FormalName subelement matches that data. If the Resource is
  427. not a NewsML TopicSet, then the way in which it is interpreted in order to
  428. provide a meaning for the data is not defined by NewsML but by the authority
  429. that governs whatever format the Resource uses.
  430. Example:
  431. <DescriptiveMetadata>
  432. <Catalog>
  433. <Resource Duid="resource1">
  434. <Urn>urn:newsml:iptc.org:20001006:Ranking:1</Urn>
  435. <Url>www.iptc.com/vocabularies/iptc-rank.xml</Url>
  436. <DefaultVocabularyFor Context="@Confidence"/>
  437. <DefaultVocabularyFor Context="@Importance"/>
  438. </Resource>
  439. <Resource Duid="resource2">
  440. <Urn>urn:newsml:iptc.org:20001006:TopicTypes:1</Urn>
  441. <Url>www.iptc.com/vocabularies/iptc-topictype.xml</Url>
  442. <DefaultVocabularyFor Context="TopicType@FormalName"/>
  443. </Resource>
  444. </Catalog>
  445. <TopicSet>
  446. <Topic Duid="topic1">
  447. <TopicType FormalName="Person">
  448. <Description Variant="Name">Bill Clinton</Description>
  449. <Description Variant="Position">President of the USA</Description>
  450. </Topic>
  451. </TopicSet>
  452. <TopicOccurrence
  453. AssignedBy="Desk Editor"
  454. Confidence="High"
  455. HowPresent="principal subject"
  456. Topic="#topic1"/>
  457. </DescriptiveMetadata>
  458. ================================================================================
  459. -->
  460. <!ELEMENT DefaultVocabularyFor EMPTY>
  461. <!ATTLIST DefaultVocabularyFor %localid;
  462. Context CDATA #REQUIRED
  463. Scheme CDATA #IMPLIED >
  464. <!--
  465. ==================================== Delete ====================================
  466. An instruction to delete an element within a NewsItem. The NewsItem is
  467. the previous revision of the current one, and the element to be deleted is the
  468. one whose Duid value is equal to the value of the Delete element's DuidRef
  469. attribute.
  470. ================================================================================
  471. -->
  472. <!ELEMENT Delete EMPTY>
  473. <!ATTLIST Delete %localid;
  474. DuidRef CDATA #REQUIRED >
  475. <!--
  476. ================================= DerivedFrom ==================================
  477. A reference to an NewsItem from which this one is derived. The NewsItem attribute
  478. identifies the relevant NewsItem. Its value can be an http URL or a NewsML URN
  479. as described in the comment to PublicIdentifier.
  480. ================================================================================
  481. -->
  482. <!ELEMENT DerivedFrom (Comment* )>
  483. <!ATTLIST DerivedFrom %localid;
  484. NewsItem CDATA #IMPLIED >
  485. <!--
  486. ================================= Description ==================================
  487. A description that identifies a Topic, thereby indicating the meaning of a
  488. formal name associated with that Topic. The xml:lang attribute indicates what
  489. language the description is in. The optional Variant attribute allows multiple
  490. descriptions to be given in the same language, and meaningfully distinguished
  491. from one another.
  492. ================================================================================
  493. -->
  494. <!ELEMENT Description (#PCDATA )>
  495. <!ATTLIST Description %localid;
  496. xml:lang CDATA #IMPLIED
  497. Variant CDATA #IMPLIED >
  498. <!--
  499. ============================= DescriptiveMetadata ==============================
  500. Information describing the content of a NewsComponent.
  501. ================================================================================
  502. -->
  503. <!ELEMENT DescriptiveMetadata (Catalog? , Language* , Genre? , SubjectCode* , OfInterestTo* , TopicOccurrence* , Property* )>
  504. <!ATTLIST DescriptiveMetadata %localid;
  505. %assignment; >
  506. <!--
  507. =================================== Encoding ===================================
  508. The encoding of the data comprising the content of a ContentItem.
  509. ================================================================================
  510. -->
  511. <!ELEMENT Encoding %data;>
  512. <!ATTLIST Encoding %localid;
  513. Notation CDATA #REQUIRED >
  514. <!--
  515. =================================== EndDate ====================================
  516. A natural-language statement of the date at which specified usage rights come
  517. to an end.
  518. ================================================================================
  519. -->
  520. <!ELEMENT EndDate (#PCDATA | Origin )*>
  521. <!ATTLIST EndDate %localid;
  522. xml:lang CDATA #IMPLIED
  523. %assignment; >
  524. <!--
  525. =================================== FileName ===================================
  526. The suggested or actual storage file name for a NewsItem.
  527. ================================================================================
  528. -->
  529. <!ELEMENT FileName (#PCDATA )>
  530. <!ATTLIST FileName %localid; >
  531. <!--
  532. ================================= FirstCreated =================================
  533. The date and, optionally, time at which a NewsItem was first created, expressed
  534. in ISO 8601 Basic Format, as described in the comment to the DateAndTime
  535. attribute within the assignment ENTITY declaration above.
  536. ================================================================================
  537. -->
  538. <!ELEMENT FirstCreated (#PCDATA )>
  539. <!ATTLIST FirstCreated %localid; >
  540. <!--
  541. ================================= FormalName ===================================
  542. A string of characters whose meaning is determined by a naming scheme within a
  543. controlled vocabulary. The controlled vocabulary may (but is not required to)
  544. take the form of a NewsML TopicSet. The optional Scheme attribute determines
  545. which naming scheme applies, when several exist within the same controlled
  546. vocabulary.
  547. ================================================================================
  548. -->
  549. <!ELEMENT FormalName (#PCDATA )>
  550. <!ATTLIST FormalName %localid;
  551. Scheme CDATA #IMPLIED >
  552. <!--
  553. ==================================== Format ====================================
  554. An indication of the format of a ContentItem. The value of the FormalName
  555. attribute is a formal name for the Format. Its meaning and permitted values are
  556. determined by a controlled vocabulary as described in the comment to the
  557. formalname ENTITY declaration above.
  558. ================================================================================
  559. -->
  560. <!ELEMENT Format EMPTY>
  561. <!ATTLIST Format %localid;
  562. %formalname; >
  563. <!--
  564. ================================= FutureStatus =================================
  565. An indication of the status a NewsItem will have at a specified future date. The
  566. value of the FormalName attribute is a formal name for the FutureStatus. Its
  567. meaning is determined by a controlled vocabulary as described in the comment
  568. to the formalname ENTITY declaration above.
  569. ================================================================================
  570. -->
  571. <!ELEMENT FutureStatus EMPTY>
  572. <!ATTLIST FutureStatus %localid;
  573. %formalname; >
  574. <!--
  575. ==================================== Genre =====================================
  576. An indication of the Genre of a NewsComponent. The value of the FormalName
  577. attribute is a formal name for the Genre. Its meaning and permitted values are
  578. determined by a controlled vocabulary as described in the comment to the
  579. formalname ENTITY declaration above.
  580. ================================================================================
  581. -->
  582. <!ELEMENT Genre EMPTY>
  583. <!ATTLIST Genre %localid;
  584. %formalname;
  585. %assignment; >
  586. <!--
  587. ================================== Geography ===================================
  588. A natural-language statement of the geographical area or areas to which
  589. specified usage rights apply.
  590. ================================================================================
  591. -->
  592. <!ELEMENT Geography (#PCDATA | Origin )*>
  593. <!ATTLIST Geography %localid;
  594. xml:lang CDATA #IMPLIED
  595. %assignment; >
  596. <!--
  597. =================================== HeadLine ===================================
  598. A displayable headline.
  599. ================================================================================
  600. -->
  601. <!ELEMENT HeadLine (#PCDATA | Origin )*>
  602. <!ATTLIST HeadLine %localid;
  603. xml:lang CDATA #IMPLIED >
  604. <!--
  605. ================================ Identification ================================
  606. Identification information for the NewsItem.
  607. ================================================================================
  608. -->
  609. <!ELEMENT Identification (NewsIdentifier , NameLabel? , DateLabel? , Label* )>
  610. <!ATTLIST Identification %localid; >
  611. <!--
  612. ================================= InsertAfter ==================================
  613. An instruction to insert content after a designated element within a NewsItem.
  614. The content to be inserted is the content of the InsertAfter element. The
  615. NewsItem into which it is to be inserted is the previous revision of the current
  616. one, and the element after which it is to be inserted is the one whose Duid
  617. value is equal to the value of the InsertAfter element's DuidRef attribute.
  618. ================================================================================
  619. -->
  620. <!ELEMENT InsertAfter ANY>
  621. <!ATTLIST InsertAfter %localid;
  622. DuidRef CDATA #REQUIRED >
  623. <!--
  624. ================================= InsertBefore =================================
  625. An instruction to insert content before a designated element within a NewsItem.
  626. The content to be inserted is the content of the InsertBefore element. The
  627. NewsItem into which it is to be inserted is the previous revision of the current
  628. one, and the element before which it is to be inserted is the one whose Duid
  629. value is equal to the value of the InsertBefore element's DuidRef attribute.
  630. ================================================================================
  631. -->
  632. <!ELEMENT InsertBefore ANY>
  633. <!ATTLIST InsertBefore %localid;
  634. DuidRef CDATA #REQUIRED >
  635. <!--
  636. ================================= Instruction ==================================
  637. An instruction from a news provider to the recipient of a NewsItem. A special
  638. case of Instruction is an indication of the effect the current revision of a
  639. NewsItem has on the status of any previous revisions of the NewsItem that may
  640. still be on the recipient's system. In this case, it will contain one or more
  641. RevisionStatus elements. Otherwise, the value of the FormalName attribute is a
  642. formal name for the Instruction, and its meaning is determined by a controlled
  643. vocabulary as described in the comment to the formalname ENTITY declaration
  644. above.
  645. ================================================================================
  646. -->
  647. <!ELEMENT Instruction (RevisionStatus* )>
  648. <!ATTLIST Instruction %localid;
  649. %formalname; >
  650. <!--
  651. ================================= KeywordLine ==================================
  652. A displayable set of keywords relevant to a news object. This can be used by a
  653. NewsML system to assist manual or automated searches.
  654. ================================================================================
  655. -->
  656. <!ELEMENT KeywordLine (#PCDATA | Origin )*>
  657. <!ATTLIST KeywordLine %localid;
  658. xml:lang CDATA #IMPLIED >
  659. <!--
  660. ==================================== Label =====================================
  661. A human-readable label for a NewsItem.
  662. ================================================================================
  663. -->
  664. <!ELEMENT Label (LabelType , LabelText )>
  665. <!ATTLIST Label %localid; >
  666. <!--
  667. =================================== LabelText ==================================
  668. The text that constitutes a Label of a given LabelType.
  669. ================================================================================
  670. -->
  671. <!ELEMENT LabelText (#PCDATA )>
  672. <!ATTLIST LabelText %localid; >
  673. <!--
  674. ================================= LabelType ====================================
  675. A user-defined type of label. The value of the FormalName attribute is a formal
  676. name for the LabelType. Its meaning and permitted values are determined by a
  677. controlled vocabulary as described in the comment to the formalname ENTITY
  678. declaration above.
  679. ================================================================================
  680. -->
  681. <!ELEMENT LabelType EMPTY>
  682. <!ATTLIST LabelType %localid;
  683. %formalname; >
  684. <!--
  685. =================================== Language ===================================
  686. An indication of the, or a, language used in a content item. The value of the
  687. FormalName attribute is a formal name for the Language. Its meaning and
  688. permitted values are determined by a controlled vocabulary as described in the
  689. comment to the formalname ENTITY declaration above.
  690. ================================================================================
  691. -->
  692. <!ELEMENT Language EMPTY>
  693. <!ATTLIST Language %localid;
  694. %formalname;
  695. %assignment; >
  696. <!--
  697. ================================= Limitations ==================================
  698. A natural-language statement of the terms and conditions that apply to the
  699. specified usage rights.
  700. ================================================================================
  701. -->
  702. <!ELEMENT Limitations (#PCDATA | Origin )*>
  703. <!ATTLIST Limitations %localid;
  704. xml:lang CDATA #IMPLIED
  705. %assignment; >
  706. <!--
  707. ================================== MediaType ===================================
  708. An indication of the media type of a ContentItem. The value of the FormalName
  709. attribute is a formal name for the MediaType. Its meaning and permitted values
  710. are determined by a controlled vocabulary as described in the comment to the
  711. formalname ENTITY declaration above.
  712. ================================================================================
  713. -->
  714. <!ELEMENT MediaType EMPTY>
  715. <!ATTLIST MediaType %localid;
  716. %formalname; >
  717. <!--
  718. =================================== Metadata ===================================
  719. An container for a user-defined type of metadata.
  720. ================================================================================
  721. -->
  722. <!ELEMENT Metadata (Catalog? , MetadataType , Property+ )>
  723. <!ATTLIST Metadata %localid; >
  724. <!--
  725. =============================== MetadataType ===================================
  726. An indication of the type of metadata that is represented by the Property
  727. elements within this Metadata element. The value of the FormalName attribute is
  728. a formal name for the MetadataType. Its meaning and permitted values are
  729. determined by a controlled vocabulary as described in the comment to the
  730. formalname ENTITY declaration above.
  731. ================================================================================
  732. -->
  733. <!ELEMENT MetadataType EMPTY>
  734. <!ATTLIST MetadataType %localid;
  735. %formalname; >
  736. <!--
  737. =================================== MimeType ===================================
  738. An indication of the MIME-type of a ContentItem. The value of the FormalName
  739. attribute is a formal name for the MimeType. Its meaning and permitted values
  740. are determined by a controlled vocabulary as described in the comment to the
  741. formalname ENTITY declaration above.
  742. ================================================================================
  743. -->
  744. <!ELEMENT MimeType EMPTY>
  745. <!ATTLIST MimeType %localid;
  746. %formalname; >
  747. <!--
  748. ================================== NameLabel ===================================
  749. A string used by human users as a name to help identify a NewsItem. Its form is
  750. determined by the provider. It might be identical to the textual content of
  751. the SlugLine element, for example, but even if this is so, the system should not
  752. process the NameLabel as a slugline. Nothing can be assumed about the nature of
  753. the string within NameLabel beyond the fact that it can help to identify the
  754. NewsItem to humans.
  755. ================================================================================
  756. -->
  757. <!ELEMENT NameLabel (#PCDATA )>
  758. <!ATTLIST NameLabel %localid; >
  759. <!--
  760. ================================ NewsComponent =================================
  761. A container for news objects, used to identify the role of news objects in
  762. relation to one another, and to ascribe metadata to them. The Essential
  763. attribute indicates whether the provider considers that this NewsComponent
  764. is essential to the meaning of the NewsComponent within which it is contained.
  765. The EquivalentsList attribute indicates whether or not the NewsItems or
  766. NewsItemRefs, NewsComponents or ContentItems contained within this one are
  767. equivalent to one another in content and/or meaning
  768. ================================================================================
  769. -->
  770. <!ELEMENT NewsComponent (Comment* , Catalog? , TopicSet* , Role? , BasisForChoice* , NewsLines? , AdministrativeMetadata? , RightsMetadata? , DescriptiveMetadata? , Metadata* , ( (NewsItem | NewsItemRef )+ | NewsComponent+ | ContentItem+ )? )>
  771. <!ATTLIST NewsComponent %localid;
  772. Essential (yes | no ) 'no'
  773. EquivalentsList (yes | no ) 'no'
  774. xml:lang CDATA #IMPLIED >
  775. <!--
  776. ================================= NewsEnvelope =================================
  777. Information about the transmission of one or more NewsItems as a NewsML
  778. document.
  779. ================================================================================
  780. -->
  781. <!ELEMENT NewsEnvelope (TransmissionId? , SentFrom? , SentTo? , DateAndTime , NewsService* , NewsProduct* , Priority? )>
  782. <!ATTLIST NewsEnvelope %localid; >
  783. <!--
  784. ================================ NewsIdentifier ================================
  785. A globally unique identifier for a NewsItem.
  786. ================================================================================
  787. -->
  788. <!ELEMENT NewsIdentifier (ProviderId , DateId , NewsItemId , RevisionId , PublicIdentifier )>
  789. <!--
  790. =================================== NewsItem ===================================
  791. A managed set of information representing a point of view, at a given time, on
  792. some event or events. Its Identification and NewsManagement provide
  793. manageability. It may contain either a NewsComponent, or one or more Updates
  794. that modify aspects of a previous Revision of the same NewsItem, or a
  795. TopicSet.
  796. ================================================================================
  797. -->
  798. <!ELEMENT NewsItem (Comment* , Catalog? , Identification , NewsManagement , (NewsComponent | Update+ | TopicSet )? )>
  799. <!ATTLIST NewsItem %localid;
  800. xml:lang CDATA #IMPLIED >
  801. <!--
  802. ================================== NewsItemId ==================================
  803. An identifier for the NewsItem. The combination of NewsItemId and DateId must
  804. be unique among NewsItems that emanate from the same provider. Within these
  805. constraints, the NewsItemId can take any form the provider wishes. It may take
  806. the form of a name for the NewsItem that will be meaningful to humans, but this
  807. is not a requirement. The provider may optionally relate the values of
  808. NewsItemId to a controlled vocabulary, which is invoked by the Vocabulary
  809. attribute. The value ofthe Vocabulary attribute may be an http URL, a NewsML
  810. URN, or the # character followed by the value of the Duid attribute of a
  811. TopicSet in the current document. The Scheme attribute, if present, serves to
  812. distinguish which of possibly multiple naming schemes in the controlled
  813. vocabulary is the one that governs the NewsItemId.
  814. ================================================================================
  815. -->
  816. <!ELEMENT NewsItemId (#PCDATA )>
  817. <!ATTLIST NewsItemId Vocabulary CDATA #IMPLIED
  818. Scheme CDATA #IMPLIED >
  819. <!--
  820. ================================= NewsItemRef ==================================
  821. A pointer to a NewsItem that is deemed to replace the NewsItemRef element. The
  822. NewsItem attribute is a pointer to the relevant NewsItem. Its value can be an
  823. http URL, or a NewsML URN as described in the comment to PublicIdentifier, or a
  824. fragment identifier consisting of a # character followed by the Duid of a
  825. NewsItem in the current document.
  826. ================================================================================
  827. -->
  828. <!ELEMENT NewsItemRef (Comment* )>
  829. <!ATTLIST NewsItemRef %localid;
  830. NewsItem CDATA #IMPLIED >
  831. <!--
  832. ================================= NewsItemType =================================
  833. An indication of the type of a NewsItem. The value of the FormalName attribute
  834. is a formal name for the NewsItemType. Its meaning and permitted values are
  835. determined by a controlled vocabulary as described in the comment to the
  836. formalname ENTITY declaration above.
  837. ================================================================================
  838. -->
  839. <!ELEMENT NewsItemType EMPTY>
  840. <!ATTLIST NewsItemType %localid;
  841. %formalname; >
  842. <!--
  843. =================================== NewsLine ===================================
  844. A newsline of a type not included in the NewsML specification.
  845. ================================================================================
  846. -->
  847. <!ELEMENT NewsLine (NewsLineType , NewsLineText+ )>
  848. <!ATTLIST NewsLine %localid; >
  849. <!--
  850. =================================== NewsLineText ===================================
  851. The text of a NewsLine of user-defined type.
  852. ================================================================================
  853. -->
  854. <!ELEMENT NewsLineText (#PCDATA | Origin )*>
  855. <!ATTLIST NewsLineText %localid;
  856. xml:lang CDATA #IMPLIED >
  857. <!--
  858. ================================ NewsLineType ==================================
  859. An indication of a user-defined NewsLine type. The value of the FormalName
  860. attribute is a formal name for the NewsLineType. Its meaning and permitted
  861. values are determined by a controlled vocabulary as described in the comment
  862. to the formalname ENTITY declaration above.
  863. ================================================================================
  864. -->
  865. <!ELEMENT NewsLineType EMPTY>
  866. <!ATTLIST NewsLineType %localid;
  867. %formalname; >
  868. <!--
  869. ================================== NewsLines ===================================
  870. A container for all the NewsLines that a NewsComponent has.
  871. ================================================================================
  872. -->
  873. <!ELEMENT NewsLines ( (HeadLine , SubHeadLine? )* , ByLine* , DateLine* , CreditLine* , CopyrightLine* , RightsLine* , SeriesLine* , SlugLine* , KeywordLine* , NewsLine* )>
  874. <!ATTLIST NewsLines %localid; >
  875. <!--
  876. ================================ NewsManagement ================================
  877. Information relevant to the management of a NewsItem.
  878. ================================================================================
  879. -->
  880. <!ELEMENT NewsManagement (NewsItemType , FirstCreated , ThisRevisionCreated , Status , StatusWillChange? , Urgency? , RevisionHistory? , DerivedFrom* , AssociatedWith* , Instruction* , Property* )>
  881. <!ATTLIST NewsManagement %localid; >
  882. <!--
  883. ==================================== NewsML ====================================
  884. A NewsML document, which must contain a NewsEnvelope and one or more NewsItems,
  885. and may include a Catalog element and a TopicSet element.
  886. ================================================================================
  887. -->
  888. <!ELEMENT NewsML (Catalog? , TopicSet* , (NewsEnvelope , NewsItem+ ) )>
  889. <!ATTLIST NewsML %localid; >
  890. <!--
  891. ================================= NewsProduct ==================================
  892. An identifier for a product to which all the NewsItems in a NewsML document
  893. belong. The value of the FormalName attribute is a formal name for the
  894. NewsProduct. Its meaning and permitted values are determined by a controlled
  895. vocabulary as described in the comment to the formalname ENTITY declaration
  896. above.
  897. ================================================================================
  898. -->
  899. <!ELEMENT NewsProduct EMPTY>
  900. <!ATTLIST NewsProduct %localid;
  901. %formalname; >
  902. <!--
  903. ================================= NewsService ==================================
  904. An identifier for a service to which all the NewsItems in a NewsML document
  905. belong. The value of the FormalName attribute is a formal name for the
  906. NewsService. Its meaning and permitted values are determined by a controlled
  907. vocabulary as described in the comment to the formalname ENTITY declaration
  908. above.
  909. ================================================================================
  910. -->
  911. <!ELEMENT NewsService EMPTY>
  912. <!ATTLIST NewsService %localid;
  913. %formalname; >
  914. <!--
  915. =================================== Notation ===================================
  916. An indication of the notation of a ContentItem. The value of the FormalName
  917. attribute is a formal name for the Notation. Its meaning and permitted values
  918. are determined by a controlled vocabulary as described in the comment to the
  919. formalname ENTITY declaration above.
  920. ================================================================================
  921. -->
  922. <!ELEMENT Notation EMPTY>
  923. <!ATTLIST Notation %localid;
  924. %formalname; >
  925. <!--
  926. ================================= OfInterestTo =================================
  927. An indication of the target audience of a NewsItem. The value of the FormalName
  928. attribute is a formal name for the target audience. Its meaning and permitted
  929. values are determined by a controlled vocabulary as described in the comment to
  930. the formalname ENTITY declaration above.
  931. ================================================================================
  932. -->
  933. <!ELEMENT OfInterestTo (Relevance? )>
  934. <!ATTLIST OfInterestTo %localid;
  935. %formalname;
  936. %assignment; >
  937. <!--
  938. ==================================== Origin ====================================
  939. A wrapper for all or part of the text of a piece of text, which provides a
  940. pointer to an item of data corresponding formally to what is being described
  941. here in natural language. The Href attribute identifies the relevant data, and
  942. may be an http URL or a NewsML URN as described in the comment to
  943. PublicIdentifier, optionally including a fragment identifier. Alternatively, it
  944. can be a simple fragment identifier consisting of a # character followed by the
  945. value of the Duid of an element in the current document.
  946. ================================================================================
  947. -->
  948. <!ELEMENT Origin (#PCDATA | Origin )*>
  949. <!ATTLIST Origin %localid;
  950. %assignment;
  951. Href CDATA #IMPLIED >
  952. <!--
  953. =================================== Party ======================================
  954. An indication of the person, company or organisation that has a particular
  955. relationship to this NewsItem in the news workflow. The value of the FormalName
  956. attribute is a formal name for the Party. Its meaning and permitted values
  957. are determined by a controlled vocabulary as described in the comment to the
  958. formalname ENTITY declaration above.
  959. ================================================================================
  960. -->
  961. <!ELEMENT Party EMPTY>
  962. <!ATTLIST Party %localid;
  963. %formalname;
  964. Topic CDATA #IMPLIED >
  965. <!--
  966. =================================== Priority ===================================
  967. An indication of the priority notation of a NewsItem. The value of the
  968. FormalName attribute is a formal name for the Priority. Its meaning and
  969. permitted values are determined by a controlled vocabulary as described in
  970. the comment to the formalname ENTITY declaration above.
  971. ================================================================================
  972. -->
  973. <!ELEMENT Priority EMPTY>
  974. <!ATTLIST Priority %localid;
  975. %formalname; >
  976. <!--
  977. =================================== Property ===================================
  978. A property of a NewsComponent or of a Topic. The property has a name and either
  979. a simple Value or a complex value consisting of a set of further properties.
  980. Value
  981. =====
  982. A string representation of the value of a Property.
  983. ValueRef
  984. ========
  985. A pointer to the value of the Property. This might be a Topic in a TopicSet, or
  986. any other piece of data. If both Value and ValueRef are provided, then ValueRef
  987. identifies the actual value of the property, with Value simply providing a
  988. string representation or mnemonic for it.
  989. Example:
  990. <Catalog>
  991. <Resource Duid="resource1">
  992. <Urn>urn:newsml:reuters.com:20001001:Physical Characteristics:3</Urn>
  993. <Url>www.reuters.com/vocabs/physical.xml</Url>
  994. <Url>www.iptc.com/vocabularies/memberdefined/reuters/physical.xml</Url>
  995. <DefaultVocabularyFor Scheme="short" Context="Metadata/Property[@FormalName='Width']"/>
  996. </Resource>
  997. </Catalog>
  998. <Property FormalName="Width" Vocabulary="#resource1">
  999. <Property FormalName="Unit" ValueRef="urn:newsml:iptc.org:20001006:units:1#cm"/>
  1000. <Property FormalName="Quantity" Value="7.5"/>
  1001. </Property>
  1002. AllowedValues
  1003. =============
  1004. The AllowedValues attribute, if present, is a pointer to a controlled vocabulary
  1005. that delimits the set of allowed values for the property. This may be an http
  1006. URL, or a NewsML URN, or a fragment identifier consisting of a # charactger
  1007. followed by the Duid of an element in the current document. The pointer must
  1008. reference either a Resource element that designates an external controlled
  1009. vocabulary, or a TopicSet element, that is itself the controlled vocabulary.
  1010. ================================================================================
  1011. -->
  1012. <!ELEMENT Property (Property* )>
  1013. <!ATTLIST Property %localid;
  1014. %formalname;
  1015. %assignment;
  1016. Value CDATA #IMPLIED
  1017. ValueRef CDATA #IMPLIED
  1018. AllowedValues CDATA #IMPLIED >
  1019. <!--
  1020. =================================== Provider ===================================
  1021. An individual and/or company or organisation that released a news object for
  1022. publication.
  1023. ================================================================================
  1024. -->
  1025. <!ELEMENT Provider (%party; )>
  1026. <!ATTLIST Provider %localid; >
  1027. <!--
  1028. ================================== ProviderId ==================================
  1029. An identifier for the news provider that produced the NewsItem. The
  1030. provider's ID is specified in the element content. This should be an Internet
  1031. domain name that is owned by the provider at the date identified by the DateId
  1032. subelement of the NewsIdentifier, or the name for the Provider drawn from a
  1033. controlled vocabulary identified by a URN specified in the Vocabulary attribute.
  1034. This will ensure that the identity of the provider can be inferred unambiguously
  1035. from the full NewsIdentifier.
  1036. Example:
  1037. <NewsIdentifier>
  1038. <ProviderId>iptc.org</ProviderId>
  1039. <DateId>20001001</DateId>
  1040. <NewsItemId>NewsML version 1.0</NewsItemId>
  1041. <RevisionId>1</RevisionId
  1042. </NewsIdentifier>
  1043. Because the domain name "iptc.org" was owned on 1 October 2000 by the
  1044. International Press Telecommunications Council (IPTC) and no-one else, it is
  1045. certain that IPTC is the provider in this case.
  1046. ================================================================================
  1047. -->
  1048. <!ELEMENT ProviderId (#PCDATA )>
  1049. <!ATTLIST ProviderId Vocabulary CDATA #IMPLIED >
  1050. <!--
  1051. =============================== PublicIdentifier ===============================
  1052. A public identifier (in the sense defined by the XML 1,0 Specification) for a
  1053. NewsItem. This is the NewsML URN, and must be constructed as follows:
  1054. If the ProviderId is a domain name
  1055. urn:newsml:{ProviderId}:{DateId}:{NewsItemId}:{RevisionId}{RevisionId@Update}
  1056. If the ProviderId is name drawn from a controlled vocabulary
  1057. urn:newsml:|{ProviderId@Vocabulary}|{ProviderId}|:{DateId}:{NewsItemId}:{RevisionId}{RevisionId@Update}
  1058. where {x} means "the content of the x subelement of the NewsIdentifier" and
  1059. {x@y} means "the value of the y attribute of the x subelement of the
  1060. NewsIdentifier", with the exception that if the Update attribute of the
  1061. RevisionId element has its default value of N, it is omitted from the URN, and
  1062. that the Vocabulary attribute of the ProviderId element is stripped of the
  1063. substring "urn:" with which it begins. The Vocabulary attribute of ProviderId
  1064. necessarily begins with the characters "urn:" because, as stated in the
  1065. comment to the ProviderId element above, it must take the form of a URN
  1066. identifying a controlled vocabulary.
  1067. Note that the existence of this URN enables the NewsItem to be referenced
  1068. unambiguously by pointers from other XML elements or resources. Within such
  1069. pointers, if the RevisionId, its preceding : character and its following Update
  1070. qualifier are omitted, then the pointer designates the most recent revision at
  1071. the time it is resolved.
  1072. ================================================================================
  1073. -->
  1074. <!ELEMENT PublicIdentifier (#PCDATA )>
  1075. <!--
  1076. ================================== Relevance ===================================
  1077. An indication of the relevance of a NewsItem to a given target audience. The
  1078. value of the FormalName attribute is a formal name for the Relevance. Its
  1079. meaning and permitted values are determined by a controlled vocabulary as
  1080. described in the comment to the formalname ENTITY declaration above.
  1081. ================================================================================
  1082. -->
  1083. <!ELEMENT Relevance EMPTY>
  1084. <!ATTLIST Relevance %localid;
  1085. %formalname;
  1086. %assignment; >
  1087. <!--
  1088. =================================== Replace ====================================
  1089. An instruction to replace a designated element within a NewsItem. The element
  1090. that is to replace the designated element is the content of the Replace element.
  1091. The NewsItem within which the replacement takes place is the previous revision
  1092. of the current one, and the element to be replaced is the one whose Duid
  1093. value is equal to the value of the Replace element's DuidRef attribute.
  1094. ================================================================================
  1095. -->
  1096. <!ELEMENT Replace ANY>
  1097. <!ATTLIST Replace %localid;
  1098. DuidRef CDATA #REQUIRED >
  1099. <!--
  1100. ================================== Resource ====================================
  1101. An indication where a given resource can be found, and whether it is to be used
  1102. as the default vocabulary for certain formal names within the current subtree
  1103. of a NewsML document. The Urn attribute provides a NewsML URN for the resource.
  1104. THe Url attribute(s) provide(s) a location or locations where the resource may
  1105. be found. The DefaultVocabularyFor element contains an XPath pattern. The
  1106. identified resource acts as default vocabulary for any element within the
  1107. subtree whose root is the parent of the current Catalog, that matches this XPath
  1108. pattern.
  1109. ================================================================================
  1110. -->
  1111. <!ELEMENT Resource (Urn? , Url* , DefaultVocabularyFor* )>
  1112. <!ATTLIST Resource %localid; >
  1113. <!--
  1114. =============================== RevisionHistory ================================
  1115. A pointer to a file containing the revision history of the NewsItem.
  1116. ================================================================================
  1117. -->
  1118. <!ELEMENT RevisionHistory EMPTY>
  1119. <!ATTLIST RevisionHistory %localid;
  1120. Href CDATA #REQUIRED >
  1121. <!--
  1122. ================================== RevisionId ==================================
  1123. A positive integer indicating which Revision of a given NewsItem this is. Any
  1124. positive integer may be used, but it must always be the case that of two
  1125. instances of a NewsItem that have the same ProviderId, DateId and NewsItemId,
  1126. the one whose RevisionId has the larger value must be the more recent revision.
  1127. A RevisionId of 0 is not permitted. The PreviousRevision attribute must be
  1128. present, and its value must be equal to the content of the RevisionId element
  1129. of the NewsItem's previous revision, if there is one, and 0 if the NewsItem has
  1130. no previous revision. If the NewsItem contains an Update element or elements,
  1131. then the Update attribute must be set to U. If the NewsItem consists only of a
  1132. replacement set of NewsManagement data, then the Update attribute must be set
  1133. to A. If neither of these is the case, then the Update attribute must be set
  1134. to N.
  1135. ================================================================================
  1136. -->
  1137. <!ELEMENT RevisionId (#PCDATA )>
  1138. <!ATTLIST RevisionId PreviousRevision CDATA #REQUIRED
  1139. Update CDATA #REQUIRED >
  1140. <!--
  1141. ================================ RevisionStatus ================================
  1142. Indicates the status that previous revisions now has as a result of the release
  1143. of the current revision. The optional Revision attribute is an integer, equal to
  1144. the RevisionId of the revision in question. If it is not present, then the
  1145. status applies to ALL previous revisions, without exception.
  1146. ================================================================================
  1147. -->
  1148. <!ELEMENT RevisionStatus (Status )>
  1149. <!ATTLIST RevisionStatus %localid;
  1150. Revision CDATA #IMPLIED >
  1151. <!--
  1152. ================================= RightsHolder =================================
  1153. A string of text indicating who has the usage rights, optionally enriched with
  1154. pointers to further information about the relevant people, companies or
  1155. organisations.
  1156. ================================================================================
  1157. -->
  1158. <!ELEMENT RightsHolder (#PCDATA | Origin )*>
  1159. <!ATTLIST RightsHolder %localid;
  1160. xml:lang CDATA #IMPLIED
  1161. %assignment; >
  1162. <!--
  1163. ================================== RightsLine ==================================
  1164. A displayable version of rights information. Note that this is distinct from
  1165. copyright information. Copyright information is about who owns a news object;
  1166. rights information is about who is allowed to use it, in what way and under
  1167. what circumstances.
  1168. ================================================================================
  1169. -->
  1170. <!ELEMENT RightsLine (#PCDATA | Origin )*>
  1171. <!ATTLIST RightsLine %localid;
  1172. xml:lang CDATA #IMPLIED >
  1173. <!--
  1174. ================================ RightsMetadata ================================
  1175. Information about the rights pertaining to a NewsComponent.
  1176. ================================================================================
  1177. -->
  1178. <!ELEMENT RightsMetadata (Catalog? , Copyright* , UsageRights* , Property* )>
  1179. <!ATTLIST RightsMetadata %localid;
  1180. %assignment; >
  1181. <!--
  1182. ===================================== Role =====================================
  1183. An identifier of the role played by a NewsComponent within a NewsComponent
  1184. that contains it. The outermost NewsComponent within a NewsItem need not
  1185. specify a Role attribute value. The value of the FormalName attribute is a
  1186. formal name for the Role. Its meaning and permitted values are determined by
  1187. a controlled vocabulary as described in the comment to the formalname ENTITY
  1188. declaration above.
  1189. ================================================================================
  1190. -->
  1191. <!ELEMENT Role EMPTY>
  1192. <!ATTLIST Role %localid;
  1193. %formalname; >
  1194. <!--
  1195. =================================== SentFrom ===================================
  1196. An individual and/or company or organisation from whom the NewsML document is
  1197. being sent.
  1198. ================================================================================
  1199. -->
  1200. <!ELEMENT SentFrom (%party; )>
  1201. <!ATTLIST SentFrom %localid; >
  1202. <!--
  1203. ==================================== SentTo ====================================
  1204. An individual and/or company or organisation to whom the NewsML document is
  1205. being sent.
  1206. ================================================================================
  1207. -->
  1208. <!ELEMENT SentTo (%party; )>
  1209. <!ATTLIST SentTo %localid; >
  1210. <!--
  1211. ================================== SeriesLine ==================================
  1212. A displayable version of information about a news object's place in a series.
  1213. ================================================================================
  1214. -->
  1215. <!ELEMENT SeriesLine (#PCDATA | Origin )*>
  1216. <!ATTLIST SeriesLine %localid;
  1217. xml:lang CDATA #IMPLIED >
  1218. <!--
  1219. ================================== SizeInBytes =================================
  1220. The exact size in bytes of a ContentItem's inline or referenced data object.
  1221. ================================================================================
  1222. -->
  1223. <!ELEMENT SizeInBytes (#PCDATA )>
  1224. <!ATTLIST SizeInBytes %localid; >
  1225. <!--
  1226. =================================== SlugLine ===================================
  1227. A string of text, possibly embellished by hyperlinks and/or formatting, used to
  1228. display a NewsItem's slug line. (Note that the meaning of the term "slug line",
  1229. and the uses to which it is put, are a matter for individual providers to
  1230. define within their own workflow and business practice.)
  1231. ================================================================================
  1232. -->
  1233. <!ELEMENT SlugLine (#PCDATA | Origin )*>
  1234. <!ATTLIST SlugLine %localid;
  1235. xml:lang CDATA #IMPLIED >
  1236. <!--
  1237. ==================================== Source ====================================
  1238. An individual and/or company or organisation that provided source material for
  1239. a news object. The optional NewsItem attribute must be present in the case of
  1240. a syndicated NewsItem. It provides the URN of the NewsItem that is being
  1241. syndicated. Note that a sequence of Source elements can be used to indicate the
  1242. sequence of syndicators through which a NewsItem has passed.
  1243. ================================================================================
  1244. -->
  1245. <!ELEMENT Source (%party; )>
  1246. <!ATTLIST Source %localid;
  1247. NewsItem CDATA #IMPLIED >
  1248. <!--
  1249. ================================== StartDate ===================================
  1250. A natural-language statement of the date at which specified usage rights come
  1251. into effect.
  1252. ================================================================================
  1253. -->
  1254. <!ELEMENT StartDate (#PCDATA | Origin )*>
  1255. <!ATTLIST StartDate %localid;
  1256. xml:lang CDATA #IMPLIED
  1257. %assignment; >
  1258. <!--
  1259. ==================================== Status ===================================
  1260. An indication of the Status of a NewsItem. The value of the FormalName
  1261. attribute is a formal name for the Status. Its meaning and permitted values
  1262. are determined by a controlled vocabulary as described in the comment to the
  1263. formalname ENTITY declaration above.
  1264. ================================================================================
  1265. -->
  1266. <!ELEMENT Status EMPTY>
  1267. <!ATTLIST Status %localid;
  1268. %formalname; >
  1269. <!--
  1270. =============================== StatusWillChange ===============================
  1271. Advance notification of a status change that will automatically occur at the
  1272. specified date and time. For example, an item with a Status of "embargoed" might
  1273. have a StatusWillChange element stating that the status will become "usable" at
  1274. a specified time. This is equivalent to announcing in advance the time at which
  1275. the embargo will end and the item will be released.
  1276. ================================================================================
  1277. -->
  1278. <!ELEMENT StatusWillChange (FutureStatus , DateAndTime )>
  1279. <!ATTLIST StatusWillChange %localid; >
  1280. <!--
  1281. ================================= SubHeadLine ==================================
  1282. A displayable subsidiary headline.
  1283. ================================================================================
  1284. -->
  1285. <!ELEMENT SubHeadLine (#PCDATA | Origin )*>
  1286. <!ATTLIST SubHeadLine %localid;
  1287. xml:lang CDATA #IMPLIED >
  1288. <!--
  1289. =================================== Subject ====================================
  1290. An indication of the Subject of a NewsItem. The value of the FormalName
  1291. attribute is a formal name for the Subject. Its meaning and permitted values
  1292. are determined by a controlled vocabulary as described in the comment to the
  1293. formalname ENTITY declaration above.
  1294. ================================================================================
  1295. -->
  1296. <!ELEMENT Subject EMPTY>
  1297. <!ATTLIST Subject %localid;
  1298. %formalname;
  1299. %assignment; >
  1300. <!--
  1301. ================================= SubjectCode ==================================
  1302. A container for the IPTC Subject Codes that indicate the subject of a NewsItem,
  1303. as defined in the IPTC Information Interchange Model. It consists of one more
  1304. Subject, SubjectMatter and SubjectDetail elements, optionally amplified by one
  1305. or more SubjectQualifier elements.
  1306. ================================================================================
  1307. -->
  1308. <!ELEMENT SubjectCode ( (Subject | SubjectMatter | SubjectDetail ) , SubjectQualifier* )*>
  1309. <!ATTLIST SubjectCode %localid;
  1310. %assignment; >
  1311. <!--
  1312. ================================ SubjectDetail =================================
  1313. An indication of the SubjectDetail of a NewsItem. The value of the FormalName
  1314. attribute is a formal name for the SubjectDetail. Its meaning and permitted
  1315. values are determined by a controlled vocabulary as described in the comment
  1316. to the formalname ENTITY declaration above.
  1317. ================================================================================
  1318. -->
  1319. <!ELEMENT SubjectDetail EMPTY>
  1320. <!ATTLIST SubjectDetail %localid;
  1321. %formalname;
  1322. %assignment; >
  1323. <!--
  1324. ================================ SubjectMatter =================================
  1325. An indication of the SubjectMatter of a NewsItem. The value of the FormalName
  1326. attribute is a formal name for the SubjectMatter. Its meaning and permitted
  1327. values are determined by a controlled vocabulary as described in the comment to
  1328. the formalname ENTITY declaration above.
  1329. ================================================================================
  1330. -->
  1331. <!ELEMENT SubjectMatter EMPTY>
  1332. <!ATTLIST SubjectMatter %localid;
  1333. %formalname;
  1334. %assignment; >
  1335. <!--
  1336. =============================== SubjectQualifier ===============================
  1337. An indication of the SubjectQualifier of a NewsItem. The value of the FormalName
  1338. attribute is a formal name for the SubjectQualifier. Its meaning and permitted
  1339. values are determined by a controlled vocabulary as described in the comment to
  1340. the formalname ENTITY declaration above.
  1341. ================================================================================
  1342. -->
  1343. <!ELEMENT SubjectQualifier EMPTY>
  1344. <!ATTLIST SubjectQualifier %localid;
  1345. %formalname;
  1346. %assignment; >
  1347. <!--
  1348. =============================== SystemIdentifier ===============================
  1349. A system identifier (in the sense defined by the XML 1,0 Specification) for a
  1350. NewsItem.
  1351. ================================================================================
  1352. -->
  1353. <!ELEMENT SystemIdentifier (#PCDATA )>
  1354. <!ATTLIST SystemIdentifier %localid; >
  1355. <!--
  1356. ============================= ThisRevisionCreated ==============================
  1357. The date and, optionally, time at which the current revision of a NewsItem was
  1358. created, expressed in ISO 8601 Basic Format, as described in the comment to the
  1359. DateAndTime attribute within the assignment ENTITY declaration above.
  1360. ================================================================================
  1361. -->
  1362. <!ELEMENT ThisRevisionCreated (#PCDATA )>
  1363. <!ATTLIST ThisRevisionCreated %localid; >
  1364. <!--
  1365. ==================================== Topic =====================================
  1366. This element provides information about a thing (Topic) named by a formal
  1367. name or occurring in a NewsComponent. A Topic must have one or more TopicType
  1368. subelements, which state what type of Topic it is. The optional Details
  1369. attribute provides a pointer, in the form of a URL or URN, to additional
  1370. information about the Topic.
  1371. ================================================================================
  1372. -->
  1373. <!ELEMENT Topic (Comment* , Catalog? , TopicType+ , FormalName* , Description* , Property* )>
  1374. <!ATTLIST Topic %localid;
  1375. Details CDATA #IMPLIED >
  1376. <!--
  1377. =============================== TopicOccurrence ================================
  1378. An indication that a particular topic occurs within the content of a
  1379. NewsComponent. The optional HowPresent attribute indicates the nature of that
  1380. topic's occurrence. The value of the Topic attribute must consist of a #
  1381. character followed by the value of the Duid attribute of a Topic in the current
  1382. document.
  1383. ================================================================================
  1384. -->
  1385. <!ELEMENT TopicOccurrence EMPTY>
  1386. <!ATTLIST TopicOccurrence %localid;
  1387. %assignment;
  1388. Topic CDATA #IMPLIED >
  1389. <!--
  1390. ================================== TopicSet ====================================
  1391. A container for Topics. The value of the FormalName attribute is a formal name
  1392. for the TopicSet. Its meaning and permitted values are determined by a
  1393. controlled vocabulary as described in the comment to the formalname ENTITY
  1394. declaration above.
  1395. ================================================================================
  1396. -->
  1397. <!ELEMENT TopicSet (Comment* , Catalog? , TopicSetRef* , Topic* )>
  1398. <!ATTLIST TopicSet %localid;
  1399. %formalname; >
  1400. <!--
  1401. ================================= TopicSetRef ==================================
  1402. A pointer to a TopicSet that is to be merged with the current one. The TopicSet
  1403. attribute is a pointer to the relevant TopicSet. Its value can be an http URL,
  1404. or a NewsML URN as described in the comment to PublicIdentifier, or a fragment
  1405. identifier consisting of a # character followed by the Duid of a TopicSet in the
  1406. current document. The presence of a TopicSetRef child in a TopicSet has the
  1407. effect that all the Topics in the referenced TopicSet are included by reference
  1408. within the current TopicSet. When this merging results in there exising two
  1409. FormalName grandchildren of the same TopicSet that have the same content and
  1410. the same Scheme attribute value, then the Topics whose children are in fact the
  1411. same topic, and are deemed to be merged. The merging of Topics need not be
  1412. performed physically by the system, but the meaning of the data is
  1413. exactly the same as if the merging were actually performed. Merging two
  1414. Topcis consists of creating a single Topic that contains all the children of
  1415. both, and eliminating duplicates.
  1416. ================================================================================
  1417. -->
  1418. <!ELEMENT TopicSetRef (Comment* )>
  1419. <!ATTLIST TopicSetRef %localid;
  1420. TopicSet CDATA #IMPLIED >
  1421. <!--
  1422. ================================== TopicType ===================================
  1423. An indication of the type of a Topic. The value of the FormalName attribute is
  1424. a formal name for the TopicType. Its meaning and permitted values are determined
  1425. by a controlled vocabulary as described in the comment to the formalname ENTITY
  1426. declaration above.
  1427. ================================================================================
  1428. -->
  1429. <!ELEMENT TopicType EMPTY>
  1430. <!ATTLIST TopicType %localid;
  1431. %formalname; >
  1432. <!--
  1433. ================================== TopicUse ====================================
  1434. An indication of where a particular Topic is used in a NewsML document. The
  1435. value of the Topic attribute must consist of a # character followed by the
  1436. value of the Duid of a Topic in the current document. The value of the Context
  1437. attribute is an XPath pattern indicating the context where the referenced topic
  1438. is used within the subtree to which the current Catalog applies. If the Context
  1439. attribute is not present, the TopicUse element simply states that this topic is
  1440. present somewhere in the subtree.
  1441. ================================================================================
  1442. -->
  1443. <!ELEMENT TopicUse EMPTY>
  1444. <!ATTLIST TopicUse Topic CDATA #REQUIRED
  1445. Context CDATA #IMPLIED >
  1446. <!--
  1447. ================================ TransmissionId ================================
  1448. An identifier for the NewsML document transmission. This should be unique among
  1449. all distinct transmissions from the same publisher. If a transmission is
  1450. repeated (perhaps because the sender is not confident that it was successfully
  1451. received) then the same TransmissionId content may be used, but a Repeat
  1452. attribute should be provided to distinguish the second transmission from the
  1453. first. The form that the value of the Repeat attribute takes is determined by
  1454. the provider. Likewise, the format for the TransmissionId itself is for the
  1455. provider to decide. It could for example consist of a channel identifier
  1456. followed by a sequence number.
  1457. ================================================================================
  1458. -->
  1459. <!ELEMENT TransmissionId (#PCDATA )>
  1460. <!ATTLIST TransmissionId %localid;
  1461. Repeat CDATA #IMPLIED >
  1462. <!--
  1463. ==================================== Update ====================================
  1464. A modification to an existing NewsItem. This can be an insertion, replacement
  1465. or deletion. Note that the Update element cannot be used to modify the
  1466. NewsManagement or Identification element, or any of their descendants.
  1467. Modifications to these parts of the NewsItem can be made by issuing the
  1468. NewsItem under the current revision number, with only the Identification and
  1469. NewsManagement elements present. These will replace the previous Identification
  1470. and NewsManagement elements in their totality.
  1471. ================================================================================
  1472. -->
  1473. <!ELEMENT Update (InsertBefore | InsertAfter | Replace | Delete )*>
  1474. <!ATTLIST Update %localid; >
  1475. <!--
  1476. =================================== Urgency ====================================
  1477. An indication of the urgency of a NewsItem. The value of the FormalName
  1478. attribute is a formal name for the Urgency. Its meaning and permitted values
  1479. are determined by a controlled vocabulary as described in the comment to the
  1480. formalname ENTITY declaration above.
  1481. ================================================================================
  1482. -->
  1483. <!ELEMENT Urgency EMPTY>
  1484. <!ATTLIST Urgency %localid;
  1485. %formalname; >
  1486. <!--
  1487. ===================================== Url ======================================
  1488. A URL that can be used to locate a Resource.
  1489. ================================================================================
  1490. -->
  1491. <!ELEMENT Url (#PCDATA )>
  1492. <!ATTLIST Url %localid; >
  1493. <!--
  1494. ===================================== Urn ======================================
  1495. A URN that provides a global identifier for a resource. This will typically (but
  1496. not necessarily) be a NewsML URN as described in the comment to PublicIdentifier.
  1497. ================================================================================
  1498. -->
  1499. <!ELEMENT Urn (#PCDATA )>
  1500. <!ATTLIST Urn %localid; >
  1501. <!--
  1502. ================================= UsageRights ==================================
  1503. Information about the usage rights pertaining to a NewsComponent.
  1504. ================================================================================
  1505. -->
  1506. <!ELEMENT UsageRights (UsageType? , Geography? , RightsHolder? , Limitations? , StartDate? , EndDate? )>
  1507. <!ATTLIST UsageRights %localid;
  1508. %assignment; >
  1509. <!--
  1510. ================================== UsageType ===================================
  1511. A natural-language indication of the type of usage to which the rights apply.
  1512. ================================================================================
  1513. -->
  1514. <!ELEMENT UsageType (#PCDATA | Origin )*>
  1515. <!ATTLIST UsageType %localid;
  1516. xml:lang CDATA #IMPLIED
  1517. %assignment; >