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 p
On Thu, Jul 2, 2015 at 11:47 AM, Gordon Brander
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 Law.
>
> It’s s
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_.
I
On 2 July 2015 at 03:37, Tantek Çelik 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. Minimizing our
On Thu, Jul 2, 2015 at 4:37 AM, Tantek Çelik 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 sites)
>
> http:/
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 Wed, Jul 1, 2015 at 7:37 PM, Tantek Çelik 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, just a few days ago bs
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 i
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 ext
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
>
On Saturday, June 27, 2015, Benjamin Francis wrote:
> On 26 June 2015 at 19:25, Marcos Caceres > 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
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 p
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
schem
On Sat, Jun 27, 2015 at 5:51 AM, Marcos Caceres 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
> code that will b
On 26 June 2015 at 19:25, Marcos Caceres 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 additional met
On Fri, Jun 26, 2015 at 5:37 PM, Benjamin Francis wrote:
> On 26 June 2015 at 08:00, Anne van Kesteren 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 think that we should be terribly
On 26 June 2015 at 08:00, Anne van Kesteren 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
dev-platform@lists.mozilla.
On 26 June 2015 at 17:02, Anne van Kesteren 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 does
Microform
On Fri, Jun 26, 2015 at 2:18 PM, Benjamin Francis 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 (albeit fairly co
On Thu, Jun 25, 2015 at 7:19 PM, Benjamin Francis 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 quickly updated if t
On 26 June 2015 at 12:58, Ted Clancy 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 leverage technologies
On 26 June 2015 at 08:29, Karl Dubost 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 post coming...
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 Microfor
Le 26 juin 2015 à 08:00, Anne van Kesteren 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. Iterate. Look at
Removing dev-webapi since it's (near) dead.
On Thu, Jun 25, 2015 at 7:19 PM, Benjamin Francis 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 outlined still seems
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 existing
On 3 June 2015 at 19:42, Benjamin Francis 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].
My conclusions so fa
On 04/06/2015 12:34 , Benjamin Francis wrote:
On 4 June 2015 at 03:27, Michael[tm] Smith 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 actua
On 4 June 2015 at 03:27, Michael[tm] Smith 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 require
[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 , 2015-06-02 08:31 +0900:
> On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking wrote:
>
[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 , 2015-06-02 08:31 +0900:
> On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking wrote:
> > We should use whatever formats p
Benjamin Francis , 2015-06-03 19:42 +0100:
...
> Open Graph is quite primitive in comparison to other formats in terms of
> what can be expressed (and it's not clear to me whether it validates as
> either valid HTML5 or valid RDFa)
It’s not valid HTML(5), because the HTML spec doesn’t allow the me
Thanks for all the responses so far! Comments inline...
On 30 May 2015 at 21:09, Jonas Sicking 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.
>
Agree, that's
Gordan has the right general idea to approaching this problem space.
On Mon, Jun 1, 2015 at 5:42 PM, Gordon Brander 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 twitter/facebook
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 twitter/facebook/etc do.
>
> But I'm still all for proper standardization. Including driving
> towards good technical solutions.
Yup. We’re rea
On Mon, Jun 1, 2015 at 4:31 PM, Anne van Kesteren wrote:
> On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking 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.
>>
Benjamin,
Le 30 mai 2015 à 21:35, Benjamin Francis 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 the
> web. The
On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking 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 irrelevant. That
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
t
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 t
On 30 May 2015 at 00:56, Anne van Kesteren 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 anywhere,
exce
On Fri, May 29, 2015 at 2:55 AM, Benjamin Francis 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 similar way.
We've b
On 28 May 2015 at 18:13, Benjamin Francis 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
> propose that the p
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
mean
44 matches
Mail list logo
