Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 05 14:43
    inakijaneiro added as member
  • Oct 13 2020 17:32
    MrJuanVilla added as member
  • Oct 13 2020 17:32
    andreacorrea89 added as member
  • Apr 12 2020 00:23
    andynice labeled #16
  • Apr 12 2020 00:23
    andynice labeled #16
  • Apr 12 2020 00:23
    andynice opened #16
  • Jan 07 2020 00:51
    roddolf added as member
  • Jun 19 2019 21:34

    mhernandeza on master

    Update issue templates (compare)

  • Jun 19 2019 21:05

    mhernandeza on master

    Update issue templates (compare)

  • Jun 19 2019 20:24
    maggsmg closed #2
  • Jun 19 2019 20:22

    maggsmg on master

    Update README.md (compare)

  • Jun 19 2019 16:48
    MiguelAraCo edited as member
  • Jun 19 2019 16:40
    MiguelAraCo added as member
  • Jun 19 2019 16:37
    Frost-bit removed as member
  • Jun 19 2019 16:29
    Frost-bit added as member
  • Dec 01 2018 01:22

    MiguelAraCo on master

    Delete file left by GitBook (compare)

  • Dec 01 2018 01:20
    MiguelAraCo deleted #7
  • Dec 01 2018 01:20
    MiguelAraCo closed #8
  • Dec 01 2018 01:20
    MiguelAraCo commented #8
  • Dec 01 2018 01:19
    MiguelAraCo closed #9
Cody Burleson
@codyburleson
I notice in the document tree from within the Workbench that there is now a vocabularies/ container (with <vocab>/shapes/) inside. Is this container intended to be restricted as a sort of system-managed container? Or is there some way that it might be of usefulness to end-users too? The reason why I ask is that I have an idea that involves use of the Shapes Constraint Language (SCHACL). So, I'm just kind of wondering if I wanted to define some shapes of my own, is there any usefulness or convention for doing that in some relation to the existing vocabularies/ container?
Miguel Aragón
@MiguelAraCo
It is not limited to the system. Any document prepended with a . is marked as a system managed document
We have plans to use this document to provide things like custom validation (using SHACL) and other vocabulary-related features
Cody Burleson
@codyburleson
OK.
Miguel Aragón
@MiguelAraCo
We just published a new version of the platform:
carbonldp/carbonldp-platform:1.0.0-alpha.7
It includes several bugfixes. If you are using the alpha version, please update your instances
Miguel Aragón
@MiguelAraCo
Just published a new version of the JS SDK: v1.0.0-alpha.8. It fixes a minor bug. Please update your projects to use this version if you are using the alpha line
Alex Arriaga
@alex-arriaga

I have a sugestiong for the documentation in the Quick Start Guide. I was configuring my Carbon instance in a production-ready environment using Linode (just because we wanted to test that provider instead of localhost).

I went through the installation/configuration process using this guide https://carbonldp.com/documentation/v1.0.x/quick-start-guide/ and in the step 1.1 Create the platform's configuration file there is an example of a config.yaml file for localhost.

I made a really beginner mistake… using the default config.yaml file and running this command for starting both Carbon Platform and Carbon Workbench

docker run -d --name carbonldp-platform -p 8083:8083 \
    -v /opt/carbonldp:/opt/carbonldp/shared \
    carbonldp/carbonldp-platform:1.0.x-alpha

docker run -d --name carbonldp-workbench -p 8000:80 \
    -e “CARBON_HOST=carbonldp.webtraining.zone:8083" \
    -e "CARBON_PROTOCOL=http" \
    carbonldp/carbonldp-workbench:1.0.x-alpha
Of course, that didn’t work because I wanted my instance running on carbonldp.webtraining.zone:8083 but I didn’t change the host in the config.yaml file!!
So, when I tried to open my Carbon Workbench, it could’nt connect to the platform
Alex Arriaga
@alex-arriaga
Screen Shot 2018-01-13 at 12.45.01 PM.png
So, it would be great if you can add another example of a config.yaml but with an actual fully qualified domain name
Something, like: When you are configuring Carbon LDP with a fully qualified domain, be sure you modify your config.yaml accordingly, as in following example:
Alex Arriaga
@alex-arriaga
2) Another really cool feature when reading documentation is to be able to share an specific section of a page. For example in Github all the h1…h6 have a “on-hover anchor” that you can copy and share, for example:
Screen Shot 2018-01-16 at 2.56.42 PM.png
3) In a lower priority, I went to the ES2015 boilerplate, and I realized it has an old version of the Carbon JavaScript SDK https://github.com/carbonLDP/carbonldp-js-es2015-boilerplate easy to fix, just doing the npm install… :)
Miguel Aragón
@MiguelAraCo
In the boilerplates please use branch v1.0.x-alpha
That's the one that we are keeping up-to-date with the alpha line
Alex Arriaga
@alex-arriaga
Excellent!
Miguel Aragón
@MiguelAraCo
1) Thanks for the suggestion, we'll try to make it clearer that you need to change some values depending on your particular configuration
2) That's a very good suggestion, we'll definitely incorporate it into our documentation
Alex Arriaga
@alex-arriaga

4) One of the things we usually ask ourselves is how to translate our Object Oriented programs into Linked Data stuff, (for example how to name the properties for a given schema, what is the equivalent to a relationship between OO classes, etc.).

Let's imagine I want to create a Blog in Carbon, I could have two data models with these kind of relations:

Post hasMany Comment
Comment belongsTo Post

In an Object Oriented approach this relations could be modeled as follows:

class Post {
    comments: List<Comment>;
}

Comment {
    post: Post
}

Translated into a "Linked Data" mindset:

Post should have an schema with properties
Comment should have an schema with properties
That's very clear...

However, when talking about how to represent my "comments" list, things change... should that be a container? what is container anyways? should that be an access point?

It would be awesome to have documentation about "How to translate an Object Oriented System into its Linked Data version”.

I created this github issue: CarbonLDP/carbonldp-website#193 ;)
Miguel Aragón
@MiguelAraCo
The concept of container has been pulled away from our new documentation
Miguel Aragón
@MiguelAraCo
Users of past versions please try to think about the objects as just documents
Alex Arriaga
@alex-arriaga
I see, I see
Miguel Aragón
@MiguelAraCo
There is a section that talks about lists under the https://carbonldp.com/documentation/v1.0.x/javascript-sdk/getting-started/
And there is no "correct" way of translating a list from an object oriented world to a linked data world
It's still a list
You can create an access point to manage that list
If you do, the access point will allow you to add/remove members with a single request and that's it
But it is not needed. Any list is just a series of values assigned to an object's property
The getting started page tries to answer the question "How to translate an Object Oriented System into its Linked Data version" by simply saying: you don't need to
Miguel Aragón
@MiguelAraCo
(Although it doesn't explicitly say that... maybe we should create a FAQ section)
The only thing that you need to be worried about, is if you want your objects to be documents on their own, or be fragments of another document. Which is covered in the page "Object model"
Miguel Aragón
@MiguelAraCo
You have a lot of options:
  • Store post's comments as descendants of the post via an AccessPoint. Meaning comments will end up having IDs like: posts/my-post/comments/123123/
  • Store post's comments as children of a document that will hold all of the sites comments. After that, link the comment to its post. Meaning comments/123123/
  • Store post's comments as fragments of the post. Meaning _:123123 inside posts/my-post/
  • Store post's comments as named fragments of the post. Meaning posts/my-post/#comment-12312
Which one is the best? Depends on the situation and your particular requirements
(Don't get me wrong, I think we need to state this somewhere in the documentation, I'm just writing it here for now)
AlexSerrano22
@AlexSerrano22
hi again :P
CarbonLDP/carbonldp-platform#8

and a comment about the documentation of creating an access point on the tab "JavaScript ES2015", you have this lines:

        return project.refresh<Project>();
        return person1.refresh<Person>();

but the classes are on "typescript" only :P

Miguel Aragón
@MiguelAraCo
Please help us by creating issues for any typo or mistake in the documentation, in the https://github.com/CarbonLDP/carbonldp-website repository
AlexSerrano22
@AlexSerrano22
ok
Miguel Aragón
@MiguelAraCo
Thank you for reporting them :smile:
AlexSerrano22
@AlexSerrano22
CarbonLDP/carbonldp-website#194
Miguel Aragón
@MiguelAraCo
:clap:
Alex Arriaga
@alex-arriaga
Perfect @MiguelAraCo
Cody Burleson
@codyburleson
Perfect? Hmmm... I wouldn't go that far. ;-)
Alex Arriaga
@alex-arriaga
:D
Miguel Aragón
@MiguelAraCo
Just published a new version of the platform: 1.0.0-alpha.8. The docker image 1.0.x-alpha now points to that version as well. It includes a somewhat critical bug so we advise you to update your instances if you are using the alpha line.