tantek.com

t

  1. Best social web news today:
    @AppDotNet supports h-entry h-card rel=me #microformats2!
    blog.app.net/2013/08/07/response-to-brennan-novak-part-ii
    #osfw3c

    on
  2. @jasnell Google's market position makes them a bully when they go down their own path instead of working openly. #osfw3c

    on
  3. #osfw3c #Schema-org also sets a bad example in both forking #ActivityStreams and diverging /Person from IETF #vCard4.

    on
  4. #osfw3c Sam Goto asks is #schema good or bad?
    Schema bad for open web, only allows publishing: http://tantek.com/2013/219/t19/osfw3c-contrast-microformats2-cc0-owfa-ogp-schema

    on
  5. #osfw3c contrast:

    Open publish+consume:
    * #microformats2: #CC0+#OWFa
    * #OGP: #OWFa

    Publish only:
    * #Schema: http://schema.org/docs/terms.html
    "they grant an option to receive a license under reasonable and non-discriminatory terms without royalty,
    *solely for the purpose of including markup*
    of structured data in a webpage"
    [*emphasis* mine]

    on
  6. #osfw3c asked Google #Schema-org folks to use #OWFa license at their 2011 workshop. They refused. Schema is not open.

    on
  7. #osfw3c #Schema-org talk: is nonstarter for open web due to no RF patent license for consuming: schema.org/docs/terms.html

    on
  8. @ciberch if your spec is only adopted by intranet, it's intranet-only.
    specs without open web traction fail. #osfw3c

    on
  9. @ciberch intranet-only (or centric) specs fail (WS-*).
    Standards succeed in the open, then enterprise adopts.
    #osfw3c

    on
  10. @ciberch thanks for G+ API link. Looks proprietary, based on but not actually ActivityStreams: http://indiewebcamp.com/Google%2B#Activities

    on
  11. @harryhalpin PuSH yes.
    OGP? Who consumes besides FB (+ some Twitter)?
    Rest are dead or intranet-only (dying).
    #osfw3c

    on
  12. @ciberch which specs in what open web sites? URLs?
    @harryhalpin intranet-only specs are as dead as ActiveX.
    #osfw3c

    on
  13. Learned at #osfw3c:
    @W3C should start a CG that can teach how to put HTML slides on the web instead of Powerpoint/PDF.

    on
  14. @annbass if someone does not know enough HTML to publish specs+slides, they know not enough to innovate on top #osfw3c

    on
  15. really wondering, who at #osfw3c actually ships code/products that create permalinks on the web vs. behind a firewall?

    on
  16. @annbass here's a good start:
    indiewebcamp.com/social-standards
    #microformats #hcard #hentry #webmention #xfn
    #osfw3c

    on
  17. new rule: if you can't publish your *web* "standard" doc/spec in *HTML*, go learn HTML before trying to innovate. #osfw3c

    on
  18. @manusporny - am not going to link to a *PDF* about proposed *web* technologies (however bloated). #osfw3c

    on
  19. if you're publishing your *web* "standard" docs/specs in PDF not HTML, you're doing it wrong. #osfw3c

    on
  20. just learned about a #fatberg equivalent of web tech: Open Social + LinkedData/JSONLD + RDF. docs are in PDF. #osfw3c

    on
  21. made it to #osfw3c workshop. Those of us with our own #indieweb domains are writing them on our badges in red Sharpie.

    on
  22. day 1 of @W3C Social Standards Workshop. Disappointed that  http://www.w3.org/2013/socialweb/ mentions mostly dead specs. #osfw3c

    on
  23. “it was a case of the past and the future mutually coexisting. And then the past just goes away” — @GreatDismal
    http://www.theparisreview.org/interviews/6089/the-art-of-fiction-no-211-william-gibson
    Brilliant summary of what we see so often in technology, standards, culture.

    on