order of references

specification/trace/sdk_exporters/jaeger.md

@@ -86,9 +86,12 @@ MUST be recorded as a `SpanReference` of type `CHILD_OF`, e.g.:
     )
 ```
 
+This span reference MUST be the first in the list of references.
+
 ### SpanKind
 
-OpenTelemetry `SpanKind` field MUST be encoded as `span.kind` tag in Jaeger span.
+OpenTelemetry `SpanKind` field MUST be encoded as `span.kind` tag in Jaeger span,
+except for `SpanKind.INTERNAL`, which SHOULD NOT be translated to a tag.
 
 | OpenTelemetry | Jaeger |
 | ------------- | ------ |
@@ -145,6 +148,9 @@ in Jaeger explicitly. The exporter MAY additionally convert `Link`(s) to span `L
 * set Log tags `trace_id` and `span_id` from the respective `SpanContext`'s fields
 * store `Link`'s attributes as Log tags
 
+Span references generated from `Link`(s) MUST be added _after_ the span reference
+generated from [Parent ID](#parent-id), if any.
+
 ### Events
 
 Events MUST be converted to Jaeger Logs. OpenTelemetry Event's `time_unix_nano` and `attributes` fields map directly to Jaeger Log's `timestamp` and `fields` fields. Jaeger Log has no direct equivalent for OpenTelemetry Event's `name` and `dropped_attributes_count` fields but OpenTracing semantic conventions specify some special attribute names [here](https://github.com/opentracing/specification/blob/master/semantic_conventions.md#log-fields-table). OpenTelemetry Event's `name` and `dropped_attributes_count` fields should be added to Jaeger Log's `fields` map as follows: