Re: Video syntax

[David Chambers]

Hi folks,

Sorry to revive an old thread, but I thought I'd mention that Mango—as of an
hour ago—now also translates Vimeo video links to appropriate markup.

See, for example,
http://davidchambers.name/blog/di-fara-pizza-documentary/m/ (strip the "m/"
to see the rendered version).

The
relevant line is `[Di Fara pizza documentary][3]`.

Thanks again, Waylan, for suggesting the use of standard link syntax for
video. It's great to be able to keep Markdown documents free of HTML without
introducing new syntax.

David


On 18 September 2010 14:55, David Chambers wrote:

> Hi David,
>
> The URL you received is not (quite) the one I sent. There was (at my end) a
> space between the URL and "(Markdown)". The correct address is
> http://davidchambers.name/blog/soda-pop-stop/m/.
>
> David
>
>
>
> On 19 September 2010 01:22, David Herren  wrote:
>
>> Don't know about anyone else, but these links are failing at present.
>>
>> On Sep 17, 2010, at 10:18 PM, David Chambers wrote:
>>
>> > To see an example visit
>> > http://davidchambers.name/blog/soda-pop-stop/m/(Markdown).
>> >
>> > Then, strip the "m/" from the URL to see the the HTML version.
>>
>>
>> /david
>>
>> --
>> david herren - shoreham, vt, us na terra solsys orionarm
>>
>> Some people have a mental horizon of radius zero, and call it their point
>> of view. -- David Hilbert
>>
>> ___
>> Markdown-Discuss mailing list
>> Markdown-Discuss@six.pairlist.net
>> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>>
>
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Chambers]

Hi David,

The URL you received is not (quite) the one I sent. There was (at my end) a
space between the URL and "(Markdown)". The correct address is
http://davidchambers.name/blog/soda-pop-stop/m/.

David


On 19 September 2010 01:22, David Herren  wrote:

> Don't know about anyone else, but these links are failing at present.
>
> On Sep 17, 2010, at 10:18 PM, David Chambers wrote:
>
> > To see an example visit
> > http://davidchambers.name/blog/soda-pop-stop/m/(Markdown).
> >
> > Then, strip the "m/" from the URL to see the the HTML version.
>
>
> /david
>
> --
> david herren - shoreham, vt, us na terra solsys orionarm
>
> Some people have a mental horizon of radius zero, and call it their point
> of view. -- David Hilbert
>
> ___
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Herren]

Don't know about anyone else, but these links are failing at present.

On Sep 17, 2010, at 10:18 PM, David Chambers wrote:

> To see an example visit
> http://davidchambers.name/blog/soda-pop-stop/m/(Markdown).
> 
> Then, strip the "m/" from the URL to see the the HTML version.


/david

--
david herren - shoreham, vt, us na terra solsys orionarm

Some people have a mental horizon of radius zero, and call it their point of 
view. -- David Hilbert

___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Vinay Augustine]

Maybe this would help: http://www.oembed.com/

oEmbed is a format for allowing an embedded representation of a URL on third
> party sites. The simple API allows a website to display embedded content
> (such as photos or videos) when a user posts a link to that resource,
> without having to parse the resource directly.
>

-- 
-Vinay Augustine, Ph.D.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Chambers]

I've just committed this change (commit
390).
Mango now replaces non-inline YouTube links with embedded video markup.

To see an example visit
http://davidchambers.name/blog/soda-pop-stop/m/(Markdown).

Then, strip the "m/" from the URL to see the the HTML version.

After some deliberation I elected to use YouTube's iframe embedding
methodas
it serves either HTML5 video or Flash as appropriate. Since the markup
is
generated by a Django template, though, it's easily customized.

Although I've gone to quite a bit of trouble to accommodate just a single
service, it's certainly nice to be able to write…

[Soda Pop Stop](http://www.youtube.com/watch?v=gPbh6Ru7VVM)

… and be done!

David


On 16 September 2010 21:56, David Chambers wrote:

> On 16 September 2010 21:10, Allan Odgaard wrote:
>
> There is a difference between a link and an embedded object.
>
>
>> Presently we have `[…](…)` for links and `![…](…)` for embedded objects
>> (limited to images).
>
>
>> I therefor not only think it would be more appropriate to use the
>> `![…](…)` syntax for embedding video/audio, but by using the `[…](…)` syntax
>> with auto-detection, you make it impossible for users to link to the
>> resource (rather than embed it).
>
>
> You make two very good points, Allan. Regarding the first – that it's
> useful to maintain a clear syntactic distinction between links and embedded
> objects – I agree in principle. The drawback of such an approach, however,
> is that it necessitates the use of syntax which will be incorrectly
> interpreted by all existing Markdown implementations. If we were to use the
> image syntax, for example, a standard Markdown processor would produce *
> image* markup. Were we to use a slightly modified version of the image
> syntax to avoid this incorrect interpretation, a standard Markdown processor
> would likely leave the input unchanged.
>
> The nice thing about using standard link syntax is that the fallback is a
> descriptive link – completely acceptable in my opinion. A trade-off exists
> between semantically-correct syntax and interoperability. The side of the
> divide on which one stands depends on how highly one values each of these
> concerns.
>
> I believe that your second point – that it needs to remain possible to *link
> to* a video – is more easily solved. *Links* to videos will almost always
> appear inline within a body of text; embedded videos, on the other hand,
> will not. I'll provide two examples to illustrate my point.
>
>
> *Example 1*
>
> You must check out [Soda Pop Stop][1]. It's a short documentary about a
> store in LA which sells nothing but soda.
>
> [1]: http://www.youtube.com/v/gPbh6Ru7VVM
>
>
> *Example 2*
>
> # Soda Pop Stop
>
> A short documentary about a store in LA which sells nothing but soda.
>
> [Soda Pop Stop][1]
>
> [1]: http://www.youtube.com/v/gPbh6Ru7VVM
>
>
> I would expect the first to be converted to a link and the second to be
> converted to embedding markup (by Mango) or to a link (by standard Markdown
> processors). Distinguishing between the two cases using a regular expression
> is straightforward. If one *wanted* to include a link to a video on its
> own line, one could simply add a full stop (.) at the end of the line.
> Things get a bit murky when one considers the possibility of allowing
> embedded video within other elements (such as lists and blockquotes), so
> initially I plan to insert embedding markup only in the straightforward
> situation demonstrated above.
>
>
> On 16 September 2010 21:10, Allan Odgaard <
> 1edf4d33-d1b1-4c97-a393-3d2b4ee5e095+markd...@uuid-mail.com<1edf4d33-d1b1-4c97-a393-3d2b4ee5e095%2bmarkd...@uuid-mail.com>
> > wrote:
>
>> On 16 Sep 2010, at 03:32, Waylan Limberg wrote:
>>
>>  […] Just parse the urls for "youtube.com" (or "vimeo" etc) and when
>>> found, convert to an appropriate object. It's easy, simple and introduces no
>>> new syntax of any kind.
>>>
>>
>> There is a difference between a link and an embedded object.
>>
>> Presently we have `[…](…)` for links and `![…](…)` for embedded objects
>> (limited to images).
>>
>> I therefor not only think it would be more appropriate to use the
>> `![…](…)` syntax for embedding video/audio, but by using the `[…](…)` syntax
>> with auto-detection, you make it impossible for users to link to the
>> resource (rather than embed it).
>>
>>
>> ___
>> Markdown-Discuss mailing list
>> Markdown-Discuss@six.pairlist.net
>> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>>
>
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Chambers]

On 16 September 2010 21:10, Allan Odgaard wrote:

There is a difference between a link and an embedded object.


> Presently we have `[…](…)` for links and `![…](…)` for embedded objects
> (limited to images).


> I therefor not only think it would be more appropriate to use the `![…](…)`
> syntax for embedding video/audio, but by using the `[…](…)` syntax with
> auto-detection, you make it impossible for users to link to the resource
> (rather than embed it).


You make two very good points, Allan. Regarding the first – that it's useful
to maintain a clear syntactic distinction between links and embedded objects
– I agree in principle. The drawback of such an approach, however, is that
it necessitates the use of syntax which will be incorrectly interpreted by
all existing Markdown implementations. If we were to use the image syntax,
for example, a standard Markdown processor would produce *image* markup.
Were we to use a slightly modified version of the image syntax to avoid this
incorrect interpretation, a standard Markdown processor would likely leave
the input unchanged.

The nice thing about using standard link syntax is that the fallback is a
descriptive link – completely acceptable in my opinion. A trade-off exists
between semantically-correct syntax and interoperability. The side of the
divide on which one stands depends on how highly one values each of these
concerns.

I believe that your second point – that it needs to remain possible to *link
to* a video – is more easily solved. *Links* to videos will almost always
appear inline within a body of text; embedded videos, on the other hand,
will not. I'll provide two examples to illustrate my point.


*Example 1*

You must check out [Soda Pop Stop][1]. It's a short documentary about a
store in LA which sells nothing but soda.

[1]: http://www.youtube.com/v/gPbh6Ru7VVM


*Example 2*

# Soda Pop Stop

A short documentary about a store in LA which sells nothing but soda.

[Soda Pop Stop][1]

[1]: http://www.youtube.com/v/gPbh6Ru7VVM


I would expect the first to be converted to a link and the second to be
converted to embedding markup (by Mango) or to a link (by standard Markdown
processors). Distinguishing between the two cases using a regular expression
is straightforward. If one *wanted* to include a link to a video on its own
line, one could simply add a full stop (.) at the end of the line. Things
get a bit murky when one considers the possibility of allowing embedded
video within other elements (such as lists and blockquotes), so initially I
plan to insert embedding markup only in the straightforward situation
demonstrated above.


On 16 September 2010 21:10, Allan Odgaard <
1edf4d33-d1b1-4c97-a393-3d2b4ee5e095+markd...@uuid-mail.com<1edf4d33-d1b1-4c97-a393-3d2b4ee5e095%2bmarkd...@uuid-mail.com>
> wrote:

> On 16 Sep 2010, at 03:32, Waylan Limberg wrote:
>
>  […] Just parse the urls for "youtube.com" (or "vimeo" etc) and when
>> found, convert to an appropriate object. It's easy, simple and introduces no
>> new syntax of any kind.
>>
>
> There is a difference between a link and an embedded object.
>
> Presently we have `[…](…)` for links and `![…](…)` for embedded objects
> (limited to images).
>
> I therefor not only think it would be more appropriate to use the `![…](…)`
> syntax for embedding video/audio, but by using the `[…](…)` syntax with
> auto-detection, you make it impossible for users to link to the resource
> (rather than embed it).
>
>
> ___
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Allan Odgaard]

On 16 Sep 2010, at 03:32, Waylan Limberg wrote:

[…] Just parse the urls for "youtube.com" (or "vimeo" etc) and when  
found, convert to an appropriate object. It's easy, simple and  
introduces no new syntax of any kind.


There is a difference between a link and an embedded object.

Presently we have `[…](…)` for links and `![…](…)` for embedded  
objects (limited to images).


I therefor not only think it would be more appropriate to use the `![…] 
(…)` syntax for embedding video/audio, but by using the `[…](…)`  
syntax with auto-detection, you make it impossible for users to link  
to the resource (rather than embed it).


___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Chambers]

On 16 September 2010 13:32, Waylan Limberg  wrote:

An interesting thought just occurred to be when re-reading this. Why do you
> need any special syntax at all? Why not just:


>[Soda Pop Stop](http://www.youtube.com/v/gPbh6Ru7VVM )


> Just parse the urls for "youtube.com" (or "vimeo" etc) and when
> found, convert to an appropriate object. It's easy, simple and introduces
> no new syntax of any kind.


Brilliant suggestion, Waylan! I'd been thinking that providing a default
replacement for unrecognized video hosts would be helpful (the `[Vv]ideo:`
syntax would enable this), but you've convinced me otherwise. By using
standard link syntax, the fact that Mango will replace a link to a YouTube
video with the markup necessary to embed that video will be a magical
special case, whereas using `[Vv]ideo:` would set the unreasonable
expectation (as you so rightly point out) that any video should work.

Thanks everyone, for your input. I'll run with the standard link approach,
and add to Mango special rules for handling youtube.com video links.

David


On 16 September 2010 13:32, Waylan Limberg  wrote:

> On Wed, Sep 15, 2010 at 9:24 PM, Waylan Limberg  wrote:
> > While I realize youtube can be extracted from parsing the url, by
>
> An interesting thought just occurred to be when re-reading this. Why
> do you need any special syntax at all? Why not just:
>
>[Soda Pop Stop](http://www.youtube.com/v/gPbh6Ru7VVM )
>
> Just parse the urls for "youtube.com" (or "vimeo" etc) and when found,
> convert to an appropriate object. It's easy, simple and introduces no
> new syntax of any kind.
>
> --
> 
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
> ___
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Waylan Limberg]

On Wed, Sep 15, 2010 at 9:24 PM, Waylan Limberg  wrote:
> While I realize youtube can be extracted from parsing the url, by

An interesting thought just occurred to be when re-reading this. Why
do you need any special syntax at all? Why not just:

[Soda Pop Stop](http://www.youtube.com/v/gPbh6Ru7VVM )

Just parse the urls for "youtube.com" (or "vimeo" etc) and when found,
convert to an appropriate object. It's easy, simple and introduces no
new syntax of any kind.

-- 

\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Waylan Limberg]

On Wed, Sep 15, 2010 at 6:47 PM, David Chambers
 wrote:
> Of course, this markup applies to YouTube but may not apply to other
> services. That being the case, though, I'd still benefit from a `youtube:`
> solution since 80% or more of the videos I embed are YouTube videos. The
> fact that I'd need to include HTML for the other 20% does not deter me.

I suppose personal projects have been implemented for much less
convincing reasons. But if all your implementing is youtude support,
then I'd call it that. `youtude:...` not 'video:...`. Although I
suppose your trying to come up with a syntax for the more general use
case and then move on from there to the more specific. I guess it's
that general use case that I don't see the need for and the reason for
my objection. With a clearer picture of what you actually what to
accomplish, my objections have lessoned.

> One thing that I'd like to make clear, Waylan, is that I'm raising the issue
> on this list because it's a great place for such a discussion, not because
> I'm expecting any of the Markdown implementations to support such syntax.

I guess I understood that.  Sorry if that didn't come through in my
response. I still see developing a syntax for video in general a waste
for the reasons previously stated, so I guess I was trying to
discourage a useless discussion, but if you're really only interested
in a simple syntax to easily embed videos from youtube, vimeo and the
like - and not necessarily expecting it to be an all encompassing
solution for any embedded video, then I can see how that could be
useful as third party add-on to markdown. And this is certainly the
place to get good feedback on a solution.

> Last night another option occurred to me: `[Video: Soda Pop
> Stop](http://www.youtube.com/v/gPbh6Ru7VVM)`.
> The reason that I find this option so appealing is that the above remains
> valid Markdown in non-Mango contexts. Mango will perform preprocessing to
> convert this to the appropriate video markup, but without this preprocessing
> the line would simply be converted to a descriptive link.

I actually like this. It introduces nothing new, will not trip up
unmodified implementations of markdown and still provides enough clues
to embed a video properly (assuming a known source is used).

Despite what I said above, I suppose you would *not* want to do:

[YouTube: Soda Pop Stop](gPbh6Ru7VVM)

While that is more specific and won't create false expectations that
the syntax will work for any type of video, it won't provide a useful
link in an unmodified markdown parser. Perhaps as a safe middleground
I'd suggest:

[YouTube: Soda Pop Stop](http://www.youtube.com/v/gPbh6Ru7VVM)

While I realize youtube can be extracted from parsing the url, by
doing the syntax this way, it is more clear to users that this only
works for supported known (and popular) video hosting sites. No false
expectations about it working for every possible video out there.  And
maybe in the future when all those variables needed to embed html5
video tags are simplified, a more basic [video: ...] syntax could be
adopted as well.

I think that's the root of my concern. If you call it '[video:...]'
you will get complaints insisting that every possible use case for
embedded video be supported - which is just not practical today (as
you acknowledge). But if you call it '[youtube:...]` or `[vimeo:...]`,
etc., then if others want support for a specific as yet unsupported
use-case, they can develop it themselves and maybe even provide their
solution for public consumption. But hey, it's your project that you
will be maintaining. What do I care?
-- 

\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Evan]

 Could either of the following be useful as the markup generated by the 
video tag?


http://camendesign.com/code/video_for_everybody

http://www.mediafront.org/project/osmplayer

E.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[David Chambers]

On 16 September 2010 05:33, Waylan Limberg  wrote:

The fact is, when I go back up and reread this message and get to the source
>  tag, all I see is ` video which gets inserted in the document" and I skip to the next block. It
> doesn't really make reading the document any more painful or difficult.  And
> when writing, well, we need to include all that metadata anyway.


You make two excellent points here, Waylan, and I agree on both counts.

That said, I'm still keen to add some sort of support for shorthand to
Mango, as I personally would find this very helpful. The following, taken
from a post I wrote a year ago on embedding YouTube clips using valid XHTML
markup,
provides useful context:

http://www.youtube.com/v/video_id&hl=en&fs=1&rel=0";>
http://www.youtube.com/v/video_id&hl=en&fs=1&rel=0"; />



While this has not been updated to make use of the `video` element, it
demonstrates that the potential value of some sort of find and replace
mechanism. After all, that's exactly what I've been doing manually for the
last year: to embed a YouTube video I've pasted in the above snippet and
done a find and replace on "video_id". Since I'm styling the `object` via
CSS, I don't even include width and height.

Of course, this markup applies to YouTube but may not apply to other
services. That being the case, though, I'd still benefit from a `youtube:`
solution since 80% or more of the videos I embed are YouTube videos. The
fact that I'd need to include HTML for the other 20% does not deter me.

One thing that I'd like to make clear, Waylan, is that I'm raising the issue
on this list because it's a great place for such a discussion, *not* because
I'm expecting any of the Markdown implementations to support such syntax.

Last night another option occurred to me: `[Video: Soda Pop Stop](
http://www.youtube.com/v/gPbh6Ru7VVM)`.

The reason that I find this option so appealing is that the above remains
valid Markdown in non-Mango contexts. Mango will perform preprocessing to
convert this to the appropriate video markup, but without this preprocessing
the line would simply be converted to a descriptive link.

Sure, you could implement `![alt text](somerandomsite:key)`, but do you
> really want to update your code to support every new video host that comes
> along? Or would you provide some api by which the user could define his own?
> I don't know about you, but every time I link to some new video host from my
> blog, I don't want to have to update my code (even if I wrote it all myself)
> so markdown knows about the new site.


Django (on which Mango is built) offers a simple solution. Mango could, for
example, ship with three templates to handle video: video.html, vimeo.html,
and youtube.html. It could parse the video URLs to determine whether to
apply the YouTube template, the Vimeo template, or the generic (fallback)
template. Users would have the freedom both to add templates for other hosts
and to override the bundled templates.

I agree that updating application code to facilitate the embedding of
possibly just a single video is unreasonable, so I'll stick to pasting in
HTML in these cases.

David


On 16 September 2010 06:05, david parsons  wrote:

> On Thu, Sep 16, 2010 at 01:33:49AM +1200, David Chambers wrote:
> > I'm planning to update Mango  to facilitate adding
> > video to Markdown documents. At the moment, of course, it's possible to
> > include video by including the appropriate HTML. There are three reasons,
> > though, that having syntax (official or unofficial) for video is a good
> > idea:
> >
> >- *Simplicity.* Writing something like [youtube:gPbh6Ru7VVM] is easy.
> >Including half a dozen lines of HTML is much less so.
>
>  I don't know if it's feasable until a standard way of doing video
>  emerges and the video-station websites start following it.  A html5
>   block is lovely, but it's not very useful until the bulk of
>  the web world can deal with it without complaint.
>
> > My question is, *has anyone given thought to an appropriate syntax for
> video
> > in Markdown?*
>
>Sure.   We've got the framework for it:
>
>[text](object:[content-type:]url [=size] ['comment'])
>
>And then you can do something like
>
>[![no support for this content
> here](sorry.gif)](video:x-shockwave-flash:
> http://www.youtube.com/v/oFHSZLIOLZs =425x328 'this may not be terse, but
> at least it's not naked html')
>
>[Honk!](audio:/~orc/klaxon.wav)
>
>
>without introducing (another form of) ascii spaghetti to the language.
>
>
>-david parsons
> ___
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/mar

Re: Video syntax

[david parsons]

On Thu, Sep 16, 2010 at 01:33:49AM +1200, David Chambers wrote:
> I'm planning to update Mango  to facilitate adding
> video to Markdown documents. At the moment, of course, it's possible to
> include video by including the appropriate HTML. There are three reasons,
> though, that having syntax (official or unofficial) for video is a good
> idea:
> 
>- *Simplicity.* Writing something like [youtube:gPbh6Ru7VVM] is easy.
>Including half a dozen lines of HTML is much less so.

 I don't know if it's feasable until a standard way of doing video
 emerges and the video-station websites start following it.  A html5
  block is lovely, but it's not very useful until the bulk of
 the web world can deal with it without complaint.

> My question is, *has anyone given thought to an appropriate syntax for video
> in Markdown?*

Sure.   We've got the framework for it:

[text](object:[content-type:]url [=size] ['comment'])

And then you can do something like

[![no support for this content 
here](sorry.gif)](video:x-shockwave-flash:http://www.youtube.com/v/oFHSZLIOLZs 
=425x328 'this may not be terse, but at least it's not naked html')

[Honk!](audio:/~orc/klaxon.wav)


without introducing (another form of) ascii spaghetti to the language.


-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Albert Skye]

> Clearly one option is to use the same syntax as for images but with 
> an extra `!`, but what would we use for audio in that case? `!!!` 
> would be ridiculous.

No need for more syntax. Overload image syntax instead; i.e., insert resource 
at URL here.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Waylan Limberg]

On Wed, Sep 15, 2010 at 9:33 AM, David Chambers
 wrote:
> My question is, has anyone given thought to an appropriate syntax for video
> in Markdown? We're a long way (five years, at least) from being at the point
> where `` will be sufficient to get the
> job done, so this probably isn't something that Markdown itself will include
> for quite some time. I'm nonetheless interested to hear others' thoughts as
> to what an appropriate syntax might be.

Well until we are at that point, I don't think there is anything we
can practically do.

Consider this html5 markup which you would presumably be generating
(taken from http://diveintohtml5.org/video.html):


  
  
  


Until all those codec issues you mention are resolved, many people may
need to list multiple source paths  (as well as the mime type and
codecs for each) for one video. The width and height should also be
listed, even for a single source. How do you list all that in a simple
markdown syntax. Seems to me html5's syntax does as good a job as any.
True, this doesn't work for flash. That still requires and whole other
 tag as a sibling of the  tags - which is a whole
other mess I'll ignore.

True, flash aside, a certain site may use a specific url scheme, only
offer a certain subset of codeces and offer all videos at a set size;
which could then be passed into your script as user definable options.
But, do you really want to maintain that when new and different
(better?) codeces come along with new requirements? And what about
videos hosted off site that follow different url schemes, offer
different codeces and different sizes?

On Wed, Sep 15, 2010 at 11:34 AM, Vinay Augustine
 wrote:
> What about a URI-like handler?
>
>    ![alt text](video:/path/to/video)

That works if the media is hosted locally (and codeces, size etc has
been resolved in the code), but what about:

![alt text(video:http://somerandomsite.com/path/to/video)

Do we really want people to write (and later read) all those colons
(`video:http:`) in one url? And what about the codec/size/other
meta-data used by that site - which may differ from your own?

Sure, you could implement `![alt text](somerandomsite:key)`, but do
you really want to update your code to support every new video host
that comes along? Or would you provide some api by which the user
could define his own? I don't know about you, but every time I link to
some new video host from my blog, I don't want to have to update my
code (even if I wrote it all myself) so markdown knows about the new
site.

The fact is, when I go back up and reread this message and get to the
source  tag, all I see is `` will be sufficient to get the job done,
I'll probably just use that.  And actually, if you do implement a
post-processor of some kind, why not just make that the syntax?
Markdown should see that as raw html and pass it through unaltered. If
that day ever does come, just remove your post-processor and be done
with it.

My (perhaps more than) $0.02.

-- 

\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Video syntax

[Vinay Augustine]

> Currently, we have:
> [link text](/path/to/link) for links, and
> ![alt text](/path/to/image) for images.

What about a URI-like handler?

![alt text](video:/path/to/video)
![alt text](audio:/path/to/audio)
![alt text](image:/path/to/image)
![alt text](/path/to/image)

The downside is that for audio & video you would need different tags
depending on the site. Maybe site-specific ones would be appropriate:

![alt text](youtube:key)
![alt text](vimeo:key)
![alt text](lastfm:key)
![alt text](flickr:key)

-V
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss

Video syntax

[David Chambers]

I'm planning to update Mango  to facilitate adding
video to Markdown documents. At the moment, of course, it's possible to
include video by including the appropriate HTML. There are three reasons,
though, that having syntax (official or unofficial) for video is a good
idea:

   - *Simplicity.* Writing something like [youtube:gPbh6Ru7VVM] is easy.
   Including half a dozen lines of HTML is much less so.
   - *Readability.* Gruber created Markdown not just because he wanted to
   avoid writing markup – he wanted to avoid *reading* it, too!
   - *Separation of concerns.* Documents should provide for each video just
   a link (and optionally alt text) the way they do for images. This way, the
   application can take on the responsibility of generating the appropriate
   markup. This is tremendously beneficial: HTML5 video is still relatively
   new, sites are being updated to take advantage of native video, and new
   video formats are emerging. Given this moving target it's difficult to be
   sure that hard-coded video markup will remain correct a year from now.
   Handing this responsibility to the application means that all video markup
   on a site can be updated with a single update to the application.

My question is, *has anyone given thought to an appropriate syntax for video
in Markdown?* We're a long way (five years, at least) from being at the
point where `` will be sufficient to get
the job done, so this probably isn't something that Markdown itself will
include for quite some time. I'm nonetheless interested to hear others'
thoughts as to what an appropriate syntax might be.

Currently, we have:

[link text](/path/to/link) for links, and

![alt text](/path/to/image) for images.

Clearly one option is to use the same syntax as for images but with an extra
`!`, but what would we use for audio in that case? `!!!` would be
ridiculous.

David
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss