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

[I18N] Examples provide no language or direction metadata #958

Open
aphillips opened this issue Jun 24, 2019 · 5 comments
Open

[I18N] Examples provide no language or direction metadata #958

aphillips opened this issue Jun 24, 2019 · 5 comments
Labels
dcat feedback Issues stemming from external feedback to the WG future-work issue deferred to the next standardization round

Comments

@aphillips
Copy link

Examples 1-5 (for example)
https://www.w3.org/TR/2019/WD-vocab-dcat-2-20190528/#ex-catalog

Examples in the document do not include language or direction metadata, even though they contain natural language strings. Example 1 shows the way:

:catalog
  a dcat:Catalog ;
  dct:title "Imaginary Catalog" ;
  rdfs:label "Imaginary Catalog" ;
  foaf:homepage <http://example.org/catalog> ;
  dct:publisher :transparency-office ;
  dct:language <http://id.loc.gov/vocabulary/iso639-1/en>  ;
  dcat:dataset :dataset-001  , :dataset-002 , :dataset-003 ;
  .

While this example does include a language value, other examples do not. There is also no mention of direction metadata, a gap in linked data that I18N is working on with multiple groups currently.

[This comment is part of the I18N horizontal review.]

@davebrowning
Copy link
Contributor

davebrowning commented Jul 23, 2019

Language tags added in #1007

@davebrowning
Copy link
Contributor

Thanks for the feedback - we've taken the comments on board and addressed the language tag point.

On direction metadata - in principle we're supportive of this but after WG/DCAT editor review and discussion, and given the limited time and specific skills, we'd look to consider provision of suitable examples in future versions or in an associated primer (assuming there is the will for that WG/CG to address).

This isssue will remain open and be moved to the 'Future Work' milestone.

@davebrowning davebrowning added the future-work issue deferred to the next standardization round label Sep 25, 2019
@aphillips
Copy link
Author

Thanks for adding language tags to the examples. For extra credit in future updates, try using some non-English exampled :-)

For direction metadata, proposals at the JSON-LD level are moving forward, but there remains no solution at the RDF level. Keeping this for "future-work" is a satisfactory solution for your CR transition. Thanks.

@agbeltran
Copy link
Member

Hi @aphillips, could you let us know about the status of the JSON-LD and RDF representations of direction metadata?

@riccardoAlbertoni
Copy link
Contributor

This issue was discussed in the last DCAT submeeting [1].
The document available at [2] states that the text direction problem must be solved on the RDF level and analyzes possible alternatives. Therefore, DCAT expects to inherit a solution for expressing text direction from RDF.

We keep this issue open and move it as future work, as we might want to integrate the DCAT examples when the solution is made available.

[1]https://www.w3.org/2022/05/03-dxwgdcat-minutes
[2]https://w3c.github.io/rdf-dir-literal/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dcat feedback Issues stemming from external feedback to the WG future-work issue deferred to the next standardization round
Projects
None yet
Development

No branches or pull requests

5 participants