Difference between revisions of "ESciDoc Application Profiles"

	eSciDoc Solutions
	PubMan:; Overview · Functionalities; Interfaces · Support ;
	Faces:; Overview · Functionalities; Scope · Support ;
	ViRR:; Overview · Functionalities ; Scope · Support;
	imeji; Digitization Lifecycle;
	edit

Latest revision as of 06:50, 1 July 2016

work in progress (draft)

Aim and Scope[edit]

The eSciDoc Application Profiles (AP) documents 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.

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

eSciDoc PubMan - Functional Requirements[edit]

PubMan_Functionalities

eSciDoc PubMan - Domain Model[edit]

eSciDoc Description Set Profile (Classes)[edit]

Publication[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/publication
Label	publication
DC Definition	A book, article, or other documentary resource.
DC Comment	-
eSciDoc Definition	A publication, e.g. book, article, inproceedings.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	http://purl.org/dc/terms/BibliographicResource
Best practice	-
Remarks	-

File[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/file
Label	file
eSciDoc Definition	A digital resource.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	-
Best practice	-
Remarks	-

Organization[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/organization
Label	organization
DC Definition	A resource that acts or has the power to act.
DC Comment	-
eSciDoc Definition	-
eSciDoc Comment	-
Type of term	Class
NarrowerThan	http://purl.org/dc/terms/Agent
Best practice	-
Remarks	-

Person[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/person
Label	person
DC Definition	A resource that acts or has the power to act.
DC Comment	-
eSciDoc Definition	Detailed information of the person.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	http://purl.org/dc/terms/Agent
Best practice	-
Remarks	-

Event[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/event
Label	event
eSciDoc Definition	Some items are related to an event, e.g. a conference or a lecture series.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	-
Best practice	-
Remarks	-

Source[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/source
Label	source
DC Definition	A book, article, or other documentary resource.
DC Comment	-
eSciDoc Definition	The bundle in which the item has been published, e.g. a journal, a book, a series or a database.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	http://purl.org/dc/terms/BibliographicResource
Best practice	-
Remarks	-

Legal Case[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/legal-case
Label	legal case
eSciDoc Definition	-
eSciDoc Comment	-
Type of term	Class
Best practice	-
Remarks	-

Project-Info[edit]

Term URI	http://purl.org/escidoc/metadata/profiles/0.1/project-info
Label	Project information
eSciDoc Definition	The Project information contains information about funding project the publication is related to.
eSciDoc Comment	-
Type of term	Class
NarrowerThan	-
Best practice	-
Remarks	-

eSciDoc PubMan Description Templates (Statements)[edit]

Related eSciDoc Encoding Schemes[edit]

ESciDoc_Encoding_Schemes

References[edit]

↑ CWA14855: Dublin Core Application Profile guidelines, see http://dublincore.org/usage/documents/profile-guidelines/

[cen14855-1] CWA14855: Dublin Core Application Profile guidelines, see http://dublincore.org/usage/documents/profile-guidelines/

[1]

@@ Line 4: / Line 4: @@
 == Aim and Scope ==
-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.
+The eSciDoc Application Profiles (AP) documents 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<ref name="cen14855">CWA14855: Dublin Core Application Profile guidelines, see http://www.cen.eu/cenorm/businessdomains/businessdomains/isss/cwa/cwa14855.asp</ref>
+The format of the table below follows the CEN Workshop Agreement 14855 for Dublin Core Application Profile Guidelines<ref name="cen14855">CWA14855: Dublin Core Application Profile guidelines, see http://dublincore.org/usage/documents/profile-guidelines/</ref>
 ==eSciDoc PubMan - Functional Requirements==
@@ Line 18: / Line 15: @@
 ==eSciDoc PubMan - Domain Model==
-[[Image:Pubman-domain-model.png]]
+[[File:Domain Model.png]]
 == eSciDoc Description Set Profile (Classes) ==
@@ Line 119: / Line 116: @@
 {|style="border:1px solid #1b90b5; "
 |width="150pt" bgcolor=#CEE3F6| '''Term URI'''
-|width="500pt"| http://purl.org/escidoc/metadata/proifles/0.1/person
+|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/person
 |-
 | bgcolor=#CEE3F6 | '''Label'''
@@ Line 201: / Line 198: @@
 | bgcolor=#CEE3F6 | '''NarrowerThan'''
 | http://purl.org/dc/terms/BibliographicResource
+|-
+| bgcolor=#CEE3F6 | '''Best practice'''
+| -
+|-
+| bgcolor=#CEE3F6 | '''Remarks'''
+| -
+|}
+=== Legal Case ===
+{|style="border:1px solid #1b90b5; "
+|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
+|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/legal-case
+|-
+| bgcolor=#CEE3F6 | '''Label'''
+| legal case
+|-
+| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
+| -
+|-
+| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
+| -
+|-
+| bgcolor=#CEE3F6 | '''Type of term'''
+| Class
+|-
+| bgcolor=#CEE3F6 | '''Best practice'''
+| -
+|-
+| bgcolor=#CEE3F6 | '''Remarks'''
+| -
+|}
+=== Project-Info ===
+{|style="border:1px solid #1b90b5; "
+|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
+|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/project-info
+|-
+| bgcolor=#CEE3F6 | '''Label'''
+| Project information
+|-
+| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
+| The Project information contains information about funding project the publication is related to.
+|-
+| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
+| -
+|-
+| bgcolor=#CEE3F6 | '''Type of term'''
+| Class
+|-
+| bgcolor=#CEE3F6 | '''NarrowerThan'''
+| -
 |-
 | bgcolor=#CEE3F6 | '''Best practice'''
@@ Line 217: / Line 265: @@
 * [[ESciDoc_Application_Profile_File|Description Template File]]
 * [[ESciDoc_Application_Profile_Event|Description Template Event]]
+* [[ESciDoc_Application_Profile_LegalCase|Description Template Legal Case]]
+* [[ESciDoc_Application_Profile_Yearbook|Description Template Yearbook]]
+* [[ESciDoc_Application_Profile_project-info|Description Template project-info]]
 == Related eSciDoc Encoding Schemes ==
@@ Line 225: / Line 276: @@
-[[Category:eSciDoc|Application Profile]]
-[[Category:Metadata]]
 [[Category:ESciDoc_Application_Profiles| ]]
 [[Category:PubMan_Functional_Specification|Application_Profile]]