Talk:ESciDoc Application Profiles

From MPDLMediaWiki
Revision as of 14:40, 29 January 2008 by Andi (talk | contribs)
Jump to navigation Jump to search

The proposed data model for a complex type like "Creator" in eSciDoc looks like this:

  • Creator, with properties
    • CreatorType, can either be:
      • Person, which has the following properties:
        • Complete Name
        • Family Name
        • Given Name
        • Alternative Name
        • Person Title
        • Pseudonym
      • Organisation
          • Identifier
      • Organisation, with the following properties:
        • Oranisation Name
        • Address
        • Identifier
    • Creator Type has a further property:
      • Creator Role, which can be:
        • Author
        • Artist
        • Editor, ....


If we want the Application Profile to be Dublin-Core-Compliant, an issue with such complex types arises:
The DC Application Profile guidelines define Application Profiles as flat structures by allowing for relational attributes such as

  • Refines
  • Refined By
  • Encoding Scheme For
  • Has Encoding Scheme
  • Similar To

One possible solution to the dilemma would look like:

  • use "person" as an element that refines "creator" with an encoding scheme that defines its components (complete name, family name, ...)
  • use "organisation" as an element that refines "creator" with a corresponding encoding scheme
  • either
    • attach creatorRole as component of "person" and "organisation" with yet another encoding scheme (not sure whether or not nested encoding schemes are allowed)
    • or create an element "creatorRole" on the same level as "person" and "organisation" with a corresponding encoding scheme

Are there other suggestions?