Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 14 09:42
    KMax closed #66
  • Jun 14 09:42
    KMax commented #66
  • Jun 14 09:29
    csarven commented #66
  • Jun 14 09:25
    KMax commented #66
  • Jun 14 09:19
    csarven commented #66
  • Jun 14 09:16
    KMax starred w3c/ldn
  • Jun 14 09:16
    KMax opened #66
  • May 28 09:46
    ertugerata starred w3c/ldn
  • May 14 21:37
    QuantumCloudDatabase starred w3c/ldn
  • Apr 17 19:39
    salifm starred w3c/ldn
  • Mar 05 16:44

    plehegar on master

    Boilerplate files (compare)

  • Mar 05 14:51
    AntoniaWild starred w3c/ldn
  • Feb 03 17:03
  • Dec 04 2018 11:49

    csarven on master

    Remove unused CSS/JS in ED Change spacing from 4 to 2 (compare)

  • Oct 05 2018 07:02
    taurenshaman starred w3c/ldn
  • May 22 2018 03:15
    BlackGlory starred w3c/ldn
  • May 11 2018 19:16
    js-choi starred w3c/ldn
  • Mar 21 2018 14:59
    luismendes070 starred w3c/ldn
  • Mar 04 2018 17:20
    Visgean starred w3c/ldn
Xavier Sumba
@cuent
Great, it works. Thanks.
Sarven Capadisli
@csarven
@cuent What's your (FOAF) URI and homepage? I'd like to add you to the acknowledgements. It will show up in the Editor's Draft now.. and later on when that's pushed to w3.org
Bart van Leeuwen
@semanticfire
Sarven Capadisli
@csarven
Currently using http://blog.resc.info/ as your homepage @semanticfire
Sarven Capadisli
@csarven
@cuent Any chance of you pulling off a Sender or Consumer implementation?
Bart van Leeuwen
@semanticfire
@csarven maybe do the company one http://netage.nl
Sarven Capadisli
@csarven
@semanticfire Do you have an implementation in the works?
March 14 (next Tuesday) we hope to be able to go to Proposed Recommendation. A few more Consumer implementations will solidify things.
Bart van Leeuwen
@semanticfire
not by next tuesady :smile:
Sarven Capadisli
@csarven
Any rough ETA? This is useful to know in case there are a few more others which might submit later on.. and so we could push the PR later.
Bart van Leeuwen
@semanticfire
hopefully before summer
Sarven Capadisli
@csarven
Sender is relatively trivial to implement, Consumer is not bad.. Receiver is more involving
Ok
Bart van Leeuwen
@semanticfire
is that specific enough ?
Sarven Capadisli
@csarven
yes
WG charter ends June
Xavier Sumba
@cuent
I'll to try to get the work done this weekend.
Can the version of Apache Marmotta be included in the implementation report?
Sarven Capadisli
@csarven
Yes, of course. I can update. Which version.. in the implementation name right?
Do you have a more permanent location for your FOAF than github?
Xavier Sumba
@cuent
I think you can use http://cuent.me because I owe the domain.
Yes, the report was made with the version 3.3.0. As a note, we can add that it also was tested in the upcoming version 3.4.0.
Sarven Capadisli
@csarven
@cuent I updated the report's note, thanks.
Sarven Capadisli
@csarven
@cuent Is it possible for Marmotta to access control some notifications as mentioned here https://www.w3.org/TR/ldn/#test-receiver-get-notifications-limited
Sarven Capadisli
@csarven
for example, if the inbox has n1,n2,n3, but may only show ldp:contains n1,n3 to me.
Sarven Capadisli
@csarven
@cuent Another test is this "Receivers SHOULD use constraints to filter unwarranted notifications from being created on the server and exposed by the Inbox." .. I noticed that Marmotta has ldp:constrainedBy, but are there reasons why a notification may be rejected (due its RDF shape or something in or not in the headers)?
Xavier Sumba
@cuent
IDK, let me try tonight!
Sarven Capadisli
@csarven
Thanks
semanticfire @semanticfire finally found time to look at LDN
Bart van Leeuwen
@semanticfire
the contents of the notifications themself are freeform right ?
Sarven Capadisli
@csarven
@semanticfire Absolutely. Entirely depends on applications' needs.
Bart van Leeuwen
@semanticfire
I'm trying to wrap LDN around a JMS Topic containing updates
but that is tricky since Topic message consumption is a destructive read
can I inline the notification within a inbox fetch ?
Sarven Capadisli
@csarven
I don't think I understand the question
Bart van Leeuwen
@semanticfire
If I request ../inbox
the inbox should reference notifications it has, can these notifications also be inlined to the inbox ?
or phrased differently, can I get the inbox and the notification contents in one GET
Sarven Capadisli
@csarven
I see. That's not defined by LDN. Each notification would need to resolve. If the Inbox also includes the notifications contents in its own description, that's fine. That extra bit is not part of LDN
Bart van Leeuwen
@semanticfire
I'd like to prevent the extra roundtrip, and solve my destructive read problem in one go
Sarven Capadisli
@csarven
LDN sets no restriction on Inbox's description other than listing the notification URLs with ldp:contains
Bart van Leeuwen
@semanticfire
and they must resolve ?
Sarven Capadisli
@csarven
Yes, but that may be subject to other constraints e.g., access control. Not related to the Inbox URL itself.
Bart van Leeuwen
@semanticfire
I see
Sarven Capadisli
@csarven
Basically, if your Receiver is capable of resolving the individual notifications, that'd conform. Whether they actually resolve in your setup or not is something else.
Bart van Leeuwen
@semanticfire
I'm more on the consumer side with my implementation
Sarven Capadisli
@csarven
Yea, normally the Consumer will have to follow-up on the ldp:contains values and fetch
Same thing though. Your implementation may do something extra (like what you describe) but the baseline is what I described.