Changes between Version 203 and Version 204 of CMDI 1.2/Specification
- Timestamp:
- 06/22/16 14:52:43 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Specification
v203 v204 244 244 A detailed specification of the above mentioned parts of a CMD instance is given in the next four sections. 245 245 246 === Example s===246 === Example 1 CMD instance envelope === 247 247 248 248 {{{ … … 291 291 || ||`<cmd:MdCollectionDisplayName>`||`xs:string`||0 or 1||The collection to which the described resource belongs, given as a human-readable name. Exploitation tools can use this name to present metadata collections.|| 292 292 293 === Example s===293 === Example 2 Header with foreign attribute === 294 294 295 295 {{{ … … 366 366 367 367 368 === Example s ===368 === Example 3 Resources === 369 369 370 370 {{{ … … 396 396 <cmd:ResourceRelationList/> 397 397 </cmd:Resources> 398 398 }}} 399 400 === Example 4 ResourceRelation List === 401 402 {{{ 403 #!xml 399 404 <cmd:ResourceRelationList/> 400 405 <cmd:ResourceRelation> … … 413 418 || ||`<cmd:IsPartOf>` ||`xs:anyURI`||0 to unbounded||A reference to an external resource of which the described resource is a part, in the form of a PID (`RECOMMENDED`) or a URL.|| 414 419 415 === Example s===420 === Example 5 IsPartOf List === 416 421 417 422 {{{ … … 447 452 || || || ||`<cmdp:{CMDComponent}>*`||`xs:complexType`||As specified in the CMD profile||A chunk of information related to the described resource, forming a part of its parent CMD component and further composed of CMD Elements and other CMD Components.|| 448 453 454 === Example 5 CMD instance payload === 455 456 {{{ 457 #!xml 458 <cmd:Components> 459 ... 460 </cmd:Components> 461 }}} 462 463 449 464 ---- 450 465 … … 475 490 || || `<Component>` || `xs:complexType` || 1 || Definition of the component's structure. || 476 491 477 === Example s===492 === Example 7 CCSL document === 478 493 479 494 {{{ … … 516 531 * A successor `SHOULD` only be present if the status of the CMD component is deprecated. 517 532 518 === Example s===533 === Example 8 CCSL Header === 519 534 520 535 {{{ … … 527 542 </Header> 528 543 }}} 544 545 === Example 9 CCSL Header for deprecated profile with successor === 529 546 530 547 {{{ … … 567 584 * A CMD component `MUST NOT` to be a descendant of itself. 568 585 569 === Example s===586 === Example 10 CMD Component definition === 570 587 571 588 {{{ … … 613 630 * If the CMD element has a `<ValueScheme>` the data type defaults to `string`. 614 631 615 === Example s===632 === Example 11 CMD Element definition === 616 633 617 634 {{{ … … 625 642 <Documentation>The name of the web service or set of web services.</Documentation> 626 643 </Element> 627 644 }}} 645 646 === Example 12 CMD Element definition with auto value === 647 648 {{{ 649 #!xml 628 650 <Element 629 651 name="CreationDate" … … 655 677 * If the CMD attribute has a `<ValueScheme>`, the data type defaults to string. 656 678 657 === Example s===679 === Example 13 CMD Attribute definition === 658 680 659 681 {{{ … … 696 718 * The `@URI` can also be used for an open vocabulary where the facilities of the vocabulary service can be used to find suggestions for an applicable value. 697 719 698 === Example s===720 === Example 14 Value restriction with enumeration === 699 721 700 722 {{{ … … 715 737 }}} 716 738 739 === Example 15 Value restriction with pattern === 740 717 741 {{{ 718 742 #!xml … … 729 753 Examples of aspects for which display cues may be introduced are display order, structural transformation (e.g. folding of hierarchies), labeling and visual styling. 730 754 731 === Example s===755 === Example 16 Cue for CMD Element === 732 756 733 757 {{{ … … 743 767 }}} 744 768 769 === Example 17 Cue for CMD Component === 770 745 771 {{{#!comment 746 772 TODO: Example with cues on <Component>
