Add "Braille"

[dr0i]

Using "name" instead of "label" makes the labels exported to context.json.

This seems strange because:

1. we have many definitions of Uris using "label" instead of "name"
2. I think somewhere in the code is a fallback for "name" when "name" is missing so "label" is used.

However I now I grasped once the idea of the difference between "name" and "label", but it's lost to me again. Maybe this "label-name" thing should be made simpler by dropping one definition, it seems superflous @jschnasse ?

See #897.

[jschnasse]

Hi there,

ok, I admit this is confusing. We have two cases here:

1. Json-Ld shortenings (part of Json-Ld spec)
2. Labels that are used within our JsonConverter to implement the sidecar approach

1. is part of the Json-LD spec and allows the introduction of shortenings into the context like:

type: @type

Which tolds the JSON-LD processor to replace occurrences of 'type' with '@type' in a Json-Ld document when processed as rdf .
Shortenings can also be introduced with etikett.
Example
etikett.json

 {
      "multilangLabel" : {},
      "uri" : "http://purl.org/lobid/lv#ArchivedWebPage",
      "name" : "ArchivedWebPage"
}

renders to
context.json

"ArchivedWebPage" : {
      "@id" : "http://purl.org/lobid/lv#ArchivedWebPage"
 }

Which the Json-Ld processor takes as a shortening to replace occurrences of ArchivedWebPagewith http://purl.org/lobid/lv#ArchivedWebPage

2. Is part of our own JsonConverter implementation
We use entries like

 {
        "uri": "http://marc21rdf.info/terms/continuingfre#d",
        "label": "täglich"
}

to add labels according to the sidecar approach

In your case you wanted to introduce a shortening to make the Json-Document more readable/indexable. In this case you have to define a name for the Json-Ld processor. Labels on the other hand are for the JsonConverter and will occur in form of label fields` to sidecar the actual rdf uri.

Sincerely yours
Jan

[ChristophEwertowski]

Will be dealt with in #884.