regarding JSON-LD is,
AFAICT, extracting JSON-LD embedded in HTML:
http://www.w3.org/TR/json-ld/#embedding-json-ld-in-html-documents
It would be awesome if support for that would be added as well.
--
Markus Lanthaler
@markuslanthaler
] http://www.w3.org/Protocols/HTTP/Fragment/draft-bos-http-redirect-00.txt
[2]
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-7.1.2
--
Markus Lanthaler
@markuslanthaler
: schema:knows,
resource: /markus/friends
}
}
It could also be tweaked into something like
{
@id: /markus,
hasRelationshipIndirector: {
schema:knows: /markus/friends
}
}
so that it works nicely with property paths.
--
Markus Lanthaler
@markuslanthaler
not say that the members of /people/markus/friends are related to
/people/markus via foaf:knows.
But perhaps you had something completely different in mind!?
--
Markus Lanthaler
@markuslanthaler
?
It would be really helpful if answers to these questions could be given by the
schema.org sponsors.
--
Markus Lanthaler
@markuslanthaler
On Sunday, March 30, 2014 9:14 AM, Pat Hayes wrote:
On Mar 29, 2014, at 8:10 PM, Peter F. Patel-Schneider wrote:
On 03/29/2014 03:30 PM, Markus Lanthaler wrote:
Schema.org doesn't suffer from this issue as much as other vocabularies
do as it isn't defined with RDFS but uses its own, looser
in the
friends list.
When Markus is a very popular guy the list can also be paginated.
Hope that makes sense.
Yes it does. It is, however, just a variation of Niklas' proposal... however
with more commonly known properties.
--
Markus Lanthaler
@markuslanthaler
old JSON services to be upgraded
to JSON-LD+Hydra services by just adding a context to the JSON
representations, i.e., without breaking existing clients.
--
Markus Lanthaler
@markuslanthaler
if it would be state explicitely that the range also
include collections/lists.
3. RDFS and OWL reasoning will work on schema:knows.
No, not in the case of schema but there are other vocabularies where it is
important.
And sorry, this is impossible.
Yes, unfortunately.
--
Markus Lanthaler
On Tuesday, March 25, 2014 7:25 PM, Niklas Lindström wrote:
On Tue, Mar 25, 2014 at 6:58 PM, Markus Lanthaler wrote:
OK.. this is quite similar to what we discussed in the Hydra CG
(and what LDP does):
/markus a schema:Person ;
/markus/friends/:manages [
:subject
/ .
/markus schema:knows /alice .
So, how would I link from /markus to /markus/friends?
--
Markus Lanthaler
@markuslanthaler
in the context
of this discussion. That's exactly the reason why I included the quite
explicit plea in my first mail:
please let's not talk about hash URLs etc. here, ok?
So, please. Let's try to focus on the problem at hand.
Thanks,
Markus
--
Markus Lanthaler
@markuslanthaler
On Mar 25
(schema:knows).
--
Markus Lanthaler
@markuslanthaler
regards,
Haschek
PS: as this is my first post to this group, I add a short info about me
(don't know if it is necessary here):
Michael Haschke, born in Leipzig, studied worked in the AKSW at Uni
Leipzig on the OntoWiki GUI
the semantic condition could be published as a reference at
:listPropertyOf?
--
Markus Lanthaler
@markuslanthaler
Pat Hayes
On Mar 24, 2014, at 10:24 AM, Markus Lanthaler
markus.lantha...@gmx.net wrote:
Hi all,
We have an interesting discussion in the Hydra W3C Community Group
[1
to suggest to infer
the semantics based on the URL's structure, which is against the principle of
URI Opacity [1].
[1] http://www.w3.org/TR/webarch/#uri-opacity
--
Markus Lanthaler
@markuslanthaler
Original Message
On Tue Mar 25 2014 at 9:01:33 AM, Pat Hayes pha
tell the client at all why it
should follow schema:url links to /markus{n}. The same is more or less true
abut schema:sameAs.
--
Markus Lanthaler
@markuslanthaler
Voila! (With the big provisio that I have no idea whether the schema.org
processors actually dothe right thing here, asthere
Hi Niklas,
On Tuesday, March 25, 2014 5:21 PM, Niklas Lindström wrote:
On Tue, Mar 25, 2014 at 4:57 PM, Markus Lanthaler wrote:
On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
Would it be correct to summarize your question as, how do we enable
mechanical features like
On Tuesday, March 25, 2014 5:44 PM, Jason Douglas wrote:
On Tue Mar 25 2014 at 9:36:21 AM, Markus Lanthaler wrote:
On Tuesday, March 25, 2014 5:08 PM, Jason Douglas wrote:
I find that so awkward since :knows is already a repeated property.
Now we have denormalized semantics and queries
On Tuesday, March 25, 2014 7:04 PM, Peter F. Patel-Schneider wrote:
On 03/24/2014 08:24 AM, Markus Lanthaler wrote:
Hi all,
[snip]
Thanks,
Markus
P.S.: I'm aware of how LDP handles this issue, but, while I generally
like the approach it takes, I don't like that fact
,
Markus
P.S.: I'm aware of how LDP handles this issue, but, while I generally like
the approach it takes, I don't like that fact that it imposes a specific
interaction model.
[1] http://bit.ly/HydraCG
--
Markus Lanthaler
@markuslanthaler
do we enable
mechanical features like addressability and pagination to a value
collection in a way that doesn't interfere with its semantics (i.e.,
change the range)?
Yup, this sums it up quite well. Thanks.
--
Markus Lanthaler
@markuslanthaler
On Monday, December 16, 2013 10:15 AM, Alexander Dutton wrote:
On 15/12/13 12:16, Markus Lanthaler wrote:
[...]
The other trick you need to use is to map _links to a blank node
and set its container to @index so that doesn't get ignored. The
triples containing blank nodes as predicate
, and its children don't/,
which is the wrong way round for my use case.
Is there an answer?
I hope I gave you two above :-)
Cheers,
Markus
--
Markus Lanthaler
@markuslanthaler
Martynas,
This document may give you some of the rationales behind this decision:
http://wiki.whatwg.org/wiki/Why_not_conneg
Cheers,
Markus
--
Markus Lanthaler
@markuslanthaler
-Original Message-
From: Martynas Jusevičius [mailto:marty...@graphity.org]
Sent: Thursday
On Thursday, November 21, 2013 10:43 PM, Kingsley Idehen wrote:
On 11/21/13 4:18 PM, Markus Lanthaler wrote:
Anyway, do you have a URL for a Turtle doc?
No, as I said, at the moment I don't serve a Turtle version. Of
course you
can use a translator to turn the JSON-LD into Turtle (but you
such a statement. Thus you
need to use constructs such as hydra:Link and hydra:Resource to make the
distinction explicit.
Hope this helps. If not, let me know.
--
Markus Lanthaler
@markuslanthaler
-lanthaler.com/hydra/
[2] http://www.w3.org/community/hydra/
--
Markus Lanthaler
@markuslanthaler
On Thursday, November 21, 2013 5:06 PM, Kingsley Idehen wrote:
On 11/21/13 7:33 AM, Markus Lanthaler wrote:
Sure.. it's included at the end of the spec [1 above] and also available
as standalone JSON-LD file:
http://purl.org/hydra/core
Note, there's a content negotiation problem here
On Thursday, November 21, 2013 9:22 PM, Kingsley Idehen wrote:
On 11/21/13 2:00 PM, Markus Lanthaler wrote:
On Thursday, November 21, 2013 7:34 PM, Kingsley Idehen wrote:
But I am looking for Turtle, hence:
curl -ILH Accept: text/turtlehttp://purl.org/hydra/core
:-)
Sure
,
Markus
[1] https://github.com/HydraCG/Specifications/issues/15
[2] http://www.markus-lanthaler.com/hydra/api-demo/vocab
--
Markus Lanthaler
@markuslanthaler
Hi Kingsley,
On Thursday, November 21, 2013 1:16 PM, Kingsley Idehen wrote:
On 11/21/13 6:14 AM, Markus Lanthaler wrote:
Hi Ruben,
You probably already expected me asking this :-) Why not Hydra [1]?
[...]
[1] http://www.markus-lanthaler.com/hydra/
[2] http://www.w3.org/community
on the discussion to
date, we can discuss this further over there.
Awesome! Welcome on board :-)
[1] https://github.com/HydraCG/Specifications/issues/5
--
Markus Lanthaler
@markuslanthaler
On Thursday, November 21, 2013 7:37 PM, Kingsley Idehen wrote:
On 11/21/13 1:01 PM, Markus Lanthaler wrote:
Awesome! Welcome on board:-)
[1]https://github.com/HydraCG/Specifications/issues/5
SeeAlso:
http://linkeddata.uriburner.com/about/id/entity/https/github.com/HydraC
G
On Thursday, November 21, 2013 7:34 PM, Kingsley Idehen wrote:
On 11/21/13 12:46 PM, Markus Lanthaler wrote:
HTTP/1.1 200 OK
Server: cloudflare-nginx
Date: Thu, 21 Nov 2013 16:04:33 GMT
Content-Type: application/ld+json
All fine at my end though so everything should work. Or did I miss
34 matches
Mail list logo
