Update doc #57
Update doc #57
Conversation
| * image | ||
| * (will be others) | ||
| * url (a URL) | ||
| * displayName (skos:prefLabel) |
There was a problem hiding this comment.
displayName should be label, also we should add note to all the entities as well.
There was a problem hiding this comment.
There was a problem hiding this comment.
@ahdinosaur thanks, was having a hard time finding final decisions on some of these, makes sense it is in the context. Get it on note.
On label, did we decide to use label for people's names as well as group names? Doesn't seem right to me now. I get it if everything is just a graph on a page, but seems not so good for a domain vocab. (Sorry probably am bike shedding again.... or maybe all vocab work is that way? :) )
There was a problem hiding this comment.
yeah, i feel this. is there something that works for both? (i really like simplicity and consistency.) we want to represent skos:prefLabel, skos:altLabel, and skos:hiddenLabel. so maybe we do vf:name (as in Activity Streams and schema.org), vf:alternateName (as in schema.org), and vf:hiddenName?
There was a problem hiding this comment.
Well I thought vf:displayName wasn't too bad for both people and groups, and it was on elf's example json-ld. :) vf:name is fine with me too. I definitely agree it has to be the same for all kinds of agents. And that it should represent skos:prefLabel. Or are you thinking it should be the same for all nodes? Still the name stuff might work for that too. I did change it to label for now. Maybe we can see what the first user thinks? Or just make an executive decision without elf?
There was a problem hiding this comment.
i mean all nodes. pulled out into a proposal: valueflows/valueflows#101.
|
looks great @fosterlynn. 😄 made a comment about |
Updating the doc to help with NextEdge work. Review from @ahdinosaur and @pmackay would be greatly appreciated, with @elf-pavlik out of pocket.