Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity

December 1, 2015

Ding-Dong! Flash Is Dying!

Filed under: Cybersecurity,HTML5,Security — Patrick Durusau @ 6:47 pm

Flash, HTML5 and Open Web Standards

From the post:

Adobe has a history of pioneering and advancing industry standards. We embrace standards and, where none exist, we create them.

Flash has played a leading role in bringing new capabilities to the web. From audio and animation, to interactivity and video, Flash has helped push the web forward.

Today, open standards like HTML5 have matured and provide many of the capabilities that Flash ushered in. Our customers have clearly communicated that they would like our creative applications to evolve to support multiple standards and we are committed to doing that. So today we are announcing Animate CC, previously Flash Professional CC, which will be Adobe’s premier web animation tool for developing HTML5 content while continuing to support the creation of Flash content. Adobe Animate CC will be available in early 2016. In addition, Adobe will release an HTML5 video player for desktop browsers, which will complement Adobe’s support for HTML5 on mobile. [Visit the Primetime blog for more information].

I didn’t realize we lacked a standard for web insecurity. Certainly Adobe Flash set the standard for maximum cyberinsecurity. I don’t know that I would brag about it.

Adobe says that new standards aren’t mature in “web gaming and premium video” and so will keep promoting Flash for those use cases. I take that to mean standards geeks and implementation experts need to double down in both of those areas.

The sooner Flash is just an unpleasant memory the more secure we will all be in the present.

I first saw this in a Facebook post by Alex Brown.

June 3, 2015

W3C Validation Tools – New Location

Filed under: CSS3,HTML,HTML5,W3C,WWW — Patrick Durusau @ 10:52 am

W3C Validation Tools

The W3C graciously hosts the following free validation tools:

CSS Validator – Checks your Cascading Style Sheets (CSS)

Internationalization Checker – Checks level of internationalization-friendliness.

Link Checker – Checks your web pages for broken links.

Markup Validator – Checks the markup of your Web documents (HTML or XHTML).

RSS Feed Validator – Validator for syndicated feeds. (RSS and Atom feeds)

RDF Validator – Checks and visualizes RDF documents.

Unicorn – Unified validator. HTML, CSS, Links & Mobile.

Validator.nu Checks HTML5.

I mention that these tools are free to emphasize there is no barrier to their use.

Just as you wouldn’t submit a research paper with pizza grease stains on it, use these tools to proof draft standards before you submit them for review.

February 21, 2015

Redefining “URL” to Invalidate Twenty-One (21) Years of Usage

Filed under: HTML5,WWW — Patrick Durusau @ 3:11 pm

You may be interested to know that efforts are underway to bury the original meaning of URL and to replace it with another meaning.

Our trail starts with the HTML 5 draft of 17 December 2012, which reads in part:

2.6 URLs

This specification defines the term URL, and defines various algorithms for dealing with URLs, because for historical reasons the rules defined by the URI and IRI specifications are not a complete description of what HTML user agents need to implement to be compatible with Web content.

The term “URL” in this specification is used in a manner distinct from the precise technical meaning it is given in RFC 3986. Readers familiar with that RFC will find it easier to read this specification if they pretend the term “URL” as used herein is really called something else altogether. This is a willful violation of RFC 3986. [RFC3986]

2.6.1 Terminology

A URL is a string used to identify a resource.

A URL is a valid URL if at least one of the following conditions holds:

  • The URL is a valid URI reference [RFC3986].
  • The URL is a valid IRI reference and it has no query component. [RFC3987]
  • The URL is a valid IRI reference and its query component contains no unescaped non-ASCII characters. [RFC3987]
  • The URL is a valid IRI reference and the character encoding of the URL’s Document is UTF-8 or a UTF-16 encoding. [RFC3987]

You may not like the usurpation of URL and its meaning but at least it is honestly reported.

Compare Editor’s Draft 13 November 2014, which reads in part:

2.5 URLs

2.5.1 Terminology

A URL is a valid URL if it conforms to the authoring conformance requirements in the WHATWG URL standard. [URL]

A string is a valid non-empty URL if it is a valid URL but it is not the empty string.

Hmmm, all the references to IRIs and violating RFC3986 has disappeared.

But there is a reference to the WHATWG URL standard.

If you follow that internal link to the bibliography you will find:

[URL]
URL (URL: http://url.spec.whatwg.org/), A. van Kesteren. WHATWG.

Next stop: URL Living Standard — Last Updated 6 February 2015, which reads in part:

The URL standard takes the following approach towards making URLs fully interoperable:

  • Align RFC 3986 and RFC 3987 with contemporary implementations and obsolete them in the process. (E.g. spaces, other “illegal” code points, query encoding, equality, canonicalization, are all concepts not entirely shared, or defined.) URL parsing needs to become as solid as HTML parsing. [RFC3986] [RFC3987]
  • Standardize on the term URL. URI and IRI are just confusing. In practice a single algorithm is used for both so keeping them distinct is not helping anyone. URL also easily wins the search result popularity contest.

A specification being developed by WHATWG.org.

Not nearly as clear and forthcoming as the HTML5 draft as of 17 December 2012. Yes?

RFC3986 and RFC3987 are products of the IETF. If revisions of those RFCs are required, shouldn’t that work be at IETF?

Or at a minimum, why is a foundation for HTML5 not at the W3C, if not at IETF?

The conflating URLs (RFC3986) and IRIs (RFC3987) is taking place well away from the IETF and W3C processes.

A conflation that invalidates twenty-one (21) years of use of URL in books, papers, presentations, documentation, etc.

BTW, URL was originally defined in 1994 in RFC1738.

Is popularity of an acronym worth that cost?

December 19, 2014

Terms Defined in the W3C HTML5 Recommendation

Filed under: HTML5,W3C — Patrick Durusau @ 6:27 pm

Terms Defined in the W3C HTML5 RecommendationHTML5 Recommendation.

I won’t say this document has much of a plot or that it is an easy read. 😉

If you are using HTML5, however, this should either be a bookmark or open in your browser.

Enjoy!

I first saw this in a tweet by AdobeWebCC.

September 17, 2014

Call for Review: HTML5 Proposed Recommendation Published

Filed under: HTML5,W3C — Patrick Durusau @ 10:13 am

Call for Review: HTML5 Proposed Recommendation Published

From the post:

The HTML Working Group has published a Proposed Recommendation of HTML5. This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. Comments are welcome through 14 October. Learn more about the HTML Activity.

Now would be the time to submit comments, corrections, etc.

Deadline: 14 October 2014.

June 2, 2014

HTML5 vs. XML: War?

Filed under: HTML5,XML — Patrick Durusau @ 3:11 pm

I stole part of the title from a tweet by Deborah A. Lapeyre that reads:

HTML5 and XML: War? Snub fest? Harmony? How should they interact? pre-Balisage 1-day Symposium. Come be heard! https://www.balisage.net/HTML5-XML/index.html

As you will gather from the tweet, Balisage is having a one day pre-conference meeting on HTML5 and XML. From the Symposium page:

Despite a decade of efforts dedicated to making XML the markup language of the Web, today it is HTML5 that has taken on that role. While HTML5 can in part be made to work with an XML syntax, reliance on that feature is rare compared to use of HTML5’s own syntax.

Over the years, the competition between these two approaches has led to animosity and frustration. But both XML and HTML5 are now clearly here to stay, and with the upcoming standardisation of HTML5 in 2014 it is now time to take stock and see how both technologies — and both communities — can coöperate constructively.

There are many environments in which these two markup languages are brought to interact. Additionally, there is much that they can learn from one another. We are looking forward to sharing experiences and ideas that bring the two together.

Does HTML 5 have the role of markup language of the Web?

As far as layout engines, you would have to say “partial support” for HTML5 at best.

And the number I was hearing last year was 10% of the Web using HTML5. Have you heard differently?

I’m sure the W3C is absolutely certain that HTML5 is the very thing for the Web but remember it wasn’t all that long ago that they abandoned their little red RDF wagon to its own fate. With enough money you can promote anything for more than a decade. Adoption, well, that’s something else entirely.

For me the obvious tip-off about HTML5 came from its description at Wikipedia HTML5:

It includes detailed processing models to encourage more interoperable implementations;

Anyone who needs a “detailed processing models” for “interoperability” doesn’t understand the nature of markup languages.

Markup languages capture the structure of documents in order for documents to be interchanged between applications. So long as an application can parse the document into its internal model and deliver the expected result to its user, then the document is “interoperable” between the applications.

What the W3C is attempting to hide behind its processing models is forcing users to view materials as defined by others. That is they want to take away your right to view and/or process a document as you want. Such as avoiding advertising or reformatting a document after removal of advertising.

Do you remember Rocky Horror Picture Show? And Janet’s comment about Rocky was “Well, I don’t like men with too many muscles.”

And Dr. Frank N. Furter’s response?

I didn’t make him for you!

Same can be said for HTML5. They didn’t make it for you.

If you think differently, bring your false gods to the HTML5 and XML: Mending Fences: A Balisage pre-conference symposium. Stay for the conference. It will give you time to find a new set of false gods.

March 19, 2014

The Seven Parts of “HTML 5 Fundamentals”

Filed under: CSS3,HTML5,WWW — Patrick Durusau @ 2:08 pm

The Seven Parts of “HTML 5 Fundamentals” by Greg Duncan.

From the post:

It’s Web Wednesday and today we’re going to take a step back and share a series by David Giard, who’s going to give us a fundamental look at HTML5. Oh, I know YOU don’t need this, but you might have a "friend" who does (cough… like me… cough…).

HTML 5 Fundamentals

Read this series of articles to learn more about HTML5 and CSS3

Part 1- An Introduction to HTML5

Part 2 – New Tags

Part 3 – New Attributes

Part 4 – New Input Types

Part 5 – CSS3

Part 6 – More CSS3

Part 7 – HTML5 JavaScript APIs

Part 1 has this jewel:

Due to the enormous scope of HTML5 and the rate at which users tend to upgrade to new browsers, it is unlikely that HTML5 will be on all computers for another decade.

Let’s see, a web “year” is approximately 3 months according to Tim Berners-Lee, so in forty (40) web years, HTML5 will be on all computers.

That’s a long time to wait so I would suggest learning features as they are supported by the top three browsers. You won’t ever be terribly behind and at the same time, your webpages wit

That would make an interesting listing if it doesn’t exist already. The features of HTML5 as a matrix against the top three browsers.

Legend for the matrix: One browser – start learning, Two browsers – start writing, Three browsers – deploy.

Yes?

I first saw this in a tweet by Microsoft Channel 9.

August 22, 2013

Three RDFa Recommendations Published

Filed under: HTML5,RDF,RDFa,WWW — Patrick Durusau @ 2:52 pm

Three RDFa Recommendations Published

From the announcement:

  • HTML+RDFa 1.1, which defines rules and guidelines for adapting the RDFa Core 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.
  • The group also published two Second Editions for RDFa Core 1.1 and XHTML+RDFa 1.1, folding in the errata reported by the community since their publication as Recommendations in June 2012; all changes were editorial.
  • The group also updated the a RDFa 1.1 Primer.

The deeper I get into HTML+RDFa 1.1, the more I think a random RDFa generator would be an effective weapon against government snooping.

Something copies some percentage of your text and places it in a comment and generates random RDFa 1.1 markup for it, thus: <!– – your content + RDFa – –>.

Improves the stats for the usage of RDFa 1.1 and if the government tries to follow all the RDFa 1.1 rules, well, let’s just say they will have less time for other mischief. 😉

June 6, 2013

HTML 5.1 (new draft)

Filed under: HTML5,W3C — Patrick Durusau @ 2:18 pm

HTML 5.1 (new draft)

Abstract:

This specification defines the 5th major version, first minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability.

Important to watch as browsers become the dominant means of content delivery.

I first saw this at: New HTML 5.1 working draft released.

May 11, 2013

Defeating DRM in HTML5

Filed under: Cybersecurity,DRM,HTML5 — Patrick Durusau @ 4:59 pm

You may heard that the W3C is giving the WWW label to DRM-based content vendors in HTML5: W3C presses ahead with DRM interface in HTML5

From the post:

On Friday, the World Wide Web Consortium (W3C) published the first public draft of Encrypted Media Extensions (EME). EME enables content providers to integrate digital rights management (DRM) interfaces into HTML5-based media players. Encrypted Media Extensions is being developed jointly by Google, Microsoft and online streaming-service Netflix. No actual encryption algorithm is part of the draft; that element is designed to be contained in a CDM (Content Decryption Module) that works with EME to decode the content. CDMs may be plugins or built into browsers.

The publication of the new draft is a blow for critics of the extensions, led by the Free Software Foundation (FSF). Under the slogan, “We don’t want the Hollyweb”, FSF’s anti-DRM campaign Defective by Design has started a petition against the “disastrous proposal”, though FSF and allied organisations have so far only succeeded in mobilising half of their target of 50,000 supporters.

I could understand this better if the W3C was getting paid by the DRM-based content vendors for the WWW label. Giving it away to commercial profiteers seems like poor business judgement.

On the order of the U.S. government developing the public internet and then giving it away as it became commercially viable. As one of the involuntary investors in the U.S. government, I would have liked a better return on that investment.

There is one fairly easy way to defeat DRM in HTML5.

Don’t use it. Don’t view/purchase products that use it, don’t produce products or services that use it.

The people who produce and sell DRM-based products will find other ways to occupy themselves should DRM-based products fail.

Unlike the FSF, they are not producing products for obscure motives. They are looking to make a profit. No profit, no DRM-vendors.

You may say that “other people” will purchase those products and services, encouraging DRM vendors. They very well may but that’s their choice.

It is unconvincing to argue for a universe of free choice when some people get to choose on behalf of others, like the public.

May 10, 2013

Cool Tools: pdf2html

Filed under: HTML5,PDF — Patrick Durusau @ 5:37 pm

Cool Tools: pdf2html by Derek Willis.

From the post:

A PDF does one thing very well: it presents an accurate image that can be viewed on just about any device. Unfortunately, PDFs also cause grief for anyone who wants to use the data they contain. Governments, in particular, have a habit of releasing PDFs when the information would be more useful and accessible as a spreadsheet. The tools for extracting text from PDFs can be flaky, but Lu Wang’s pdf2htmlEX project solves this problem. Pdf2htmlEX takes PDFs and converts them into HTML5 documents while preserving the layout and appearance of the original.

This looks very cool!

Of course, moving from HTML5 is left as an exercise for the reader. 😉

March 17, 2013

XMLQuire Web Edition

Filed under: HTML5,Saxon,XML,XSLT — Patrick Durusau @ 5:50 am

XMLQuire Web Edition: A Free XSLT 2.0 Editor for the Web

From the webpage:

XSLT 2.0 processing within the browser is now a reality with the introduction of the open source Saxon-CE from Saxonica. This processor runs as a JavaScript app and supports JavaScript interoperability and user-event handling for the era of HTML5 and the dynamic web.

This Windows product, XMLQuire, is an XSLT edtior specially extended to integrate with Saxon-CE and support the Saxon-CE language extensions that make interactive XSLT possible. Saxon-CE is not included with this product, but is available from Saxonica here.

*nix folks will have to install Windows 7 or 8 on a VM to take advantage of this software.

Worth the effort if for no other reason than to see how the market majority lives. 😉

I first saw this in a tweet by Michael Kay.

February 27, 2013

URL Homonym Problem: A Topic Map Solution

Filed under: Homonymous,HTML5,W3C — Patrick Durusau @ 5:34 pm

You may have heard about the URL homonym problem.

The term “URL” is spelled and pronounced the same way but can mean:

URL as defined by Uniform Resource Identifier (URI): Generic Syntax, RFC 3986, or

URL as defined by HTML5 (Draft, December 17, 2012)

To refresh your memory:

URL in RFC 3986 is defined as:

The term “Uniform Resource Locator” (URL) refers to the subset of URIs that, in addition to identifying a resource, provide a means of locating the resource by describing its primary access mechanism (e.g., its network “location”).

A URL in RFC 3986 is a subtype of URI.

URL in HTML5 is defined as:

A URL is a string used to identify a resource.

A URL in HTML5 is a supertype of URI and IRI.

I would say that going from being a subtype of URI to being a supertype of URI + IRI is a “…willful violation of RFC 3986….”

In LTM syntax, I would solve the URL homonym problem as follows:

#VERSION "1.3"

/* association types */

[supertype-subtype = "Supertype-subtype";
@"http://psi.topicmaps.org/iso13250/model/supertype-subtype"]

[supertype = "Supertype";
@"http://psi.topicmaps.org/iso13250/model/supertype"]

[subtype = "Subtype";
@"http://psi.topicmaps.org/iso13250/model/subtype"]

/* topics */

[uri = "URI";
@"http://tools.ietf.org/html/rfc3986#1.1"]

[url-rfc3986 = "URL";;"URL-RFC 3986"
@"http://tools.ietf.org/html/rfc3986#1.1.3"]

supertype-subtype(uri : supertype,url-rfc3986 : subtype)

[url-html5 = "URL";;"URL-HTML5"
@"http://www.w3.org/TR/2012/CR-html5-20121217/infrastructure.html#urls"]

supertype-subtype(url-html5 : supertype,uri : subtype)

A solution to the URL homonym problem only in the sense of distinguishing which definition is in use.

February 3, 2013

Scribl: an HTML5 Canvas-based graphics library…

Filed under: Genomics,Graphics,HTML5,Javascript,Visualization — Patrick Durusau @ 6:57 pm

Scribl: an HTML5 Canvas-based graphics library for visualizing genomic data over the web by Chase A. Miller, Jon Anthony, Michelle M. Meyer and Gabor Marth. (Bioinformatics (2013) 29 (3): 381-383. doi: 10.1093/bioinformatics/bts677)

Abstract:

Motivation: High-throughput biological research requires simultaneous visualization as well as analysis of genomic data, e.g. read alignments, variant calls and genomic annotations. Traditionally, such integrative analysis required desktop applications operating on locally stored data. Many current terabyte-size datasets generated by large public consortia projects, however, are already only feasibly stored at specialist genome analysis centers. As even small laboratories can afford very large datasets, local storage and analysis are becoming increasingly limiting, and it is likely that most such datasets will soon be stored remotely, e.g. in the cloud. These developments will require web-based tools that enable users to access, analyze and view vast remotely stored data with a level of sophistication and interactivity that approximates desktop applications. As rapidly dropping cost enables researchers to collect data intended to answer questions in very specialized contexts, developers must also provide software libraries that empower users to implement customized data analyses and data views for their particular application. Such specialized, yet lightweight, applications would empower scientists to better answer specific biological questions than possible with general-purpose genome browsers currently available.

Results: Using recent advances in core web technologies (HTML5), we developed Scribl, a flexible genomic visualization library specifically targeting coordinate-based data such as genomic features, DNA sequence and genetic variants. Scribl simplifies the development of sophisticated web-based graphical tools that approach the dynamism and interactivity of desktop applications.

Availability and implementation: Software is freely available online at http://chmille4.github.com/Scribl/ and is implemented in JavaScript with all modern browsers supported.

Contact: gabor.marth@bc.edu

A step towards the “virtual observatory” model of modern astronomy. Free remote access to data in astronomy has long been a fact. It was soon realized that access to data wasn’t enough, remote users needs the power of remote clusters to process large amounts of data.

The intermediate stage of remote access to data and even remote processing models are both going to require easy visualization capabilities.

Are you ready to move to remote access to topic map data?

December 18, 2012

HTML5 and Canvas 2D – Feature Complete

Filed under: HTML5,Web Applications,Web Browser,WWW — Patrick Durusau @ 6:08 am

HTML5 and Canvas 2D have been released as feature complete drafts.

Not final but a stable target for development.

If you are interested in “testimonials,” see: HTML5 Definition Complete, W3C Moves to Interoperability Testing and Performance

Personally I prefer the single page HTML versions:

HTML5 singe page version.

The Canvas 2D draft is already a single page version.

Now would be a good time to begin working on how you will use HTML5 and Canvas 2D for delivery of topic map based information.

December 13, 2012

HTML+RDFa 1.1

Filed under: HTML5,RDFa — Patrick Durusau @ 4:32 pm

HTML+RDFa 1.1 Support for RDFa in HTML4 and HTML5

Abstract:

This specification defines rules and guidelines for adapting the RDFa Core 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.

December 4, 2012

node-webkit

Filed under: CSS3,HTML5,Interface Research/Design,Javascript — Patrick Durusau @ 10:14 am

node-webkit

From the webpage:

node-webkit is an app runtime based on Chromium and node.js. You can write native apps in HTML and Javascript with node-webkit. It also lets you to call Node.js modules directly from DOM and enables a new way of writing native applications with all Web technologies.

Will HTML5 and Javascript, via apps like node-webkit free users from developer based interfaces?

Developer based interfaces are intended to be useful for others, or at least I suspect so, but quite often fall short of the mark.

Apps like node-webkit should encourage rapid prototyping and less reluctance to trash yesterday’s interface code. (I said “should,” whether it will or not remains to be seen.)

Rather than a “full featured” topic map editor, how would you divide the task of authoring a topic map into pieces?

I first saw this in Christophe Lalanne’s A bag of tweets / November 2012.

October 9, 2012

WebPlatform.org [Pump Up Web Technology Search Clutter]

Filed under: CSS3,HTML,HTML5 — Patrick Durusau @ 2:58 pm

WebPlatform.org

From the webpage:

We are an open community of developers building resources for a better web, regardless of brand, browser or platform. Anyone can contribute and each person who does makes us stronger. Together we can continue to drive innovation on the Web to serve the greater good. It starts here, with you.

From Matt Brian:

In an attempt to create the “definitive resource” for all open Web technologies, Apple, Adobe, Facebook, Google, HP, Microsoft, Mozilla, Nokia, and Opera have joined the W3C to launch a new website called ‘Web Platform

The new website will serve as a single source of relevant, up-to-date and quality information on the latest HTML5, CSS3, and other Web standards, offering tips on web development and best practises for the technologies.

I first saw this at the Semanticweb.com (Angela Guess).

So, maybe having documentation, navigable and good documentation, isn’t so weird after all. 😉

Assume I search for guidance on HTML5, CSS3, etc. Now there is a new site to add to web technology search results.

Glad to see the site, but not the addition to search clutter.

I suppose you could boost the site in response to all searches for web technology. Wonder if that will happen?

Doesn’t help your local silo of links.

October 2, 2012

Torque for mapping temporal data

Filed under: Graphics,HTML5,Mapping,Temporal Data,Visualization — Patrick Durusau @ 2:49 pm

Torque for mapping temporal data by Nathan Yau.

From the post:

Mapping data over time can be challenging, especially when you have a lot of data to load in the beginning. Torque, the new open source project by CartoDB, is a step towards making the process easier.

Torque allows you to create beautiful visualizations with big temporal datasets by bundling HTML5 browser rendering technologies with a generic and efficient temporal data transfer format created using the CartoDB SQL API. Torque visualisations work on desktop and ipads, and work well on temporal datasets with hundreds of thousands or even millions of datapoints.

Isn’t data always mapped over time?

Data always originates at a time, observed at a time, recorded at a time (by an observer, mechanical or otherwise), is valid through a time, etc.

We may omit time for some reason or purpose but that is our choice.

September 7, 2012

HTML5: Render urban population growth on a 3D world globe with Three.js and canvas

Filed under: HTML5,Maps,Marketing,Three.js — Patrick Durusau @ 2:47 pm

HTML5: Render urban population growth on a 3D world globe with Three.js and canvas By jos.dirksen.

From the post:

In this article I’ll once again look at data / geo visualization with Three.js. This time I’ll show you how you can plot the urban population growth over the years 1950 to 2050 on a 3D globe using Three.js. The resulting visualization animates the growth of the world’s largest cities on a rotating 3D world. The result we’re aiming for looks like this (for a working example look here.):

Possible contender for the topic map graphic? A 3D globe?

If you think of topic maps as representing a users world view?

Perhaps, perhaps, but then you will need a flat earth version for some users as well. 😉

August 30, 2012

HTML5 Boilerplate

Filed under: HTML5,Interface Research/Design — Patrick Durusau @ 2:17 pm

HTML5 Boilerplate

From the website:

HTML5 Boilerplate helps you build fast, robust, and adaptable web apps or sites. Kick-start your project with the combined knowledge and effort of 100’s of developers, all in one little package.

If this helps you roll out test web pages quickly, good.

If you prefer another package, please post a pointer.

August 26, 2012

HTML5, Apps and JavaScript Video

Filed under: HTML5,Javascript — Patrick Durusau @ 3:34 pm

HTML5, Apps and JavaScript Video by Brad Stenger.

From the post:

Here are the videos from last week’s TimesOpen event on HTML5, Apps and JavaScript:

If you missed the TimesOpen event on August 15th on HTML5, Apps and JavaScript, videos have been posted!

In case you are curious about good days to be in New York City in the near future, check out:

Times Open. (There’s some other reason to go to New York?)

August 18, 2012

Creating Your First HTML 5 Web Page [HTML5 – Feature Freeze?]

Filed under: HTML,HTML5,WWW — Patrick Durusau @ 4:06 pm

Creating Your First HTML 5 Web Page by Michael Dorf.

From the post:

Whether you have been writing web pages for a while or you are new to writing HTML, the new HTML 5 elements are still within your reach. It is important to learn how HTML 5 works since there are many new features that will make your pages better and more functional. Once you get your first web page under your belt you will find that they are very easy to put together and you will be on your way to making many more.

To begin, take a look at this base HTML page we will be working with. This is just a plain-ol’ HTML page, but we can start adding HTML5 elements to jazz it up!

But that’s not why I am posting it here. 😉

A little later Michael says:

The new, simple DOCTYPE is much easier to remember and use than previous versions. The W3C is trying to stop versioning HTML so that backwards compatibility will become easier, so there are “technically” no more versions of HTML.

I’m not sure I follow on “…to stop versioning HTML so that backwards compatibility will become easier….”

Unless that means that HTML (5 I assume) is going into a feature/semantic freeze?

That would promote backwards compatibility but I am not sure is a good solution.

Just curious if you have heard the same?

Comments?

July 8, 2012

Collection of CSS3 Techniques and Tutorials

Filed under: CSS3,HTML5 — Patrick Durusau @ 9:23 am

Collection of CSS3 Techniques and Tutorials

From the post:

For today I have selected few fresh and useful CSS3 tutorials for your next project. CSS3 and HTML5 are the topics that you see and hear everyday and I think it is the right time to start diving into it. While there is no freedom in expressing our ideas in CSS3 prior to weak support in major browsers we want to be the first ones when it is fully supported right? Besides chasing the trends you will gain valuable experience in HTML5 and jQuery which will help you to solve your problems in your projects.

This techniques can be proficiently functioned using markup, HTML, and some improved properties of CSS3. It has many features which are not compatible with the old web browsers and hence it will require some present day internet browsers like Internet Explorer 7 & 8, Chrome, Safari and Firefox to use the CSS3. It can be used in developing the following techniques:

  • It can be used to create multiple backgrounds
  • Developing and drawing border images
  • Handling of opacity
  • Used in text- shadowing and box sizing
  • Used for support of columns of many different web layouts.

If we go back on time we will realize how far we have come from the time of Adobe’s Flash and JavaScript, which were used to create some cool designs. Then came the new version of CSS and it was CSS3 that has transformed the world of animation with its transition features. It is the markup language that has many other applications that can be used for designing web pages that are written in XHTML or HTML. Whereas on the other hand, CSS is made for primary separation of documents that are written in simple markup languages. The content accessibility provides elements which can differ from fonts to layouts and colors.

In this compilation you will find few tutorials on creating amazing transition effects, slideshows, navigation menus and much more.

However clever your models, searching/extraction protocols, etc., there will come a time when results have to be delivered.

Graphs, charts, visualizations, networks, static and interactive will play a role, but so will basic web design/delivery techniques.

You should be aware of what is possible, should you decide to out source the design task.

This collection illustrates the range of modern web presentations. Will also make you wonder about some of the web presentations you encounter.

I first saw this at DZone.

February 27, 2012

Best Online Tools to Make Simple HTML5 Coding

Filed under: HTML5 — Patrick Durusau @ 8:24 pm

Best Online Tools to Make Simple HTML5 Coding

From the post:

HTML which stands for Hypertext mark-up language is supposed to be the main language for web pages. Hence the purpose of a web browser is to read the HTML documents and then compose them into either audible or visible websites.

HTML or Hypertext mark-up language is the main languages used for web pages. It is written in the form of tags enclosed in angle brackets. It is written within the web page content. Mostly these HTML elements are used in pairs but some that are known as empty elements are used unpaired also.

HTML5 is a language that used to create web pages, its fifth revision of HTML, a core technology of internet and basic language of designing. This advanced technology has some new features and tags that presents website designs with special effects and awesome layouts. HTML5 adds many new syntactical features.

These include the <video>, <audio>, <header> and <canvas> elements, as well as the integration of SVG(Scalable Vector Graphics) content. Today on internet, thousand of websites are available on internet having attractive designs so I have choose some great piece work of designers. I hope you will love to see this beautiful collection.

Today we cover some best online tools that helps developers to make easy and simple HTML5 coding. In this list we featured HTML5 cheat sheets, HTML5 website generator, HTML5 demos and examples, etc. Visit this list and share your thought in our comment section below.

Even if you aren’t in the web design end of things, it doesn’t hurt to have a general idea of what is easy to be done. And some idea of how to do it if you are the only one available if something breaks.

Some interesting tools. Are there others you prefer?

February 11, 2012

Flotr2

Filed under: Graphics,HTML5 — Patrick Durusau @ 7:29 pm

Flotr2

From the documentation:

Flotr2 is a library for drawing HTML5 charts and graphs. It is a branch of flotr which removes the Prototype dependency and includes many improvements.

Features:

  • mobile support
  • framework independent
  • extensible plugin framework
  • custom chart types
  • FF, Chrome, IE6+, Android, iOS
  • lines
  • bars
  • candles
  • pies
  • bubbles

See the website for some interesting (non-static) examples.

Powered by WordPress