Difference between revisions of "Code Discussion 2009-06-22"

From MPDLMediaWiki
Jump to navigation Jump to search
(New page: ==Namespace Changes== * event, source, organization, person are handled als "profiles" now (as it is already in colab) the same way like publication and the schema definitions are in sepa...)
 
 
(13 intermediate revisions by one other user not shown)
Line 1: Line 1:
=Previous topic=
[[Code_Discussion_2009-05-25 | Previous topic 2009-05-25]]
==Namespace Changes==
==Namespace Changes==
===What has changed?===


* event, source, organization, person are handled als "profiles" now (as it is already in colab) the same way like publication and the schema definitions are in separate files
* event, source, organization, person are handled als "profiles" now (as it is already in colab) the same way like publication and the schema definitions are in separate files
* enums have an own namespace (see below)
* enums have an own namespace (see below)
* all elements under publication, event, source, person, organization, file (not elements from external schemas like dc, dcterms) are in the same NS
* all elements under publication, event, source, person, organization, file (not elements from external schemas like dc, dcterms) are in the same NS
===Why?===
* every profile needs an own namespace for versioning reasons
* some properties/terms (e.g. publishing-info) occurred in different namespaces (error-prone)
* better reuse of properties/terms in diffenerent profiles if there is one common namespace for all terms
===Status===
* alle schemas for pubman are finished
* collection and image are under rework now (some types have to be renamed or merged with pubman types)
* XSLTs are updated, namespace placeholders have to be synchronized with pom
* see [[Checklist_for_Metadata_Changes]] for all required updates


==Namespaces==
==Namespaces==


===PROFILES===
===Profiles===


* file: http://purl.org/metadata/profiles/0.1/file
* file: http://purl.org/metadata/profiles/0.1/file
* organization: http://purl.org/escidoc/metadata/profiles/0.1/organization
* organization: http://purl.org/escidoc/metadata/profiles/0.1/organization
* organizationalunit: http://purl.org/escidoc/metadata/profiles/0.1/organizationalunit
* source: http://purl.org/escidoc/metadata/profiles/0.1/source
* source: http://purl.org/escidoc/metadata/profiles/0.1/source
* event: http://purl.org/escidoc/metadata/profiles/0.1/event
* event: http://purl.org/escidoc/metadata/profiles/0.1/event
* person: http://purl.org/escidoc/metadata/profiles/0.1/person
* person: http://purl.org/escidoc/metadata/profiles/0.1/person
* publication: http://purl.org/escidoc/metadata/profiles/0.1/publication
* publication: http://purl.org/escidoc/metadata/profiles/0.1/publication
* collection: http://purl.org/escidoc/metadata/profiles/0.1/collection
* image: http://purl.org/escidoc/metadata/profiles/0.1/image


===PROPERTIES/TERMS===
===Terms/Properties===


* eterms: http://purl.org/escidoc/metadata/terms/0.1/
* eterms: http://purl.org/escidoc/metadata/terms/0.1/


===VOCABULARY ENCODING SCHEMES/ENUMS===
===Vocabulary Encoding Schemes===


* eves: http://purl.org/escidoc/metadata/ves/0.1/
* eves: http://purl.org/escidoc/metadata/ves/0.1/
==Schema Locations==
* file: http://purl.org/metadata/schemas/0.1/file
* organization: http://purl.org/escidoc/metadata/schemas/0.1/organization
* organizationalunit: http://purl.org/escidoc/metadata/schemas/0.1/organizationalunit
* source: http://purl.org/escidoc/metadata/schemas/0.1/source
* event: http://purl.org/escidoc/metadata/schemas/0.1/event
* person: http://purl.org/escidoc/metadata/schemas/0.1/person
* publication: http://purl.org/escidoc/metadata/schemas/0.1/publication
* collection: http://purl.org/escidoc/metadata/schemas/0.1/collection
* image: http://purl.org/escidoc/metadata/schemas/0.1/image
* eterms: http://purl.org/escidoc/metadata/schemas/0.1/types
* eves: http://purl.org/escidoc/metadata/schemas/0.1/enumtypes
* escidocprofile: http://purl.org/escidoc/metadata/schemas/0.1/escidocprofile
==Other changes==
* organization looks like the following example:
<pre>
<organization:organization>
<dc:title xml:lang="fr">Department of Physics, University of California</dc:title>
<eterms:address>Berkeley, CA 94720, USA</eterms:address>
<dc:identifier xsi:type="eidt:ESCIDOC">P4711</dc:identifier>
</organization:organization>
</pre>
=Next topic=
[[Code_Discussion_2009-06-29 | Next topic 2009-06-29]]
[[Category:Code_Discussion|Code 2009-06-22]]

Latest revision as of 12:40, 4 September 2009

Previous topic

Previous topic 2009-05-25

Namespace Changes

What has changed?

  • event, source, organization, person are handled als "profiles" now (as it is already in colab) the same way like publication and the schema definitions are in separate files
  • enums have an own namespace (see below)
  • all elements under publication, event, source, person, organization, file (not elements from external schemas like dc, dcterms) are in the same NS

Why?

  • every profile needs an own namespace for versioning reasons
  • some properties/terms (e.g. publishing-info) occurred in different namespaces (error-prone)
  • better reuse of properties/terms in diffenerent profiles if there is one common namespace for all terms

Status

  • alle schemas for pubman are finished
  • collection and image are under rework now (some types have to be renamed or merged with pubman types)
  • XSLTs are updated, namespace placeholders have to be synchronized with pom
  • see Checklist_for_Metadata_Changes for all required updates

Namespaces

Profiles

Terms/Properties

Vocabulary Encoding Schemes

Schema Locations

Other changes

  • organization looks like the following example:

		<organization:organization>
			<dc:title xml:lang="fr">Department of Physics, University of California</dc:title>
			<eterms:address>Berkeley, CA 94720, USA</eterms:address>
			<dc:identifier xsi:type="eidt:ESCIDOC">P4711</dc:identifier>
		</organization:organization>
	

Next topic

Next topic 2009-06-29