Use id/type instead of @id/@type

[azaroth42]

Schema.org, Social Web / ActivityStreams, Annotation WG will all adopt this.
Manu, danbri, tantek, etc all agree.

There will be a best practices document published from W3C that states this

[azaroth42]

Upstream issues:

• Emerging best practice is to use id/type aliases for @id/@type w3c/web-annotation#88
• Please alias @id and @type to 'id' and 'type' w3c/activitystreams#232
• JSON-LD emerging best practice is to alias @type, @id (and other keywords) schemaorg/schemaorg#854

[azaroth42]

We should confirm that we're going to do this to avoid future discussion.
My vote: 👍

[mikeapp]

👍

[jpstroop]

👍

[tomcrane]

👍 - Went down well in The Hague

[zimeon]

👍 - I was a little concerned about the churn this causes in code using the JSON but speaking with developers @ The Hague they seemed to see the change as a net benefit

[azaroth42]

Discussion on 8/2/17: Agreement. Need to make it clear that P3 + I2 will run into both.

Could we add id and type as well as leaving in @id and @type in Image 2.2? Fewer implementations of actual processors for image -- leaflet and OSD can support both and no one will notice :)

[jpstroop]

See also: #1064

[azaroth42]

Manifest could consistently use id as it just gets fed to the Image processor anyway. Support from @jronallo and @mejackreed for this, as implementers.

[zimeon]

👍 agreed at Toronto WG meeting

[azaroth42]

Done for Presentation, removing the tag, but leaving open until all the other specs catch up.

[azaroth42]

Tagging principles to document as a design pattern.

[azaroth42]

Propose that this will be closed by documenting the principle, that we will then stick to.
E.g. by #1510

[zimeon]

👍 Agree that this is already addressed in the v3 specs, can close by documenting principle in #1510

[tomcrane]

👍