Jon, right now since PDF doesn't have any support for "identifying the expected meaning for form input data" a PDF document wouldn't fail this. We should review and make sure that this is clear in the U doc.

I read the second qualifiying bullet

The content is implemented using technologies with support for identifying the expected meaning for form input data.

as being more precise than simply restricting to markup language. There may be a technology that is not a markup language that can still support meaning (i.e., PDF could add a new field to an input property that provided that ability). I think the status of PDF can be clarified in the Understanding document.

WG is going to update the Understanding document to make this more clear. (per 7/31/2018 call)

A website uses ARIA landmarks to identify the regions of the page, and users can hide areas that are not the 'main'.
The links in the navigation of a website are marked-up so that users can add their own icons.
Icons on a website use are marked-up so that the user can substitute their own icon set into the page.

Hi guys I’m working on this CS for AAA site need to know one thing. To we need to build the site with a ability to upload a icon or have multiple new user interface components icons (build in JavaScript and apply to all the new icon be selected). Support personalization and preferences?

Or

All we need to do is us microdata (https://www.w3.org/TR/microdata/) in the code and we pass the Conformance for cs 1.3.6?

The CS is not clear for Conformance.
I think we need one failures section here to make it clear.

Failures
The following are common mistakes that are considered failures of this Success Criterion by the WCAG Working Group.

Editorial re-write here: https://rawgit.com/w3c/wcag/identify-input-purpose-updates/understanding/21/identify-input-purpose.html

thanks @johnfoliot for your help.
the new editorial re-write cs 1.3.5 help to clear some off.
To we have any new Editorial re-write for cs 1.3.6 in the work ?

It looks like John's re-write has gone into the master and been published, so I'll close this.
A review & update of 1.3.6 is a useful thing, but not covered here.