[08:48:42 CST(-0600)] <Justin_o> jhung, danaayotte_: Cindy and I would like to use Bootstrap for the metadata demo.. any concerns with that?
[08:49:31 CST(-0600)] <jhung> Justin_o, cindyli: I have no problems with that. Any reason Bootstrap over Foundation?
[08:51:23 CST(-0600)] <Justin_o> jhung: documentation.. i'd like to go with the one that easier to get started with.. i think that's basically it
[08:51:32 CST(-0600)] <Justin_o> cindyli: any other reason
[08:51:34 CST(-0600)] <Justin_o> ?
[08:54:20 CST(-0600)] <colinclark> LESS's Node-based toolchain is appealing to me, too.
[08:58:33 CST(-0600)] <jhung> Justin_o, cindyli - I'm fine with Bootstrap. I mean we have to start somewhere to figure out which one of these frameworks to adopt for our demos.
[09:19:02 CST(-0600)] <Justin_o> jhung: true.. i guess we can see from our usage if we need the extra features too
[09:26:30 CST(-0600)] <Justin_o> jhung: is there some subset of bootstrap i should include.. or should i just bring in the whole distribution
[09:27:38 CST(-0600)] <Justin_o> jhung, cindyli: maybe we can just use the CDN distribution for now.. so we don't clutter the repo. what do you think?
[09:28:37 CST(-0600)] <cindyli> Justin_o: what is "CDN distribution"….
[09:28:47 CST(-0600)] <Justin_o> cindyli: http://getbootstrap.com/getting-started/#download-cdn
[09:28:53 CST(-0600)] <Justin_o> basically just hosted versions
[09:29:21 CST(-0600)] <Justin_o> so you just use a url to a web resource
[09:29:30 CST(-0600)] <Justin_o> if you don't have internet though, it won't work
[09:30:13 CST(-0600)] <cindyli> i see. +1
[09:30:22 CST(-0600)] <Justin_o> okay.. cool. thanks
[09:34:01 CST(-0600)] <jhung> Justin_o sounds fine to me.
[09:34:19 CST(-0600)] <Justin_o> jhung: bootstrap has aria roles in there examples http://getbootstrap.com/components/#btn-groups-toolbar
[09:34:40 CST(-0600)] <jhung> Justin_o, cindyli, anastasiac - do you have time to chat Metadata encoding?
[09:34:48 CST(-0600)] <Justin_o> jhung: sure
[09:34:48 CST(-0600)] <cindyli> sure
[09:34:55 CST(-0600)] <anastasiac> any time
[09:34:56 CST(-0600)] <jhung> Skype okay?
[09:35:27 CST(-0600)] <jhung> Actually. Let'd do it in the channel.
[09:35:56 CST(-0600)] <jhung> I have 2 questions about metadata encoding Justin_o, anastasiac, cindyli
[09:36:54 CST(-0600)] <jhung> Question 1: How is metadata handled for multiple media files in a single HTML document?
[09:37:32 CST(-0600)] <jhung> Question 2: How can we support title and descriptions for each media file? Is there metadata to handle that?
[09:39:01 CST(-0600)] <anastasiac> jhung, regarding #1: there are different ways this could be handled with schema.org micro formats. Since the metadata is embedded within the markup, it could be a) all up at the beginning of the document, attempting to describe the document as a whole, or b) scattered throughout the document, describing different bits. The element containment defines the scope of the metadata. Does that make sense?
[09:39:52 CST(-0600)] <Justin_o> anastasiac: if it's the document as a whole would that be in the body or the html tag?
[09:40:02 CST(-0600)] <jhung> anastasiac: Ah cool. I think currently our metadata editing is working on the element level - so probably option b.
[09:40:16 CST(-0600)] <anastasiac> Justin_o, I believe it would be on or inside the body tag
[09:40:26 CST(-0600)] <Justin_o> anastasiac: thanks
[09:40:41 CST(-0600)] <anastasiac> personally, I think option b provides much more power, providing search engines use it accordingly
[09:40:47 CST(-0600)] <jhung> Justin_o: http://www.w3.org/wiki/WebSchemas/Accessibility has examples toward the bottom of the page.
[09:41:34 CST(-0600)] <jhung> anastasiac: the examples linked above actually shows option b you mentioned. Cool.
[09:41:53 CST(-0600)] <anastasiac> jhung, the bottom of that page also has links to more examples
[09:42:02 CST(-0600)] <jhung> Thanks.
[09:43:46 CST(-0600)] <anastasiac> jhung, regarding question #2, I'm pretty sure there are other schema.org micro formats that would be more than suitable for title and description
[09:43:55 CST(-0600)] <anastasiac> searching...
[09:44:18 CST(-0600)] <anastasiac> jhung: http://schema.org/docs/schemas.html
[09:44:31 CST(-0600)] <anastasiac> they use an inheritance scheme
[09:44:40 CST(-0600)] <anastasiac> so probably creative work has the basics like title
[09:44:51 CST(-0600)] <anastasiac> or event Thing
[09:45:06 CST(-0600)] <anastasiac> but if you search, say, videoObject, it will tell you where things are inherited from
[09:45:43 CST(-0600)] <anastasiac> jhung, I think that if we're using the schema.org version of the a11y md, we might as well use other schema.org micro formats for other md; Justin_o, would you agree?
[09:47:18 CST(-0600)] <Justin_o> anastasiac, jhung: i don't know if i fully understand but it sounds reasonable
[09:47:43 CST(-0600)] <anastasiac> 
[09:48:44 CST(-0600)] <jhung> So I guess the trick now is to find the schema.org metadata that will encode all the bits of metadata we're dealing with for the demo anastasiac.
[09:49:09 CST(-0600)] <anastasiac> jhung, should be pretty easy
[09:49:18 CST(-0600)] <anastasiac> it looks like Thing has basics like name, description
[09:49:27 CST(-0600)] <anastasiac> http://schema.org/Thing
[09:50:44 CST(-0600)] <jhung> anastasiac: cool. And I assume there should be a way of encoding alternative / equivalence relationships? i.e. Caption is an alternative to audio for a video.
[09:51:59 CST(-0600)] <anastasiac> ah, interesting, jhung. I was going to say "that's provided by the a11y md schema at http://www.w3.org/wiki/WebSchemas/Accessibility" but it's not
[09:52:05 CST(-0600)] <anastasiac> they seem to have left that out of this round of the draft
[09:52:13 CST(-0600)] <anastasiac> but we should go ahead and use the elements
[09:52:16 CST(-0600)] <anastasiac> I'll find a reference
[09:52:34 CST(-0600)] <anastasiac> jhung, have a look here: http://www.a11ymetadata.org/the-specification/
[09:52:40 CST(-0600)] <anastasiac> there's hasAdaptation and isAdaptationOf
[09:52:52 CST(-0600)] <anastasiac> that's how you encode the relationship
[09:53:37 CST(-0600)] <anastasiac> so on a video, you could add a property called "hasAdaptation" whose value is an url referencing a caption
[09:53:43 CST(-0600)] <anastasiac> and vice versa
[09:53:46 CST(-0600)] <anastasiac> make sense, jhung?
[09:54:24 CST(-0600)] <anastasiac> also, jhung I cannot recommend strongly enough that we use the accessMode property described on this page, even though it's only "under consideration"
[09:54:35 CST(-0600)] <jhung> that works anastasiac, but it doesn't offer much granularity. I.e. it doesn't give you an option of saying what modality the adaptation is for…
[09:55:24 CST(-0600)] <jhung> anastasiac: ok. We'll be sure to support the values under accessMode.
[09:56:06 CST(-0600)] <anastasiac> jhung, that's true. Some info can be inferred from other md, e.g. if it's a caption, it's pretty obvious
[09:56:40 CST(-0600)] <anastasiac> if we encounter use cases where the md is inadequate, well, then we have good ammunition to take back to the people who developed the schema to tell them it's not good enough
[09:56:40 CST(-0600)] <jhung> anastasiac: I was thinking of caption too, but caption can be for visuals as well for audio.
[09:57:01 CST(-0600)] <anastasiac> jhung, when would captions be used for visuals, and why?
[09:57:44 CST(-0600)] <jhung> i.e. a video can contain a segment with a billboard in a foreign language. Caption would be needed.
[09:58:06 CST(-0600)] <anastasiac> hm. I'd call that a subtitle, not a caption
[09:58:37 CST(-0600)] <anastasiac> but still. hm..
[09:58:41 CST(-0600)] <anastasiac> it's a good point
[09:59:10 CST(-0600)] <anastasiac> well, we'll just have to do the best we can within the spec as it is, and identify the sticking points so that we can contribute to improvement of the spec
[10:00:08 CST(-0600)] <jhung> Justin_o, cindyli - so we'll have to figure out what metadata we'll need to be encoding. Hopefully danaayotte_ and I will have something we can talk about this afternoon.
[10:00:54 CST(-0600)] <Justin_o> jhung: sounds good
[11:01:07 CST(-0600)] <colinclark> Justin_o: This was exactly the sort of thing I was thinking of when I speculated about simple document management for our authoring demo last week: http://pouchdb.com/
[11:01:43 CST(-0600)] <colinclark> I'm sure we're not quite ready for it, but it looks like when we are, there are some good client-side persistence options available to us
[11:01:49 CST(-0600)] <colinclark> that can ultimately sync with a server-side data store later
[11:03:25 CST(-0600)] <Justin_o> colinclark: that's interesting
[11:03:55 CST(-0600)] <colinclark> Seems to me we'd just want to make a new DataSource for Pouch, and we'd be ready to rock with simple client-side persistence
[11:44:31 CST(-0600)] <Justin_o> colinclark: looks doable
[13:34:45 CST(-0600)] <Justin_o> jhung, danaayotte_: do you have the designs for the demo.
[13:34:51 CST(-0600)] <Justin_o> ?
[13:35:58 CST(-0600)] <jhung> Justin_o: almost there. Give us 30 mins?
[13:36:28 CST(-0600)] <Justin_o> jhung: great thanks
[13:56:37 CST(-0600)] <jhung> Justin_o, cindyli, michelled, vjoanna, colinclark, anastasiac: Here is the current revision of the metadata demo. https://www.dropbox.com/s/o4mjq9uiz062x16/FLOE-metadata-design-1b.pdf
[13:57:11 CST(-0600)] <jhung> Justin_o, cindyli - we'll talk about it when danaayotte_ gets back. Feel free to go over it before we chat.
[13:57:26 CST(-0600)] <anastasiac> "flO.E.R" – nice
[13:57:51 CST(-0600)] <cindyli> ok. thanks, jhung
[13:59:24 CST(-0600)] <Justin_o> jhung: thanks
[14:00:10 CST(-0600)] <jhung> colinclark: I just sent this link after you left - it's the current revision of the metadata demo. https://www.dropbox.com/s/o4mjq9uiz062x16/FLOE-metadata-design-1b.pdf
[14:01:11 CST(-0600)] <colinclark> cool, yep i saw it
[14:16:27 CST(-0600)] <colinclark> jhung1: I wonder if it might make sense to make the instruction text/icons a little less prominent in the metadata demo? Maybe just as some kind of status bar or tooltip or something, rather than taking screen real estate away from the editor itself?
[14:17:48 CST(-0600)] <jhung1> colinclark: that's a good thought. Would be less distracting in a demo situation.
[14:18:53 CST(-0600)] <colinclark> yep, exactly
[14:26:47 CST(-0600)] <jhung1> Sorry colinclark, anastasiac - the annotations in the PDF I linked to earlier is a bit of a mess. Sorry.
[14:26:59 CST(-0600)] <colinclark> no worries
[14:47:02 CST(-0600)] <jhung1> colinclark: would you think it would be okay if the video in the metadata demo not be playable? (i.e. not use a video player).
[14:51:35 CST(-0600)] <colinclark> That would be a bit awkward
[14:51:35 CST(-0600)] <colinclark> is there a reason for taking that approach?
[14:55:11 CST(-0600)] <jhung1> Justin_o - care to explain to colinclark the issue?
[15:00:17 CST(-0600)] <danaayotte_> colinclark do you think the editor window needs more real estate in the authoring page as well?
[15:00:47 CST(-0600)] <Justin_o> jhung1, colinclark: actually i was suggesting that we use the plain video tag instead of the fluid videoplayer
[15:01:19 CST(-0600)] <danaayotte_> colinclark: we were thinking it makes sense to have less real estate there since the focus is on metadata creation
[15:03:56 CST(-0600)] <colinclark> You guys would know best how to use the available screen real estate
[15:04:03 CST(-0600)] <colinclark> and I like that this is clearly framed as a demo
[15:04:15 CST(-0600)] <colinclark> but on the other hand, we also want these things to have the potential to be useful as they grow
[15:04:30 CST(-0600)] <colinclark> the components that make up the metadata authoring UX, for example
[15:04:56 CST(-0600)] <colinclark> presumably, we'll want them to fit into a workflow where editing is indeed the primary activity of the user
[15:05:10 CST(-0600)] <colinclark> what do you think about all this, danaayotte_?
[15:05:15 CST(-0600)] <colinclark> Justin_o: Can you elaborate on why?
[15:08:03 CST(-0600)] <danaayotte_> colinclark: to clarify, you mean metadata authoring, right? not content editing in the editor window?
[15:08:30 CST(-0600)] <danaayotte_> as in …a workflow where metadata authoring is indeed the primary activity of the user?
[15:08:52 CST(-0600)] <colinclark> no
[15:08:54 CST(-0600)] <colinclark> the opposite
[15:08:56 CST(-0600)] <colinclark>
[15:08:58 CST(-0600)] <danaayotte_> wow, ok
[15:09:03 CST(-0600)] <colinclark> I'm saying...
[15:09:07 CST(-0600)] <Justin_o> colinclark: sure. 1) is for simplification which includes simpler markup for viewing source and trying to see the metadata 2) there didn't seem to be a playable view yet so it seemed like a lot of trouble when all we want is the markup. although this might be changing.. and i'm sort of thinking that we actually want something else in the editor now.. that
[15:09:07 CST(-0600)] <Justin_o> links back to the metadata entries..
[15:09:08 CST(-0600)] <colinclark> make a nice demo
[15:09:11 CST(-0600)] <colinclark> but think beyond the demo
[15:09:13 CST(-0600)] <danaayotte_>
[15:09:19 CST(-0600)] <danaayotte_> got it
[15:09:49 CST(-0600)] <colinclark> I should be really clear
[15:09:56 CST(-0600)] <colinclark> When we make demos like this, we're not just making demos
[15:10:00 CST(-0600)] <colinclark> we're starting
[15:10:08 CST(-0600)] <colinclark> we're taking a little step forward to doing something real
[15:10:13 CST(-0600)] <colinclark> that real users would use in real authoring tools
[15:10:23 CST(-0600)] <danaayotte_> yes
[15:10:27 CST(-0600)] <colinclark> So we've definitely got a super-limited amount of time for our first "slice"
[15:10:38 CST(-0600)] <colinclark> and we can make lots of trade-offs and compromises as need to get started
[15:10:54 CST(-0600)] <colinclark> but we do want to grow these things for real
[15:11:34 CST(-0600)] <colinclark> Justin_o: I think you'll need to elaborate a bit more
[15:11:43 CST(-0600)] <colinclark> I can sort of vaguely see a set of expectations about how you'll implement it
[15:11:49 CST(-0600)] <colinclark> but it's pretty fuzzy
[15:11:59 CST(-0600)] <colinclark> to me
[15:12:06 CST(-0600)] <colinclark> undoubtedly, it's much clearer to you
[15:13:39 CST(-0600)] <colinclark> I guess the key thing I'm unclear on is the "for viewing source and trying to see the metadata" part
[15:13:42 CST(-0600)] <jhung1> colinclark: that helps a lot.
[15:14:44 CST(-0600)] <Justin_o> colinclark: mostly i'm just concerned about simplification in light of the time we have.. if we weren't going to actually have a functional video it didn't make sense to use the video player.. there are some other limitations as well though, like playing audio descriptions likely isn't supported
[15:14:55 CST(-0600)] <jhung1> Basically we want anyone who sees our demo to instantly understand how metadata can be plugged into their application. So the way we have it arrange right now doesn't strongly convey that because "real" content applications have larger emphasis on content creation as the workflow, not the metadata. So we have to marry ourselves into that context.
[15:15:02 CST(-0600)] <jhung1> ^colinclark about right?
[15:15:40 CST(-0600)] <Justin_o> colinclark: the viewing metatdata part was about the requirement to view source.. the extra markup will add clutter for sure.. perhaps it won't be too bad though
[15:15:50 CST(-0600)] <colinclark> ah, I see what you mean, Justin_o
[15:16:00 CST(-0600)] <colinclark> so the "View HTML" button lets someone see the underlying markup
[15:16:13 CST(-0600)] <Justin_o> colinclark: yes
[15:16:40 CST(-0600)] <colinclark> the point being that they can see what kind of effect all our metadata-editing components can have on the resource itself?
[15:17:13 CST(-0600)] <colinclark> jhung1: yep, pretty much
[15:17:50 CST(-0600)] <Justin_o> colinclark: the metadata is also encoded into the document
[15:17:54 CST(-0600)] <colinclark> right
[15:18:00 CST(-0600)] <colinclark> Okay, so I think there are two sides to this, Justin_o
[15:18:06 CST(-0600)] <colinclark> Now, and later
[15:18:26 CST(-0600)] <colinclark> Now, you're saying "there is no view mode"
[15:19:08 CST(-0600)] <colinclark> i.e. there is-for this first preliminary two week sprint-no way to view the content you've been editing in the editor
[15:19:25 CST(-0600)] <colinclark> in which case, I agree, a Video Player instance won't be particularly useful
[15:19:45 CST(-0600)] <colinclark> Presumably in our second sprint, we might add some kind of view mode
[15:20:11 CST(-0600)] <colinclark> When we get to that point, I guess we might want to think of the content that the user is editing as a kind of "template"
[15:20:44 CST(-0600)] <colinclark> perhaps with simplified semantics that make it easy to author without having to worry about the details of a more complex component
[15:21:03 CST(-0600)] <colinclark> and then, at "view time," we'd be able to inject components using the Renderer
[15:21:21 CST(-0600)] <Justin_o> colinclark: yes.. that makes sense
[15:22:31 CST(-0600)] <colinclark> Thinking way into the future, where we have some kind of really great authoring tool, that approach need not preclude a user opening up the details of a particular component, say the Video Player, and editing the details of its template, too
[15:22:57 CST(-0600)] <colinclark> but you might imagine an expanding level of detail, starting with much more high-level, meaningful semantics
[15:23:02 CST(-0600)] <colinclark> like "this is my navigation area"
[15:23:09 CST(-0600)] <colinclark> and "I want a video player over here"
[15:23:35 CST(-0600)] <colinclark> anyway, I'm undoubtedly getting ahead of myself quite a bit 
[15:23:41 CST(-0600)] <Justin_o> colinclark: right, where you an drill down to more detal
[15:23:47 CST(-0600)] <colinclark> yup, exactly
[15:24:18 CST(-0600)] <Justin_o> colinclark: cool... so for this go round.. plain html5 video tags ?
[15:24:27 CST(-0600)] <colinclark> yep
[15:24:30 CST(-0600)] <colinclark> seems fine to mee
[15:24:32 CST(-0600)] <colinclark> me
[15:24:49 CST(-0600)] <Justin_o> colinclark: cool thanks
[15:25:07 CST(-0600)] <colinclark> no problem
[15:25:10 CST(-0600)] <colinclark> sorry i was so confused
[15:25:54 CST(-0600)] <colinclark> danaayotte_, jhung1: I guess, philosophically, our approach is to minimize the user's awareness of "metadata" as much as is absolutely possible
[15:26:17 CST(-0600)] <colinclark> and wherever they do have to interact with it, it should be as smoothly part of the process of them just making stuff and being creative
[15:26:58 CST(-0600)] <danaayotte_> thanks colinclark, that helps clarify
[15:27:13 CST(-0600)] <colinclark> I was thinking about techniques for this the other day, since it's a really hard problem
[15:27:31 CST(-0600)] <colinclark> The new version of Pages has this "opportunistic structure" mode editing documents
[15:27:45 CST(-0600)] <Bosmon> colinclark - "Pages"?
[15:28:09 CST(-0600)] <colinclark> We still need to get you that iCloud account, Bosmon
[15:28:17 CST(-0600)] <Bosmon> It seems impossible
[15:28:33 CST(-0600)] <Bosmon> I went through the full rigmarole and was still told that "this Apple ID cannot be used for an iCloud account"
[15:28:42 CST(-0600)] <Bosmon> Because of course I have not paid them MONEY for THINGS
[15:28:53 CST(-0600)] <colinclark> that doesn't make any sense, but Justin_o probably knows more about these things
[15:28:54 CST(-0600)] <Justin_o> Bosmon: did you try this site https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/wa/createAppleId
[15:29:01 CST(-0600)] <colinclark> Pages tries to encourage you to use structural styles as you're editing
[15:29:11 CST(-0600)] <Bosmon> Justin_o - yes
[15:29:14 CST(-0600)] <Bosmon> I have an Apple ID
[15:29:20 CST(-0600)] <colinclark> what a url!
[15:29:21 CST(-0600)] <Bosmon> It still does not permit me to use iCloud
[15:29:29 CST(-0600)] <colinclark> michelled remembers URLs like this very well
[15:29:35 CST(-0600)] <Bosmon> They can detect that I am not DEVOUT
[15:29:44 CST(-0600)] <Bosmon> Because I have no APPLE DEVICES
[15:29:58 CST(-0600)] <colinclark> Pages shows you text style pane as you're editing
[15:30:12 CST(-0600)] <danaayotte_> colinclark could you share a screenshot or two?
[15:30:16 CST(-0600)] <Justin_o> Bosmon: you can't use iCloud at all.. or just not the iWork suite?
[15:30:20 CST(-0600)] <colinclark> and sees, for example, if you've changed what it thinks is the "body style"
[15:30:26 CST(-0600)] <Bosmon> Justin_o - no iCloud
[15:30:35 CST(-0600)] <colinclark> and sort of vaguely prompts you to update it
[15:30:43 CST(-0600)] <colinclark> danaayotte_: It might be easier to try it yourself
[15:30:53 CST(-0600)] <Bosmon> colinclark - I'd appreciate some screenshots
[15:31:07 CST(-0600)] <colinclark> I'm trying to figure out quite how to do this
[15:31:13 CST(-0600)] <colinclark> I guess I might have to make a video
[15:31:19 CST(-0600)] <colinclark> to be clear, I think it's pretty unsuccessful
[15:31:34 CST(-0600)] <colinclark> in that it keeps distracting me as I write
[15:31:37 CST(-0600)] <colinclark> but it is trying something that Word typically completely hides
[15:31:44 CST(-0600)] <Bosmon> So is "Eufloria"... it is still a valuable source of UI ideas : P
[15:31:57 CST(-0600)] <Justin_o> Bosmon: http://support.apple.com/kb/HT4436?viewlocale=en_US&locale=en_US
[15:32:22 CST(-0600)] <Bosmon> Justin_o - yes, I am aware of this
[15:32:29 CST(-0600)] <Bosmon> As you read the page, you find the description of the requirements
[15:32:43 CST(-0600)] <Bosmon> Which I suggest you do
[15:32:54 CST(-0600)] <Justin_o> Bosmon: so yes you need to create it form an apple device.. but that should be all...
[15:33:17 CST(-0600)] <Bosmon> Justin_o - yes - but I have none - and I believe that each such device must be associated with a unique Apple ID, no?
[15:33:25 CST(-0600)] <Bosmon> I imagine that Apple is no better about device sharing than Google
[15:33:49 CST(-0600)] <colinclark> not without the GPII!
[15:33:53 CST(-0600)] <Justin_o> Bosmon: i think you can just create a new account on a Mac
[15:33:59 CST(-0600)] <Justin_o> then you can delete that user account
[15:34:08 CST(-0600)] <Bosmon> Justin_o - ok
[15:34:21 CST(-0600)] <colinclark> what's the best way to share a few casual screenshots?
[15:34:30 CST(-0600)] <Bosmon> colinclark - attachments to the wiki?
[15:34:35 CST(-0600)] <colinclark> stick it in the wiki, or is there some kind of pastie equivalent?
[15:34:46 CST(-0600)] <Justin_o> i'm heading out now.. good luck with your iCloud account Bosmon
[15:34:55 CST(-0600)] <Bosmon> Well
[15:35:00 CST(-0600)] <Bosmon> Someday I will run into someone with a Mac
[15:35:02 CST(-0600)] <Bosmon>
[15:35:15 CST(-0600)] <colinclark> we'll do it in person in Madison, Bosmon
[15:35:22 CST(-0600)] <colinclark> I'll set you up an account on my macbook
[15:35:26 CST(-0600)] <Bosmon> great
[15:35:32 CST(-0600)] <Bosmon> Then I will be ENFRANCHISED!
[15:35:36 CST(-0600)] <colinclark> and then you can hook it up to your apple id
[15:36:36 CST(-0600)] <colinclark> jhung1: is there a good page on the wiki for this kind of thing?
[15:36:55 CST(-0600)] <colinclark> research or comparative analysis of "metadata" editing?
[15:48:05 CST(-0600)] <jhung1> colinclark: Not that I know of.