Difference between revisions of "Talk:ESciDoc Application Profile File"

From MPDLMediaWiki
Jump to navigation Jump to search
m
 
Line 1: Line 1:
== Content ==
== General ==
* Content
: Is not a term describing the file for me. Suggestion to remove content from application profile --[[User:Inga|Inga]] 11:35, 15 May 2008 (CEST)
:: Supporting the proposal --[[User:Natasab|Natasa]] 14:06, 15 May 2008 (CEST)
::: Property removed from AP after checking with Andi --[[User:Inga|Inga]] 16:29, 29 May 2008 (CEST)
* Escidocidentifier has been removed because it is technical information. Thus it doesn`t belong to the metadata profile. -- [[User:Kurt|Julia]] 11:54 27 June 2008 (CEST)


is not a term describing the file for me. Suggestion to remove content from application profile --[[User:Inga|Inga]] 11:35, 15 May 2008 (CEST)
== Describing a file ==
:Supporting the proposal --[[User:Natasab|Natasa]] 14:06, 15 May 2008 (CEST)
:: Property removed from AP after checking with Andi --[[User:Inga|Inga]] 16:29, 29 May 2008 (CEST)


== xsd implementation - dc:format & dcterms:extend ==
=== Title ===


Please note that both properties are expected to be available for files, but the [https://zim01.gwdg.de/repos/smc/trunk/04_Design/01_System/MetadataHandling/XML_Schema/escidoc_file_profile.xsd xsd] only names dc:format. This was done because the imported schemes (dc and dcterms) already imply that dcterms:extent can be used for dc:format. The maximum number of dc:format has been set to "unbounded" and therefore it possible to specify:
=== Description ===
 
=== Identifier ===
 
=== Content Category ===
 
=== Size ===
* xsd implementation - dc:format & dcterms:extend
: Please note that both properties are expected to be available for files, but the [https://zim01.gwdg.de/repos/smc/trunk/04_Design/01_System/MetadataHandling/XML_Schema/escidoc_file_profile.xsd xsd] only names dc:format. This was done because the imported schemes (dc and dcterms) already imply that dcterms:extent can be used for dc:format. The maximum number of dc:format has been set to "unbounded" and therefore it possible to specify:
  <dc:format xsi:type="dcterms:IMT">image/jpeg</dc:format>
  <dc:format xsi:type="dcterms:IMT">image/jpeg</dc:format>
  <dcterms:extent>12</dcterms:extent>
  <dcterms:extent>12</dcterms:extent>


== escidocidentifier ==
=== Format ===


escidocidentifier has been removed because it is technical information. Thus it doesn`t belong to the metadata profile. -- [[User:Kurt|Julia]] 11:54 27 June 2008 (CEST)
=== Access Rights ===

Latest revision as of 09:47, 16 September 2008

General[edit]

  • Content
Is not a term describing the file for me. Suggestion to remove content from application profile --Inga 11:35, 15 May 2008 (CEST)
Supporting the proposal --Natasa 14:06, 15 May 2008 (CEST)
Property removed from AP after checking with Andi --Inga 16:29, 29 May 2008 (CEST)
  • Escidocidentifier has been removed because it is technical information. Thus it doesn`t belong to the metadata profile. -- Julia 11:54 27 June 2008 (CEST)

Describing a file[edit]

Title[edit]

Description[edit]

Identifier[edit]

Content Category[edit]

Size[edit]

  • xsd implementation - dc:format & dcterms:extend
Please note that both properties are expected to be available for files, but the xsd only names dc:format. This was done because the imported schemes (dc and dcterms) already imply that dcterms:extent can be used for dc:format. The maximum number of dc:format has been set to "unbounded" and therefore it possible to specify:
<dc:format xsi:type="dcterms:IMT">image/jpeg</dc:format>
<dcterms:extent>12</dcterms:extent>

Format[edit]

Access Rights[edit]