Comments (8)
There seems to be some editorial problem. The table of content of the ED indeed does not include the section on the DOM API, but the text itself does.
(The TOC refers to section 6 for the conversion to other formats; in the text section 6 is the DOM API, and section 7 is the conversion section...)
from microdata.
@iherman wrote
There seems to be some editorial problem. The table of content of the ED indeed does not include the section on the DOM API, but the text itself does.
That is a problem indeed. I'll fix it later today and request that we reset the CfC.
My apologies...
from microdata.
The ToC has been fixed. Re-opening this CFC with an extended deadline.
from microdata.
+1 (both to the original CFC, and the changes of @chaals)
from microdata.
-1 (will update with more comments)
tl;dr: is legacy, waste of W3C resources (CR, test suite etc.), relitigates already resolved issue from previous HTMLWG, and lastly wastes time duplicating yet another WHATWG spec.
Compromise: Ok to update existing W3C Microdata NOTE instead, with dropping DOM APIs etc.
from microdata.
+1 including above fix
from microdata.
Thanks for taking time to respond @tantek.
Your concerns naturally echo those raised by Mozilla during the WebPlat charter review. At the time it was noted that Microdata is supported by multiple major search engines - two of which, Yandex and Google, have offered editors - and that
it is used on a substantial percentage of sites on the web.
The W3C has already chartered WebPlat to move Microdata onto the Rec track. Your objection asks us to ignore the AC and our charter, but that is not something we can do.
from microdata.
The FPWD was published on May 4
from microdata.
Related Issues (20)
- Global Identifier
- Values section title odd
- Textual property value does not use language of the element HOT 4
- No description of how numeric property values are obtained. HOT 12
- Incomplete sentence: "User agents are"
- Syntax highlighting not working correctly HOT 12
- Capitalization of "microdata"
- give examples and algorithms a URL HOT 1
- Provide an example of itemid
- incomplete sentence "User agents are" HOT 2
- RDFa and JSON-LD are not equivalent HOT 12
- RDFa should generate to RDFa Lite HOT 4
- Use the same example for JSON-LD and RDFa HOT 6
- Reference to [microdata-rdf] should be changed HOT 13
- Reusing components in different contexts HOT 4
- itemref as a url, not just an ID within the same document
- "Valid" definition doesn't resolve
- "Our company" example is confusing
- Hedral the Cat HOT 1
- Hedral Issue 2 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from microdata.