Processing then begins with the root element, and all nodes in the tree are processed according to the following rules, depth-first:

Any changes to the [current evaluation context] are made first:

the [current element] is parsed for [URI mappings] and these are added to the [list of URI mappings]. Note that a [URI mapping] will simply overwrite any current mapping in the list that has the same name;
These mappings are provided by the xmlns atttribute. The value to be mapped is set by the XML namespace prefix, and the value to map is the value of the attribute--a URI. Note that the URI is not processed in any way; in particular if it is a relative path it is not resolved against the [current base]. Authors are advised to follow best practice for using namespaces, which includes not using relative paths. (See [xyz].)
the [current element] is parsed for any language information, and [language] is set in the [current evaluation context];
Language information can be provided using either the general-purpose XML attribute, xml:lang, or the HTML attribute lang.
the [current element] is parsed for any subject information, and it is used to set the [current resource] value, in the [current evaluation context];
The [current resource] can be set using @about. Note that the final value of the [current resource] is an absolute URI, which means that if @about contains a relative path the value must be normalised against [base] in the [current evaluation context], using the algorithm defined in RFC 3986.
The flag [chaining] is set to true; the [change resource] flag is set to false

Once the [current evaluation context] has been set, object resolution is carried out, as follows:

the [current object resource] is established;
Since only one [current object resource] is set per element then some attributes will have a higher priority than others. The highest priority is given to the RDFa attribute resource. If there is no resource attribute then the HTML src attribute is used, and if that is not present, the HTML href attribute is used. If none of these are present then a unique identifier or [bnode] is created. Note that the final value of the [current object resource] is an absolute URI, which means that if any of these attributes contain relative paths they must be normalised against [base] in the [current evaluation context], using the algorithm defined in RFC 3986.
the [current object literal] is established;
The [current object literal] will be set as a [plain literal] if the content attribute is present, or the body of the [current element] contains only text (i.e., there are no child elements), or the body of the [current element] does have child elements but the datatype attribute has an empty value. Additionally, if there is a value for [current language] then the value of the [plain literal] should include this language information, as described here:???. The actual literal is either the value of the content attribute (if present) or a string created by concatenating the inner content of each of the children in turn, of the [current element].

The [current object literal] will be set as a [typed literal] if the datatype attribute is present, and does not have an empty value. The actual literal is either the value of the content attribute (if present) or a string created by concatenating the inner content of each of the children in turn, of the [current element]. The final string includes the datatype, as described here:???

The [current object literal] will be set as an [XML literal] if the [current element] has child elements, and the datatype attribute is not present. The value of the [XML literal] is a string created from the inner content of the [current element], i.e., not including the element itself.

Once object resolution is complete the processor will have two objects, one a resource and the other a literal. These objects can now be used to create triples with the [current resource], depending on the presence of other attributes. This is achieved using the following processing steps:

predicates for the [current object literal] are established;
Predicates for the [current object literal] can be set by using the property attribute. If present, the attribute must contain one or more [basic curies], each of which is converted to an absolute URI using CURIE processing rules, and then used to generate a triple as follows:

subject

[current resource]

predicate

expanded value from the basic curie

object

[current object literal]

Note that literal may include language and datatype information as discussed in the section on object resolution.

If any triples are generated and if the content attribute is not present then the [chaining] flag is set to false
type values for the [current object resource] are established;
One or more 'types' for the [current object resource] can be set by using the instanceof attribute. If present, the attribute must contain one or more [basic curies], each of which is converted to an absolute URI using CURIE processing rules, and then used to generate a triple as follows:

subject

[current object resource]

predicate

http://www.w3.org/1999/02/22-rdf-syntax-ns#type

object

expanded value from the basic curie

If any triples are generated then the [chaining] flag is set to true.
predicates for the [current object resource] are established;
Predicates for the [current object resource] can be set by using one or both of the @rel and @rev attributes.
If present, the rel attribute must contain one or more [basic curies], each of which is converted to an absolute URI using CURIE processing rules, and then used to generate a triple as follows:

subject

[current resource]

predicate

expanded value from the basic curie

object

[current object resource]

If present, the rev attribute must contain one or more [basic curies], each of which is converted to an absolute URI using CURIE processing rules, and then used to generate a triple as follows:

subject

[current object resource]

predicate

expanded value from the basic curie

object

[current resource]

If any triples are generated then the [chaining] flag is set to true.
If any triples are generated then the [change resource] flag is set to true.

If the [chaining] flag is set to true then the [current resource] is set to the value of the [current object resource], and the [chaining] flag is set to false.
If the [change resource] flag is set to true then the [current resource] is set to the value of the [current object resource]

type values for the [current resource] are established;

One or more 'types' for the [current resource] can be set by using the instanceof attribute. If present, the attribute must contain one or more [basic curies], each of which is converted to an absolute URI using CURIE processing rules, and then used to generate a triple as follows:

subject: [current resource]
predicate: http://www.w3.org/1999/02/22-rdf-syntax-ns#type
object: expanded value from the basic curie

The [current evaluation context] is pushed onto a stack.

If [chaining] flag is true, the depth-first processing of the child nodes continue, otherwise the process ends (for the [current element])

NOTE: The recursive aspect of this needs to be explained a little better, in particular when we get stuff back off the stack.