I'd definitely like to keep the implementation of whatever formats we
use in Gaia given that this is still an experimental feature and the
use cases are likely to evolve as we get user feedback.
It seems to me that given that our use case here, beyond OG, is only
our internal content, I.e. Gaia.
On Thu, Jul 2, 2015 at 4:37 AM, Tantek Çelik tan...@cs.stanford.edu wrote:
Schema.org also provides existing schemas for actions associated with
items
(https://schema.org/docs/actions.html),
...
Currently the IndieWeb community is pursuing Web Actions (and has them
working across
On 2 July 2015 at 03:37, Tantek Çelik tan...@cs.stanford.edu wrote:
tl;dr: It's time. Let's land microformats parsing support in Gecko as
a Q3 Platform deliverable that Gaia can use.
Happy to hear this!
I think there's rough consensus that a subset of OG, as described by
Ted, satisfies
This thread has been fun to follow. There are only 2 hard problems in Comp Sci
and naming things is one of them ;).
Just wanted to quickly chip in: during our lively discussion about naming,
let’s not forget Postel’s Law.
It’s smart to debate which format we should encourage for _publishing_.
On Thu, Jul 2, 2015 at 11:47 AM, Gordon Brander gbran...@mozilla.com
wrote:
This thread has been fun to follow. There are only 2 hard problems in Comp
Sci and naming things is one of them ;).
Just wanted to quickly chip in: during our lively discussion about naming,
let’s not forget Postel’s
This. I don't want to lose Jonas' point in this long thread, but I also
haven't read anything here that warrants new native parser(s) yet. Let's
iterate in Gaia for now. I don't see how a C++ metadata parser is
advantageous at this point, and the RDF history lessons certainly don't
encourage that
On Wed, Jul 1, 2015 at 7:37 PM, Tantek Çelik tan...@cs.stanford.edu wrote:
There *is* a pretty strong engineering consensus, in both this thread,
and other threads *against* any use of JSON-LD, or anything Linked
Data or otherwise rebranded RDF / Semantic Web, and for good reason.
Indeed,
Great discussion and feedback in this thread - plenty to act on.
Thanks Ted Clancy for kicking this off with an impassioned reality
check. And Thanks in particular to Benjamin Francis for summarizing
product requirements and use-cases, and especially to both Ted and Ben
taking the time last week
Let me start by saying I don't care which format we use. (Formats come, and
formats go.) I do care, however, that my use case is supported.
My use case, speech enabling web apps and web pages for Firefox OS's voice
assistant Vaani, requires that the chosen format support something akin to
On June 27, 2015 at 10:02:47 AM, Anne van Kesteren (ann...@annevk.nl) wrote:
The data I have does not back this up, Microdata is shown to be growing
fast whereas Microformats usage has remained relatively stable.
Also, we didn't find Microformats usage on any of the example
high
On June 29, 2015 at 7:07:33 AM, Michael Henretty (mhenre...@mozilla.com) wrote:
We will definitely start with the simple open graph stuff that Ted
mentioned (og:title, og:type, og:url, og:image, og:description)
since they are so widely used. And yes, even these simple ones are
problematic.
On Saturday, June 27, 2015, Benjamin Francis bfran...@mozilla.com wrote:
On 26 June 2015 at 19:25, Marcos Caceres mar...@marcosc.com
javascript:_e(%7B%7D,'cvml','mar...@marcosc.com'); wrote:
Could we see some examples of the cards you are generating already with
existing data from the Web
Thanks for the responses,
Let me reiterate the Product requirements:
1. Support for a syntax and vocabulary already in wide use on the web to
allow the creation of cards for the largest possible volume of existing
pinnable content
2. Support for a syntax with a large enough and/or
On Sat, Jun 27, 2015 at 5:51 AM, Marcos Caceres mar...@marcosc.com wrote:
These look fantastic! so why not start with just those? Or are all those
card types done and thoroughly tested on a good chunk of Web content? As I
mentioned before, I'd be worried about the amount of error recovery
On 26 June 2015 at 19:25, Marcos Caceres mar...@marcosc.com wrote:
Could we see some examples of the cards you are generating already with
existing data from the Web (from your prototype)? The value is really in
seeing that users will get some real benefit, without expecting developers
to add
Removing dev-webapi since it's (near) dead.
On Thu, Jun 25, 2015 at 7:19 PM, Benjamin Francis bfran...@mozilla.com wrote:
Unless there's a really good reason not to do so, I'm going to file the bugs
and look towards getting this implemented on the Browser API as soon as
possible.
What you
Le 26 juin 2015 à 08:00, Anne van Kesteren ann...@annevk.nl a écrit :
What you outlined still seems like a rather giant hack to get this one
thing working. Is the idea to just keep adding events for each bit of
information we might need from a document?
Maybe there is a way to start small.
On 26 June 2015 at 12:58, Ted Clancy tcla...@mozilla.com wrote:
My apologies for the fact that this is such an essay, but I think this has
become necessary.
Firefox OS 2.5 will be unveiling a new feature called Pinning The Web, and
there's been some discussion about whether we should
My apologies for the fact that this is such an essay, but I think this has
become necessary.
Firefox OS 2.5 will be unveiling a new feature called Pinning The Web, and
there's been some discussion about whether we should leverage technologies
like RDFa, Microdata, JSON-LD, Open Graph, and
On 26 June 2015 at 08:29, Karl Dubost kdub...@mozilla.com wrote:
Maybe there is a way to start small. Iterate. Look at the results. And
push further in the direction which appears to be meaningful.
Exactly, I'm looking for a solid MVP that we can iterate on. More detailed
response to Ted's
On Fri, Jun 26, 2015 at 2:18 PM, Benjamin Francis bfran...@mozilla.com wrote:
When I look at RDFa, Microdata and JSON-LD I see formal W3C
recommendations, extensive vocabularies which (at least on the surface) are
agreed on by all the big search engines, and I see a clean engineering
solution
On 26 June 2015 at 17:02, Anne van Kesteren ann...@annevk.nl wrote:
I would encourage you to go a little deeper...
We need to judge standards on their merits
I did look deeper. I read most of all the specifications and several papers
on their adoption. My personal conclusion was that not only
On 26 June 2015 at 08:00, Anne van Kesteren ann...@annevk.nl wrote:
Is the idea to just keep adding events for each bit of
information we might need from a document?
That is how the Browser API works.
Ben
___
dev-platform mailing list
On Thu, Jun 25, 2015 at 7:19 PM, Benjamin Francis bfran...@mozilla.com wrote:
and JSON-LD (because it supports Gaia's more complex use cases).
Hi Ben,
My only concern here is that if you pin a contact, it seems to me that
it would be good if the name and picture of that homescreen UI should
be
On Fri, Jun 26, 2015 at 5:37 PM, Benjamin Francis bfran...@mozilla.com wrote:
On 26 June 2015 at 08:00, Anne van Kesteren ann...@annevk.nl wrote:
Is the idea to just keep adding events for each bit of
information we might need from a document?
That is how the Browser API works.
I don't
To follow up on this, there is resistance against implementing the more
complex Microdata or RDFa specifications in Gecko.
We definitely now need some form of Linked Data support for Firefox OS 2.5
so I'm suggesting the following: We should support Open Graph (because of
its wide usage by
On 3 June 2015 at 19:42, Benjamin Francis bfran...@mozilla.com wrote:
This is what I'd really like to get more of, particularly usage data.
I've reached out to a few people at Yahoo, Google and a couple of
universities and have managed to turn up a few studies with useful data
[1][2][3][4].
On 04/06/2015 12:34 , Benjamin Francis wrote:
On 4 June 2015 at 03:27, Michael[tm] Smith m...@w3.org wrote
As came up in some off-list discussion with Anne, is the “Manifest for a
web application” spec at https://w3c.github.io/manifest/ not relevant
here?
(Nothing to reverse engineer, since it
On 4 June 2015 at 03:27, Michael[tm] Smith m...@w3.org wrote
As came up in some off-list discussion with Anne, is the “Manifest for a
web application” spec at https://w3c.github.io/manifest/ not relevant
here?
(Nothing to reverse engineer, since it has an actual spec—with defined
processing
[re-sending with Marcos actually Cc’ed this time]
Marcos, if you’ve not been following along already, full context starts at
https://lists.mozilla.org/pipermail/dev-platform/2015-May/010149.html
Anne van Kesteren ann...@annevk.nl, 2015-06-02 08:31 +0900:
On Sun, May 31, 2015 at 5:09 AM, Jonas
Thanks for all the responses so far! Comments inline...
On 30 May 2015 at 21:09, Jonas Sicking jo...@sicking.cc wrote:
We should use whatever formats people are using to mark up pages. If that
is microdata we should use that. If it's RDF we should use that. If its
JSONLD we should use that.
[cc’ing Marcos] Marcos, if you’ve not been following along already, full context
starts at https://lists.mozilla.org/pipermail/dev-platform/2015-May/010149.html
Anne van Kesteren ann...@annevk.nl, 2015-06-02 08:31 +0900:
On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking jo...@sicking.cc wrote:
We
Gordan has the right general idea to approaching this problem space.
On Mon, Jun 1, 2015 at 5:42 PM, Gordon Brander gbran...@mozilla.com wrote:
On June 1, 2015 at 17:34:48 , Jonas Sicking (jo...@sicking.cc) wrote:
I think we're already talking about reverse-engineering what search
engines and
On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking jo...@sicking.cc wrote:
We should use whatever formats people are using to mark up pages. If that is
microdata we should use that. If it's RDF we should use that. If its JSONLD
we should use that.
The API that is used to extract the data is
Benjamin,
Le 30 mai 2015 à 21:35, Benjamin Francis bfran...@mozilla.com a écrit :
But Microdata is only one of the formats widely used on the web today. I'd
like to see some evidence-based discussion on which format(s) we should
support to get the most possible value out of what already exists
On Mon, Jun 1, 2015 at 4:31 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking jo...@sicking.cc wrote:
We should use whatever formats people are using to mark up pages. If that is
microdata we should use that. If it's RDF we should use that. If its
We should use whatever formats people are using to mark up pages. If that
is microdata we should use that. If it's RDF we should use that. If its
JSONLD we should use that.
The API that is used to extract the data is irrelevant. That will be an
internal API anyway. Effectively we should think of
We should consider a series of fallbacks for this internal API.
The metadata story for things like icon, title, description, hero images, is
complicated. Implementation in the follows real-world use cases like posting
rich snippets to Facebook or getting an image to show up on Twitter, rather
On 30 May 2015 at 00:56, Anne van Kesteren ann...@annevk.nl wrote:
We've bitten ourselves before going down the RDF rathole (see
extensions et al). Not sure we should so rapidly start again. Why
can't you use the Microdata API?
Is this already supported in Gecko? I can't find it documented
On Fri, May 29, 2015 at 2:55 AM, Benjamin Francis bfran...@mozilla.com wrote:
Actually what might make more sense is a getLinkedData() method on the API
which returns a Promise that resolves with the JSON data, as I think we're
also going to need a getManifest() method which could work in a
Hi,
In Gaia the Systems Front End team is implementing the Pinning the Web
design concept [1] which amongst other things represents pinned web pages
as cards on the homescreen. The goal is that where possible these cards
should not just be a thumbnail screenshot of the page, but should be a
On 28 May 2015 at 18:13, Benjamin Francis bfran...@mozilla.com wrote:
For the real implementation I suggest we investigate supporting one or
more formats for Linked Data in web pages (based on level of adoption) and
surface them to Gaia through a linkeddatachange event on the Browser API. I
42 matches
Mail list logo
