gbv / aref Goto Github PK

IRIs as predicates and subjects should be more lax than object IRIs. The definition

"IRI that does not match any of the grammar rules languageTaggedString or datatypedString"

is wrong anyway, because string "@" should also be excluded.

With http://yamltojson.com/ for dynamic conversion.

See http://gbv.github.io/aREF/aREF.html#namespace-maps (TODO)

@nichtich ,

from the spec I cannot falsify if this is possible:

---
http://example.com/people#alice:
    _ns:
        foaf: http://xmlns.com/foaf/0.1/
    a: foaf_Person

instead of:

---
_ns:
    foaf: http://xmlns.com/foaf/0.1/
http://example.com/people#alice:
    a: foaf_Person

If the first example is possible. What is the scope of the namespace map? In scope of the graph or in scope of the whole document?

---
http://example.com/people#alice:
    _ns:
        foaf: http://xmlns.com/foaf/0.1/
    a: foaf_Person
http://example.com/people#bob:
    a: foaf_Person

The RDFa-1.1 specification includes a list of default namespace/prefix mappings that could be reused instead of redefining the list for aREF [1].

[1] http://www.w3.org/2011/rdfa-context/rdfa-1.1

Circular aREF documents cannot be serialized in JSON [...]

Why is it? Isn't this a circular (self referencing) document:

{
    "http://example.com/people#alice": {
        "foaf_knows": "http://example.com/people#alice"
    }
}

@nichtich

The Talis specification has been migrated to W3C as a Working Group Note (07 November 2013) that could be referenced instead of the Talis link [1]. The W3C are heavily dependent on JSON-LD, so they discourage the use of RDF/JSON but they have committed to it as a Note at least.

[1] http://www.w3.org/TR/2013/NOTE-rdf-json-20131107/

A decoding algorithm from aREF to triples (in pseudo-code) should help implementors and show the simplicity of aREF (e.g. compared to JSON-LD).

Sequences and bags

• bibo_authorList.rdf__1.foaf_name
• bibo_authorList.rdf__2.foaf_name
• bibo_authorList.rdf__3.foaf_name
• ...

Lists

• bibo_authorList.rdf_first.foaf_name
• bibo_authorList.rdf_rest.rdf_first.foaf_name
• ...

Could be solved by special keywords:

• bibo_authorList._member.foaf_name # rdfs_member, rdf__n, rdfs_first...
• bibo_authorList._all.foaf_name
• bibo_authorList._.foaf_name
• bibo_authorList._seq.foaf_name
• bibo_authorList._bag.foaf_name
• bibo_authorList._list.foaf_name

Only for properties, as used in RDF::YAML, see https://metacpan.org/source/AUTRIJUS/RDF-YAML-0.11/t/sample.yml

Since aREF defines no format, there is no simple MIME type. An explanation and suggestions would still be helpful.

• RDF/XML is application/rdf+xml
• JSON-LD is application/ld+json
• RDF/JSON is application/rdf+json
• Turtle is text/turtle
• N-Triples is application/n-triples
• N-Quads is application/n-quads
• TriG is application/trig
• TriX is application/trix
• YAML is text/x-yaml or text/yaml or application/x-yaml or application/yaml
• JSON is application/json
• Perl code is text/x-perl
• ASN.1 encodings e.g. application/ber-stream for BER
• INI file has no MIME type
• ...

Suggestions

See also http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-regs-14#section-6 for official MIME suffixes. yaml is not registered yet.

• aREF in YAML:
  • application/rdf+yaml
• aREF in JSON:
  • application/rdf+aref+json
  • application/json+aref

...

separated with | (or-expression). Order of items should be respected.

• http://jenit.github.io/linked-csv/
• Maybe some kind-of-rant like http://manu.sporny.org/2014/json-ld-origins-2/?

Examples could also be put in another document or into an appendix.