steve
/
wiki-archive
mirror of https://github.com/tdwg/wiki-archive.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
wiki-archive/twiki/data/GUID/LSIDResolverForImages.txt,v

431 lines
12 KiB
Plaintext
Raw Permalink Normal View History

Archive entire twiki setup from owl as of today
2016-02-24 10:46:01 +00:00
head 1.14;
access;
symbols;
locks; strict;
comment @# @;
1.14
date 2007.01.29.16.16.52; author RicardoPereira; state Exp;
branches;
next 1.13;
1.13
date 2006.05.18.19.50.29; author BobMorris; state Exp;
branches;
next 1.12;
1.12
date 2006.05.18.19.49.47; author BobMorris; state Exp;
branches;
next 1.11;
1.11
date 2006.03.21.02.58.34; author BobMorris; state Exp;
branches;
next 1.10;
1.10
date 2006.03.21.02.53.53; author BobMorris; state Exp;
branches;
next 1.9;
1.9
date 2006.03.21.01.18.17; author BobMorris; state Exp;
branches;
next 1.8;
1.8
date 2006.03.21.01.16.52; author BobMorris; state Exp;
branches;
next 1.7;
1.7
date 2006.03.21.01.01.07; author BobMorris; state Exp;
branches;
next 1.6;
1.6
date 2006.03.20.23.39.07; author BobMorris; state Exp;
branches;
next 1.5;
1.5
date 2006.03.20.23.38.04; author BobMorris; state Exp;
branches;
next 1.4;
1.4
date 2006.03.20.23.21.30; author BobMorris; state Exp;
branches;
next 1.3;
1.3
date 2006.03.09.05.11.29; author LeeBelbin; state Exp;
branches;
next 1.2;
1.2
date 2006.03.08.14.59.41; author BobMorris; state Exp;
branches;
next 1.1;
1.1
date 2006.02.13.20.52.22; author RicardoPereira; state Exp;
branches;
next ;
desc
@
.
@
1.14
log
@none
@
text
@%META:TOPICINFO{author="RicardoPereira" date="1170087412" format="1.1" version="1.14"}%
---++ LSID Resolver for Images
*Coordinator(s)*: Main.BobMorris
*Participants*: Hui Dong, Greg Riccardi
Main.HuiDong did the resolver service. All entries here are by Main.BobMorris unless otherwise indicated. Please indicate when you contribute. Thanks.
----
---+++ Description
This group will develop a prototype LSID resolver for images.
----
---+++ Technical Information
* *URL for prototype user interface:*
* *LSID authority(ies):* cs.umb.edu
* *LSID namespace(s):* Mass_invasive_plant
* *Hardware platform:* Sun Fire V250 8Gb ram, 180 Gb disk
* *Server platform:* Solaris 8 (sos5.8); Apache 2.0.54, Apache tomcat 5.0.28 java servlet container
* *LSID Software stack used:* IBM LSID Server stack ver 1.0.0
* *RDF/OWL ontology used for metadata:* A slight extension of http://www.w3.org/2003/12/exif/ (http://www.w3.org/2003/12/exif/ns) as we discuss below, for metadata for "byte stream objects" such as image files. Unlear what to do for conceptual objects; Possibilities include simple representation of DIG35 "THING" element, or a representation of SDD in RDF, which would be a major, major project and quite controversial.
* *Approximate number of LSIDs stored:* Right now, 2. Later this week(?) 12,000
* *Benchmarchs:*
* *Other resources:* http://esw.w3.org/topic/ImageDescription is an apparently defunct discussion at W3C. It points to several toy RDF examples.
----
---+++ Roadmap, Milestones, Timeline
(Enter one task per line with estimated time for completion. Check tasks when completed, but leave all entries for logging purposes)
Example:
* Mar/06 - Install web server. (COMPLETE March 1. Already in place.)
* Apr/06 - Install LSID server stack (COMPLETE March 20) and map data tables; Server stack in place March 20, 2006; objects are on file system. To be followed by sample service of 12,000 objects from our image store.
----
---+++ Discussion, Implementation Issues
(List issues, roadblocks, missing software components, etc)
*Issues:*
* What to do about content descriptive metadata, which probably belong on the conceptual objects
* How to represent the relations between conceptual and bytestream objects. This must be an issue common to all digital objects.
* What do acquisition devices automate? Presently, mainly EXIF in JPEG files and perhaps in the vendor-specific "RAW" formats. Nothing(?) for scanners.
* Where are the image annotation tools and what do emit that will be helpful
* What are the widely used image servers and how do they fit in the picture, since many of them support annotation.
*Roadblocks:*
*IBM LSID browser plugin for MSIE and for Firefox: *
For both MSIE and Firefox it seems to require administrative privilege to run on WinXP by default. (It wants to write in its installation directories, which are normally privileged). Does anybody know what to do about this?
The behavior of the IBM LSID plugin in Firefox is obscurely different from that on MSIE. We'll try to characterize this a little better.
*Implementation:*
These links [[foo][bar]]should resolve.
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:BeachRoseAbstract<br>
Here it is in [[http://linnaeus.zoology.gla.ac.uk/~rpage/lsid/tester/?q=urn%3Alsid%3Acs.umb.edu%3AMass_invasive_plant%3ABeachRoseAbstract&submit=Go][ Rod Page's LSID Tester]].
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:beachrose_RosaRugosaWhiteWollRes2<br>
Here it is in [[http://linnaeus.zoology.gla.ac.uk/~rpage/lsid/tester/?q=urn%3Alsid%3Acs.umb.edu%3AMass_invasive_plant%3Abeachrose_RosaRugosaWhiteWollRes2&submit=Go][ Rod Page's LSID Tester]]
We think a lot of discussion is necessary about what is appropriate to be behind image LSIDs. Just to get our toes wet, the LSIDs at cs.umb.edu as linked above, presently do this:
1. For byte streams (presently only jpg files) the metadata is EXIF extracted from the file itself (which we don't think is that interesting), together with a list of LSIDs for some conceptual objects for which the service wishes to assert the relationship InstanceOf
1. For byte streams, there is not presently any data, though the image pixels, plus some GUID identifying the encoding of them, is a possible candidate.
1. For conceptual objects, no data; metadata is a list of LSIDs for which the conceptual object asserts a relation HasInstance. One would hope that If A HasInstance B then B InstanceOf A, but this is not presently enforced. In fact, none of the LSIDs in the various lists are even presently guaranteed resolvable, though most if not all do.
We are in the process of wrapping our biodiversity image store at http://efg.cs.umb.edu/gallery/, implemented in Menalto Gallery, so that it is actually the data store behind the LSID service. We may wait until we deploy Gallery2, which can store images as BLOBs in most RDBs, to do this. Or we may not.
For what it is worth, attentive readers will find that our namespace choice directly contravenes the opinion I express at http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDResolverNamespaces in opposition to KevinRichard's best practice recommendation of March 20, 2006. (In other words, we sort of follow his proposal, and, IMO is likely to lead us down a path of namespace proliferation since our image store is eclectic, and probably so is everybody else's.)
----
---+++ Lessons Learned, Conclusions, Recommendations
None yet.
----
---+++++ Categories
CategoryWorkingGroup
CategoryPrototypingWG
@
1.13
log
@
.
@
text
@d1 1
d4 1
a4 1
*Coordinator(s):BobMorris
d6 1
a6 1
*Participants:Hui Dong, Greg Riccardi
d9 1
a9 1
HuiDong did the resolver service. All entries here are by BobMorris unless otherwise indicated. Please indicate when you contribute. Thanks.
d19 10
a28 11
*URL for prototype user interface:*
*LSID authority(ies):* cs.umb.edu
*LSID namespace(s):* Mass_invasive_plant
*Hardware platform:* Sun Fire V250 8Gb ram, 180 Gb disk
*Server platform:* Solaris 8 (sos5.8); Apache 2.0.54, Apache tomcat 5.0.28 java servlet container
*LSID Software stack used:* IBM LSID Server stack ver 1.0.0
*RDF/OWL ontology used for metadata:* A slight extension of http://www.w3.org/2003/12/exif/ (http://www.w3.org/2003/12/exif/ns) as we discuss below,
for metadata for "byte stream objects" such as image files. Unlear what to do for conceptual objects; Possibilities include simple representation of DIG35 "THING" element, or a representation of SDD in RDF, which would be a major, major project and quite controversial.
*Approximate number of LSIDs stored:* Right now, 2. Later this week(?) 12,000
*Benchmarchs:*
*Other resources:* http://esw.w3.org/topic/ImageDescription is an apparently defunct discussion at W3C. It points to several toy RDF examples.
d86 1
a86 1
CategoryPrototypingWG@
1.12
log
@
.
@
text
@d66 1
a66 1
Here it is in [[http://linnaeus.zoology.gla.ac.uk/~rpage/lsid/tester/?q=urn%3Alsid%3Acs.umb.edu%3AMass_invasive_plant%3Abeachrose_RosaRugosaWhiteWollRes2&submit=Go"][Rod Page's LSID Tester]]
@
1.11
log
@
.
@
text
@d60 1
a60 1
These links should resolve.
d62 2
a63 3
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:BeachRoseAbstract
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:beachrose_RosaRugosaWhiteWollRes2
d65 2
@
1.10
log
@
.
@
text
@d35 2
a36 2
* Mar/06 - In place
* Apr/06 - Install LSID server stack and map data tables; Server stack in place March 20, 2006; objects are on file system. To be followed by sample service of 12,000 objects from our image store.
d74 1
a74 2
For what it is worth, attentive readers will find that our namespace choice directly contravenes the opinion I express at http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDResolverNamespaces in opposition to KevinRichard's best practice recommendation of March 20, 2006. (In other words, it sort of follows his proposal, and, IMO is likely to lead us down a path of namespace proliferation since our image store is eclectic.
@
1.9
log
@
.
@
text
@d8 1
a8 1
All entries by BobMorris unless otherwise indicated. Please indicate when you contribute. Thanks.
d68 1
a68 1
1. For byte streams (presently only jpg files) the metadata is EXIF extracted from the file itself (which we don't think is that interesting), together with a list of LSIDs for some conceptual objects for which the service wishes to assert the relationship instanceOf
@
1.8
log
@
.
@
text
@d60 1
a60 1
These links should resolve. Some commentary to follow shortly
@
1.7
log
@
.
@
text
@d7 3
d60 7
a66 1
We think a lot of discussion is necessary about what is appropriate to be behind image LSIDs. Just to get our toes wet, the LSIDs at cs.umb.edu as linked below, presently do this:
d70 5
a74 1
1. For conceptual
d80 1
a80 5
These links should resolve. Some commentary to follow shortly
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:BeachRoseAbstract
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:beachrose_RosaRugosaWhiteWollRes2
@
1.6
log
@
.
@
text
@d55 8
@
1.5
log
@
.
@
text
@d61 1
a61 1
lsidres:urn:lsid:cs.umb.edu:Mass_invasive_plant:StaghornSumacAbstract
@
1.4
log
@
.
@
text
@d20 1
a20 1
*LSID Software stack used:* (Java, Perl, .NET - client and/or server - please include versions)
d38 1
a38 1
(List issues, readblocks, missing software components, etc)
d40 1
a41 1
a42 1
a43 1
d45 9
a54 1
* What are the widely used image servers and how do they fit in the picture, since many of them support annotation.
d62 1
d65 1
@
1.3
log
@Missing close bold
.
@
text
@d16 2
a17 2
*LSID authority(ies):*
*LSID namespace(s):*
d21 1
a21 1
*RDF/OWL ontology used for metadata:* Probably some extension of http://www.w3.org/2003/12/exif/ (http://www.w3.org/2003/12/exif/ns)
d23 1
a23 1
*Approximate number of LSIDs stored:*
d33 1
a33 1
* Apr/06 - Install LSID server stack and map data tables
d53 1
d55 2
a56 2
@
1.2
log
@
.
@
text
@d21 1
a21 1
*RDF/OWL ontology used for metadata: Probably some extension of http://www.w3.org/2003/12/exif/ (http://www.w3.org/2003/12/exif/ns)
d25 1
a25 1
*Other resources:** http://esw.w3.org/topic/ImageDescription is an apparently defunct discussion at W3C. It points to several toy RDF examples.
@
1.1
log
@Initial revision
@
text
@d3 1
a3 1
*Coordinator(s):*
d5 1
a5 1
*Participants:*
d18 2
a19 2
*Hardware platform:* (Intel, Sun, etc - include complete specs: processors, amount of RAM, disk, SCSI, ATA, SATA, RAID, etc)
*Server platform:* (OS, Webserver, DBMS, programming language - please include versions)
d21 2
a22 1
*RDF/OWL ontology used for metadata:* (URI to ontology)
d25 1
a25 1
*Other resources:*
d32 1
a32 1
* Mar/06 - Set up webserver
d40 1
d42 8
d60 1
a60 1
CategoryPrototypingWG
@