I found this image which I think explains many of the kinds of things that Website builders need to think through. For some in the industry this is like.. Duh! but for others this kind of layout really helps us see the complexity and the parts we need to be thinking through to implement the website.
Many of the different kinds of things that website planners have to think through.
Who would have thunk I that I would do a post on cars? Mostly, I avoid car discussions. I have avoided these kinds of discussions since high-school, when all my friends raved about NASCAR and North American muscle cars, I have regularly reminded them that the best cars in the world prove their excellence in a race by negotiating turns in multiple directions, as well as negotiating changes in track elevation. By-the-way, RACECAR is a palindrome.
This posture has landed me quite a bit of criticism over the years. Aside from this, my practical side has suggested that a good car is one that allows one to get from ‘point A’ to ‘point B’.
My first car was a Renault, followed by a 1983 Honda Prelude, which in turn was followed by 1996 Honda Accord LX. I currently drive a 2005 Kia Spectra, which my wife bought before we were married.
1982 Renault - Mine was all light blue with a grey interior.
1982 Honda Prelude - Mine was this exact color scheme.
Driving from 2007 through 2011
But recently Becky and I have been looking at cars, not to buy one, just to look at them… and so I have been looking at some cars with more of an artistic eye rather than a functional or economical (esp. fuel efficiency) eye.
Several cars have caught my eye. I have long been a fan of the Porsche 911 and Porsche Boxter. But here are some other cars that look rather appealing. Most of these cars I have never even ridden in. Concerning color, I really like yellow. However, Bi-tonal color schemes like is common with the Toyota FJ and the Mini Cooper are also really cool. Of course Blue and white, Blue and golden (yellow), or Black and White all go nicely together.
Porsche Boxster
The Union Jack looks really cool on either the roof or the hood of this car. But being that my family color is blue, I thought that perhaps a Scottish flag might fit better.
Scottish Flag
I always find the Dodge Challenger an agressive and smart looking car.
The Subaru Baja is also a nice car.
Go to start of metadata
Matching IPTC to Dublin Core:
http://metadatadeluxe.pbworks.com/w/page/25784393/W3C,-IPTC,-Dublin-Core,-and-Adobe
This is an introduction to how this metadata is stored.
http://wiki.gbif.org/gbif/wikka.php?wakka=MMMetaData
XMP Sidecar Files
A sidecar file is an alternative to storing the metadata directly in the image file itself by instead storing the data in a separate .xmp file with the same base name as the photo. Sidecars are typically used in cases where the file format of the photo doesn't directly support embedding metadata or in cases when the image file should not be edited directly. It should be noted that very few programs support the reading the xmp sidecar files, most will default to reading and writing to the photo directly.
Gracefully copied from http://www.earlyinnovations.com/photolinker/xmp-sidecar-files.html
Note: that side car files are separate files from the photos so if that photo were to be archived it would need to form a package of two files a sidecar file and the main photo image.
Embedded Metadata
Exif
http://www.digicamhelp.com/glossary/exif-data/
http://www.opanda.com/en/iexif/
http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html
http://www.stuffware.co.uk/cheese/
IPTC
http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf
The funky Dublin Core Metadata Schema
http://www.iptc.org/std/Iptc4xmpCore/1.0/specification/Iptc4xmpCore_1.0-spec-XMPSchema_8.pdf
http://www.prismstandard.org/about/relationships.asp
Ok, so the items which can be recorded in Exif data spots, might not be able to be recorded in ITCP spots and vise versa. That is that some elements like copyright holder or photographer can be recorded in the ITCP data but not in the Exif data. This means that there is not 100% correspondence between the two sets. We can not choose to use one and ignore the other. When we throw XMP into the mix there are attentional things which can be recorded in XMP but not in either of the other sets. Additionally, XMP is in its own file, not embedded. Dublin Core (DC) is also a set of options for metadata. They are not embedded in the photo itself, rather in a way it is a way to organize a database of metadata about objects. REAP uses DC. DC is extensible, that is we can move embedded metadata (or sidecars) from photos into the REAP database's metadata structure. But then what happens when the photo is removed from the REAP container. Does the metadata travel with it?
Here is a clip gracefully copied from http://www.earlyinnovations.com/photolinker/annotation-philosophy.html
Many popular websites and applications allow you to annotate your photos by adding keywords, a description, a title, a location, a list of the people in the photograph and many other tags. These websites and applications generally suffer from two major deficiencies:
Annotations are often exclusively added to a propriety database, and not written back to the photo. This means that unless the software or website is still available in, say, 50 years, the annotations will be completely lost.
Programs that do write the annotations directly to the image file usually corrupt existing tags or write partial information.
PhotoLinker solves both of these issues.
There are several things to think about with respect to photos and metadata.
1. The What: this is the elements of the metadata's data. The "Who", "What", "Where", "When", "Why and "How" of the photo.
2. The How: The technical storage of the metadata. Where is all of this data stored.
These two issues are discussed in their own child pages. There is a lot to say on each one.
In brief the What tries to answer the question What kind of meta-data should or can be collected?
Whereas the How tries to answer the question What should or can be be done with this meta-data?
File Naming convention: http://www.controlledvocabulary.com/imagedatabases/filenaming.html
Keywords: http://www.controlledvocabulary.com/metalogging/ck_guidelines.htm
A Minimal Set of meta-data to strive to collect:
Photo ID Number: ______________________________
Collection:____________________________________
Sub-Collection:_________________________________
Who (photographer): ____________________________
Who (subject): _________________________________
Who (subject): _________________________________
Who (subject): ________________________________
Who (subject): ________________________________
Who (subject): ________________________________
People group:_________________________________
When (was the photo taken): _______________________
Where (Country): _______________________________
Where (City): _________________________________
Where (Place): ________________________________
What is in the Photo: ____________________________
What is in the Photo: ____________________________
What is in the Photo: ____________________________
Why was it taken (Event):_________________________
Description:____________________________________
Who (provider): ________________________________
Who (provider): ________________________________
Who (provider): ________________________________
Who (provider): _______________________________
While I was in Mexico, I was walking to the store with a friend, who is also a fellow linguistics student. He was telling me a story. In the course of that story a naturally occurring sentence flowed “out of his mouth”. After he said that sentence I let him finish his thought and I asked him if the sentence was gramatical.
Here is the sentence:
Yesterday, I saw the latin version of one of my friend’s husbands in Sorinana.Sorinana chain of stores in Mexico.
My contention was that the “s” on “husbands” was ungrammatical.
Of course, if the sentence is read:
Yesterday, I saw the latin version of one of my friend’s husband in Sorinana.
The sentence sounds awkward. Perhaps it is not a well formed sentence. But is it ungrammatical? What is the violation which makes the sentence sound awkward? Is it the constrained unit [one of my friend’s] which is embedded in another gramatical unit, which is apparently unconstrained [the latin version of…]?
We tried to move the gramatical units around and did not find a satisfying solution.
Yesterday, I saw the latin version of the husband of one of my friends in Soriana.
Yesterday, I saw the latin version of one of my friend’s husband in Soriana.
Yesterday, I saw a man who looked like my friend’s husband in Soriana.
Yesterday, I saw a man who could have passed as the latin version of one of my friend’s husband in Soriana.
Yesterday, I saw a man who could have passed as the latin version of the husband of one of my friends in Soriana.
Yesterday, in Soriana, I saw a latino version of my friend’s husband.
Yesterday, I saw a the latin version of the husband of one of my friends in Soriana.
Yesterday, I saw in Soriana the latin version of the husband of one of my friends.
All this variation in options of for information ordering has led me to ask three questions of English:
In a recent (2010-2011) Language Documentation Project we decided to also collect GIS data (GPS Coordinates), about our consultants (place of origin and place of current dwelling), about our recording locations and for Geo-tagging Photos. We used a Garmin eTrex Venture HC to collect the data and then we compared this data with GIS information from Google maps and the National GIS information service. This write up and evaluation of the Garmin eTrex Venture HC is based on this experience.
Continue reading
I was recently looking at licenses for databases and discovered the ODbL license. This license was pioneered by the OpenStreetMap Project. I was reading their introduction to why the change was needed. This introduction outlined what the change was, what the change would allow them to do, who agreed, who disagreed, what the cost of the change would be, among other things. I thought it was a very open, engaging and confidence building way to move a group of volunteers through change. It allows for more kinds (also different kinds) of product use. It is well worth the look at not only if you are interested in the open licensing of data in databases and why CC-BY-SA and CC0 licenses do not work for data [also as PDF], but also how they are answering the questions of the community as they are moving the community through change.
© 2005-2025 Hugh Paterson III All Rights Reserved.
By submitting a comment here you grant this site a perpetual license to reproduce your Words, Name & Website URL in attribution.
Details of your viewing experience maybe retained and used. -- Copyright notice by Blog Copyright