summaryrefslogtreecommitdiff
path: root/doc/design/metadata
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus <Jimmy@web>2014-02-25 09:57:09 +0000
committerGravatar admin <admin@branchable.com>2014-02-25 09:57:09 +0000
commitecffc15ff50493c6d143f57e057ef96804cccec9 (patch)
tree269d68eb413dddd68f529d372ee07aeb6ee08d62 /doc/design/metadata
parent5262abce37c9310d64d70f75965ea76adaed9196 (diff)
Added a comment
Diffstat (limited to 'doc/design/metadata')
-rw-r--r--doc/design/metadata/comment_3_ee850df7d3fa4c56194f13a6e3890a30._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/design/metadata/comment_3_ee850df7d3fa4c56194f13a6e3890a30._comment b/doc/design/metadata/comment_3_ee850df7d3fa4c56194f13a6e3890a30._comment
new file mode 100644
index 000000000..f77cd8611
--- /dev/null
+++ b/doc/design/metadata/comment_3_ee850df7d3fa4c56194f13a6e3890a30._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
+ nickname="Jimmy"
+ subject="comment 3"
+ date="2014-02-25T09:57:09Z"
+ content="""
+actually in your mp3 example you could have ....
+
+ATTRIBUTE=sample_rate, VALUE=22100, UNIT=Hertz
+
+another example use case is to always be consistent with the AVU order then you could stick in ntriples from RDF to do other cool things by looking up various linked data sources -- see http://www.w3.org/2001/sw/RDFCore/ntriples/ and http://www.freebase.com/, actually this would be quite cool if git-annex examined the mp3's id3 tag, the created an ntriple styled entry can be automatically parsed with the web-based annex gui and automatically pull in additional meta-data from the likes of freebase. I guess the list of ideas can just only get bigger with this potential metadata capability.
+"""]]