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

typo in Protocol: rdf:label #77

Closed
VladimirAlexiev opened this issue Sep 14, 2015 · 6 comments
Closed

typo in Protocol: rdf:label #77

VladimirAlexiev opened this issue Sep 14, 2015 · 6 comments
Assignees
Labels

Comments

@VladimirAlexiev
Copy link

http://w3c.github.io/web-annotation/protocol/wd/#container-retrieval-requirements: "human readable label using the rdf:label predicate".
Should be rdfs:label.

@azaroth42
Copy link
Collaborator

@BigBlueHat
Copy link
Member

@azaroth42 do you recall why label was chosen over name--which is what AS2 is using?

@BigBlueHat
Copy link
Member

BigBlueHat commented Jun 2, 2016

Ah....think I found it in their vocab document:

The name MAY be expressed using multiple language-tagged values.

...for which one can also substitute their unique nameMap thing...

@azaroth42
Copy link
Collaborator

rdfs:label is more widely used than as:name (obviously, as AS hasn't even gone into CR yet) so in terms of stability and likelihood that it will be understood, rdfs:label seems more appropriate.

Unless you mean the JSON-LD key for rdfs:label as label?

@BigBlueHat
Copy link
Member

@azaroth42 I suppose I meant both...actually. 😄 The rdfs:label selection makes sense over as:name, but I'm curious ('cause I don't remember) if we discussed using schema:name instead.

As far as the JSON-LD level keys...label vs. name vs. title (from Atom or HTML for instance)...I'm not sure it matters terribly. Preference being to surface the friendliest version of whatever term is used underneath--so in this case label is perfect as rdfs:label is underneath.

@iherman
Copy link
Member

iherman commented Jun 3, 2016

Propose to leave this as label

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

No branches or pull requests

4 participants