121 lines
3.4 KiB
Plaintext
121 lines
3.4 KiB
Plaintext
head 1.5;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.5
|
|
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2005.09.09.13.06.05; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2005.05.12.19.33.57; author BobMorris; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2005.05.12.16.52.30; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2005.05.12.12.03.33; author BobMorris; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@Added topic name via script
|
|
@
|
|
text
|
|
@---+!! %TOPIC%
|
|
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1126271165" format="1.0" version="1.4"}%
|
|
%META:TOPICPARENT{name="SchemaDiscussion"}%
|
|
Consider the Library of Congress Metadata Object Schema ([[http://www.loc.gov/standards/mods/][mods]]) for the description of publications. It is, I am told, widely used in the digital library world, and there is apparently a lot(?) of software that extracts publication in mods format directly from library catalogs. It is conceivable that this makes it better than an a specially defined UBIF definition of publication descriptions.
|
|
|
|
-- Main.BobMorris - 12 May 2005
|
|
|
|
I did look at it and it is being discussed on ProxyDataPublication and ProxyDataPublicationMODS. I personally have been utterly unable to understand how to use MODS for a simple things like citing an article in a journal. I guess it can do that, but it seems not really to be designed for it (rather for library objects with rich metadata, cataloguing, classification, all of which is not really relevant in scientific publication citing).
|
|
|
|
As said on the cited pages, MODS is an alternative, but someone would have to sit down and explain how to use it. Also it is pretty huge, perhaps a factor of 50 larger than the AlexandriaCore proposal...
|
|
|
|
-- Main.GregorHagedorn - 12 May 2005
|
|
|
|
|
|
Actually, I convinced myself that the "type" attribute duplication fault in the schema is not a fault but a namespace botch in XMLSpy, still there in Spy2005 SP2. Also, that version of Spy does show attributes in the diagrams in a quire reasonable way.
|
|
|
|
I'm not sure about the complaint about size. I believe neither xs:import nor xs:include actually impose any requirement to physically include anything in the containing schema, so the only issue is whether one thinks it is too big to master. But all the elements are global, so if it turns out to be convenient to only use a few of them, one would only have to study a few.
|
|
|
|
-- Main.BobMorris - 12 May 2005
|
|
|
|
Certainly, with size I only refer to the effort required by adapters to map their local data to such a complex and truly difficult to understand schema. And the effort by people writing software in making sure they are able to import all the data.
|
|
|
|
Unfortunately, when exchanging scientific data, I still believe it is important to get the full semantics, or drop only things you have analyzed as being irrelevant to your purpose. That is where I personally feel a microMODS may be needed.
|
|
|
|
-- Main.GregorHagedorn - 9 Sept 2005
|
|
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1115926437" format="1.0" version="1.3"}%
|
|
d20 6
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1115916750" format="1.0" version="1.2"}%
|
|
d13 7
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1115899413" format="1.0" version="1.1"}%
|
|
d5 3
|
|
d9 1
|
|
d11 1
|
|
a11 1
|
|
-- Main.BobMorris - 12 May 2005
|
|
@
|