Difference between revisions of "ESciDoc Application Profiles"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 22: Line 22:
* [[ESciDoc_Application_Profile_Event]]
* [[ESciDoc_Application_Profile_Event]]
* [[ESciDoc_Application_Profile_File]]
* [[ESciDoc_Application_Profile_File]]
* [[ESciDoc_Application_Profile_Source]]


== Related eSciDoc Encoding Schemes ==
== Related eSciDoc Encoding Schemes ==

Revision as of 09:24, 12 September 2008

eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit


  • work in progress

Open issues[edit]

I moved the open issues to the discussion page -- Andreas Gros 08:19, 20 March 2008 (CET)


Application Profiles[edit]

The eSciDoc Application Profiles (AP) document the descriptive elements used by eSciDoc to describe its content entities, e.g. publications, organizations, etc. Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in these APs. The APs are nowhere near to being complete yet.

In the first step, the APs are meant for documenting the existing xml schemas only. These documents should be the basis for all future communication about the metadata profiles in use, e.g. PubMan. We also expect that this approach will help us clarifying how to implement the requirements, thus the work will have certain impacts on the xml schemas.

The format of the table below follows the CEN Workshop Agreement 14855 for Dublin Core Application Profile Guidelines[1]


eSciDoc Application Profiles[edit]

Related eSciDoc Encoding Schemes[edit]



References[edit]

  1. CWA14855: Dublin Core Application Profile guidelines, see http://www.cen.eu/cenorm/businessdomains/businessdomains/isss/cwa/cwa14855.asp