Comments (7)
Just for clarification: Is the main difference between IPTC and DwC Geography
terms is that IPTC has distinction between Location created and Location Shown
and DwC does not talk about it?
Original comment by [email protected]
on 27 Aug 2012 at 9:22
from ac.
AC is a vocabulary profile for media. There is a leading organization that
defined a geographical vocabulary for media, the IPTC. This standard is the one
that the tools to manipulate media commonly support (through xmp, which refers
to IPTC for geography and other subject matters).
Thus, media like images ARE using these terms, whether tdwg endorses that or
not. Forcing tdwg-followers to use DwC geography terms would mean that they
have to duplicate some existing xmp-based metadata into DwC metadata. And the
next time metadata are changed in a media management software, the DwC data
will be outdated, unless someone is really watchfull...
I vote strongly against this proposal...
Original comment by [email protected]
on 27 Aug 2012 at 10:42
from ac.
Vijay- I believe that is the main difference.
Original comment by morris.bob
on 28 Aug 2012 at 2:07
from ac.
Gregor:
I keep vacillating on this. I accept your point, but doubt that we'll see
people use them very much, however well supported in IPTC compliant tools. A
reasonable tool that extracts metadata from an IPTC compliant tool still has to
meld that metadata with quite a few other AC terms.
Original comment by morris.bob
on 28 Aug 2012 at 2:15
from ac.
I am would leave them in for discussion, but not necessarily with the
recommendation that we will eliminate them. I think distinguishing between
Location Shown and LocatedCreated? is important, and thus I think we should
still list Location Shown in AC, since it is not in DwC. in my mind this means
we need to have our own term definition of LocationShown?, which means keep it
in IPTC. ...
I noted your comment in the wiki Bob, that you think it is unlikely that people
will use these fields (or IPTC?). LIFE really struggled with this issue - and
needed these separate fields repeatedly. So keeping Location Shown is
important. And although we didn't use IPTC, unless DwC provides a mapping to
IPTC (which I didn't see), eliminating the existing IPTC terms creates a
barrier for organizations seeking to map theirs to AC. In another note - in the
overarching comment, your refer to Location Shown, Located Created, and to
"Location Acquired." Where is Location Acquired defined? Based on the sentence
before it, are you really meaning Location Created instead of Location Acquired?
"Location created and Location shown are separated in the current version of
IPTC, and the metadata working group (MWG 2010)1 also recommends this. We will
follow this, to support the expected future increase of automatic GPS based
coordinate recording in recording devices. As a special case, the AC group
recommends to change the semantics of location shown in the case of
biodiversity specimens, where the original location may differ from the current
location at which the specimen is held in a collection. In this case,
LocationShown? should EXCLUSIVELY refer to the location where a specimen was
originally collected (gathering or sampling location). Use LocationCreated? to
express the location where the media was created (a specimen was digitized).
All geography terms from the DarwinCore? version of 9 Dec 2009 are deemed
included in the Core Layer. Specifically, this includes exactly those which are
declared by DarwinCore? to be in DarwinCore? Class Location. Note that
dwc:locality may be used, but as applied to media this term may be ambiguous as
to whether it applies to the location depicted or the location at which the
media was created. When disambiguating information is available, it is better
to use the terms Location Shown and Location Acquired."
Also, the language has changed in one sentence (where I put all caps), and I
think I disagree with it. LocationShown? should not refer "exclusively" to the
location where a specimen was originally collected (gathering or sampling
location.) We had also talked about the case where it could be a satellite
image or other long-distance shot, which shows an image of a location at a
distance from where the camera is located. I would add to the pink sentence.
"For biodiversity specimens,....". Then add a sentence, "For habitat and other
shots ..." We have to remember that not everyone is dealing with just
specimens, but also habitat shots, etc...So we shouldn't limit ourselves here.
(Also, I think this should be not in the overarching paragraph, but under the
term's definition.)
Hope this helps.
Original comment by [email protected]
on 29 Aug 2012 at 4:03
from ac.
Original comment by morris.bob
on 25 Nov 2012 at 11:59
- Added labels: Component-Terms
from ac.
The concensus seems to be to leave them in, so I am resolving this as WontFix
Original comment by morris.bob
on 8 Jun 2013 at 7:31
- Changed state: WontFix
- Added labels: Milestone-Release1.0
from ac.
Related Issues (20)
- Proposal to create a controlled vocabulary for content description HOT 6
- Investigate GUANO audio metadata standard HOT 3
- New term proposal: ac:Digital3DResource HOT 5
- Do the renaming to "Audio-visual Core" in github, website etc HOT 8
- Update ac.tdwg.org to make use of new TDWG branding HOT 2
- Example for identification keys/tools HOT 8
- rs.tdwg.org/ac redirection issue for `variant/2020-10-13` HOT 2
- Table cell boundaries not visible under new website theme HOT 4
- Error in definition of the subjectPart concept scheme HOT 3
- Implementation of subjectPart and subjectOrientation in Myriatrix HOT 6
- w3c FragmentSelector to AC terms? HOT 1
- Term change: correct reference to `ac:accessURI` in `ac:serviceExpectation` HOT 4
- Typo in dc:format HOT 1
- reference to Audubon Core in links on AC page HOT 1
- Proposal to add new terms ac:filterLowPass and ac:filterHighPass (from GUANO) HOT 4
- Discuss how to better promote AudioVisual core
- Change the label "Normative URI" to "Term IRI"
- Change the label "Term version URI" to "Term version IRI"
- AC List of terms does not link to the Executive Decisions
- AC List of terms does not explicitly give the type of its terms
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ac.