Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Syntax section #24

Open
3 tasks
cshaa opened this issue Aug 13, 2013 · 5 comments
Open
3 tasks

Adding Syntax section #24

cshaa opened this issue Aug 13, 2013 · 5 comments

Comments

@cshaa
Copy link
Contributor

cshaa commented Aug 13, 2013

Here, in the HTML6 documentation, there is nearly no desc. of the syntax - only a reference to HTML5 and the Section 4 - Tag types. But full documentation has to include it.
Here's a list of syntax articles:

  • what is a tag, what are attributes
    • tag in layman's terms
    • tag types [PARTIALLY]
    • attributes in layman's terms
    • normative description of tag
    • normative description of attributes
    • regular expersion
  • namespaces (+how to include)
  • how to parse wrong code

At this point we don't know anything about namespaces. Will there be something like xmlns? Or will they be included in doctype like this: <!DOCTYPE html,form>? And what languages to use to define new namespaces?

@OscarGodson
Copy link
Owner

Only the two you mentioned, and yes, we for sure should have a syntax. section.

@OscarGodson
Copy link
Owner

And, I don't think we need to include it in the DOCTYPE. The point of having namespaces is that you, as a developer, don't have to worry about future namespaces. Is there a benefit you see in having them manually listed out?

@philandy
Copy link

Could we make the DOCTYPE an attribute of the html tag?

@cshaa
Copy link
Contributor Author

cshaa commented Aug 22, 2013

@OscarGodson Listing namespaces is just a XML habit. It's useful for browser - to know what API to load. Eg <!DOCTYPE html,svg> would mean load "html" and "svg" APIs. If you wouldn't list it, browser would treat svg tags as ordinary semantic tags and therefore would not render the picture.
@philandy Yep, thats also a solution.

@philandy
Copy link

@m93a, Oscar's HTML6 is not XHTML; we should be able to assume default behavior for certain tags beyond the namespaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants