oslc / oslc4net Goto Github PK

mffiedler[CodePlex]
Initial port of OSLC4J does not have the ServiceProviderFactory required to create ServiceProvider resources.

E.g., string not String.

The relevant property is only supported my MSBuild since .NET 5: https://learn.microsoft.com/en-us/nuget/reference/msbuild-targets#packagereadmefile

We are using MSBuild due to MS guidance to do so given that we migrated the project to use PackageReference dependency management.

I would like to be able to use dotnet CLI to publish to NuGet before the migration to .NET 6/Core given that 49% of projects still use .NET Framework and we may need to dual-target the OSLC4Net.Client for a few releases.

Prevents the sample project from running out of the box.

MS link: https://technet.microsoft.com/en-us/library/hh873188(v=vs.110).aspx

I would like to:

1. Have common properties shared across a subset of projects within the solution. Right now, every project includes a set of properties show below. Primarily, I would like to update VersionSuffix and Version in a single place.
2. Synchronize the updates to the MSBuild Version, assembly AssemblyVersion as well as AssemblyFileVersion (which CLR doesn't care about, apparently, but which we should still keep in sync unless we can completely drop it).

<Version>0.3.0-alpha</Version>
<VersionSuffix>alpha</VersionSuffix>
<PackageLicenseExpression>EPL-1.0</PackageLicenseExpression>
<Authors>Andrii Berezovskyi and OSLC4Net contributors</Authors>
<PackageReadmeFile>README.md</PackageReadmeFile>
<!-- TODO: remove PackageOutputPath after migration to .NET Core-->
<PackageOutputPath>MSBuild_Nuget_Pack/</PackageOutputPath> 
<PackageProjectUrl>https://github.com/OSLC/oslc4net/</PackageProjectUrl>  <RepositoryUrl>https://github.com/OSLC/oslc4net/</RepositoryUrl> 

Targets .NET 3.5, last release in 2013, a security risk.

https://www.nuget.org/packages/DotNetOpenAuth.Core/

Dependency exists in OSLC4Net.Client.Oslc.Jazz.

Replacement candidate: https://restsharp.dev/. Should also allow OSLC4Net.Client.Oslc.Jazz to be migrated to net6.0+.

Needed for .NET Core https://docs.microsoft.com/en-us/aspnet/core/web-api/advanced/custom-formatters?view=aspnetcore-6.0

Downloaded this OSLC4Net build and was trying to retrieve data from RTC 7.0.2. The code is getting authenticated at client.FormLogin() and returning a OK status code. But when it is trying to fetch service provider URL based on catalog URL for the respective project area by the "client.LookupServiceProviderUrl(catalogUrl, projectArea);" it is giving the following response --

{"OSLCC004: The requested resource could not be found. "}
{StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
Strict-Transport-Security: max-age=31536000
WWW-Authenticate: Basic realm="JSA"
WWW-Authenticate: Bearer realm="JSA"
X-Powered-By: Servlet/3.0
X-JSA-AUTHORIZATION-URL: https://jazz702-jas.in.kovair.com:9643/oidc/endpoint/jazzop
X-JSA-AUTHORIZATION-REDIRECT: https://jazz702-jas.in.kovair.com:9643/oidc/endpoint/jazzop/authorize?client_id=a45241f7523e47938c26a0fb573f3aee&response_type=code&state=security_token1%3DpwXwH5CYJWwSdWMIqE2KVQoJTNvJec6JrJWDg5zURKw%3D%26security_token2%3DC%2BumLl1CViIUQxm2HLp3CxwO0VZuDLR3n8zIi5kE32w%3D%26return%3Dhttps%253A%252F%252Fjazz702-jas.in.kovair.com%253A9443%252Fccm%252Foslc%252Fworkitems%252Fcatalog%26scope%3Dopenid%2Bgeneral%2Bprofile%2Bemail%2B%26impersonation%3Dtrue&scope=openid+general+profile+email+&redirect_uri=https%3A%2F%2Fjazz702-jas.in.kovair.com%3A9443%2Fccm%2Fjsa
Set-Cookie: JSA_CSRF_b179c159-8dc3-4ecf-910b-0fe1c5969e5c=153579c3-8bea-44af-9d68-947497117191; Path=/ccm; Secure
Date: Tue, 15 Mar 2022 16:28:58 GMT
Cache-Control: no-cache="set-cookie, set-cookie2"
Content-Length: 0
Content-Language: en-US
Expires: Thu, 01 Dec 1994 16:00:00 GMT
}}

Do we need to provide any other header or any other mechanism in order to fetch data from RTC 7.0.2(authorization server) via OSLC4Net? Please provide the required fix for the above problem

OSLC4Net.Core.JsonProvider currently relies on System.Json as its main API (despite including the NuGet dependency on Newtonsoft.Json, which doesn't seem to have been used). System.Json was replaced with System.Text.Json as the recommended JSON processing approach.

The legacy System.Json namespace is not available in netstandard2.0. It should be possible to drag the legacy dependency via https://www.nuget.org/packages/System.Json#supportedframeworks-body-tab into netstandard2.0, but I was unable to get it working in #98 and removed OSLC4Net.Core.JsonProvider from the build (#109 re-adds it to the SLN).

mffiedler[CodePlex]
Need to add support for JSON to OSLC4Net. We should take a look at possibly using a JSON-LD representation (http://json-ld.org/). It looks like the dotNetRDF project has considered it, but it is in their
backlog right now:
http://dotnetrdf.org/content.asp?pageID=Ideas

We would also need to put together a Razor template to render the dialog.

Hi,
I'm a new beginner of OSLC, and I'm learning on your project.
I studied the StockQuoteSample project, I noticed we could add the "OslcDialog" and "OslcQueryCapability" on the same function(GetStockQuotes). From my understanding, this function "GetStockQuotes" is a "GET" function, why can you put the annotation "OslcDialog" on this function? In other words, what functions can we declare as "OslcDialog", and how about the "url" of "OslcDialog"?

We need some automated build to make sure the project is minimally usable.

Failed build: https://ci.appveyor.com/project/berezovskyi/oslc4net/build/1.0.1

Hi,

I see OSLC4Net uses an old .NET Framework and I would like to know if you plan to migrate to a newer version e.g. .NET Core 6 or to .NET Standard 2.0 as supported by dotNetRDF.

Thanks,

OSLC4Net relies on dotNetRDF for serialisation support. JSON-LD is a very interesting development that could bring Linked Data closer to the modern web full of fads. Unfortunately, dotNetRDF still has not implemented JSON-LD support: dotnetrdf/dotnetrdf#41

https://learn.microsoft.com/en-us/visualstudio/test/mstest-update-to-mstestv2?view=vs-2022

mffiedler[CodePlex]
Create some initial API documentation using XML comments

In OSLC4Net.StockQuoteSample.WebApiConfig#Register context.Request is being accessed.

.NET throws an exception:

System.Web.HttpException: Request is not available in this context

Which is reasonable as the method is called outside an HTTP request.

I would suggest to create OSLC4NET.Samples solution and move the client and server samples there.

Files like https://github.com/OSLC/oslc4net/blob/master/OSLC4Net_SDK/OSLC4Net.ChangeManagement/ChangeRequest.cs should be kept in sync with https://open-services.net/specifications/

• make sure the README does not make the project look abandoned
• merge with the https://github.com/OSLC/oslc4net/blob/master/doc/building.md
• point to Nuget instead of manual builds after #65 is done

We should not require people to clone OSLC4NET and build the DLL before starting to use it.

Actually, we should publish the following packages on NuGet:

• OSLC4NET.Core
• OSLC4NET.Core.Providers.RdfXml
• OSLC4NET.Core.Providers.Json
• OSLC4NET.Core.Domains.Config
• OSLC4NET.Client

• update dotnetrdf version only to the latest 1.x for now
• upgrade the GH Action, see https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ and https://github.com/microsoft/setup-msbuild
• update log4net version
• Update https://www.nuget.org/downloads executable
• set RestorePackages to true and RequireRestoreConsent in the NuGet.targets
• deprecate OSLC/JSON provider
• #66
• #65
• #67
• #69
• #68

New 2023 items:

• update dotNetRdf at least to 1.0.0.2533 (a mix of that version and 0.9.0.2110 was encountered, downgrade was made temporarily to keep things uniform) updated to 1.0.13

mffiedler[CodePlex]
Add a plain text version of the EPL V 1.0 to the source

mffiedler[CodePlex]
This will be a port (of sorts) of the OSLC4JStockQuote application to the OSLC4Net project. The StockQuote provider will be a sample OSLC provider which is not implemented for a traditional (CM, QM, RM, etc) domain.

The StockQuote sample defines 1 resource: StockQuote which has such predicates as lastTradedPrice, highPrice, lowPrice, changePricePercent etc. The Google stock quote API will be used to populate the values.

The sample will demonstrate how to use the OSLC4Net attribute notations to quotdecoratequot a C# class with OSLC attributes. It will also demonstrate how to:

• create ASP.NET MVC 4 controllers to handle the HTTP REST calls
• register the OSLC4Net RdfXmlMediaTypeFormatter to handle application/rdf+xml and application/xml.

https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/

cayrong[CodePlex]
hi,
i download the sample using GitHub but i can't compile it, the NuGet keep failing to retrieve missing packages.

i''ve tried to compile it using vs 2010 amp 2012 none works.

thanks

They should be replaced with the NuGet dependencies:

• https://www.nuget.org/packages/dotNetRDF/1.0.0.2473

• https://www.nuget.org/packages/Newtonsoft.Json/5.0.4

• https://www.nuget.org/packages/VDS.Common/1.2.0

All the headers set before a GetResource call are wiped out. I cannot add my own headers

First NuGet packages were published manually because all guides with better approaches required .NET Core / .NET 5, while we were targeting .NET4.8. Now that we target .NET 6+, we should modernise our NuGet deployment pipeline.

Hi,
Thanks all for the good work, but now I want to create a new requirement in a existing folder other than Root Folder.
I don't find any support in the client.
Regards
Dieter

CM tests currently target an old version of Lyo CM samples:

https://github.com/OSLC/oslc4net/blob/e9a3107a49f21ead209c716d8c003fa7d5258df3/doc/building.md#running-the-changemanagement-tests

We should migrate to using https://github.com/oslc-op/refimpl

I was trying to figure out where acceptance tests define their URIs and the answer was: nowhere! The library code is set up to guess a URI if null is provided.

We shall not be doing this. OSLC Core 3.0 defines discovery on a given domain (and thus, a URI, if you strip off the original path) via a /.well-defined/ URI and not though some magic like "http://" + IPGlobalProperties.GetIPGlobalProperties().HostName+ ":8080/";

Unfortunately, this will be a breaking change.

mffiedler[CodePlex]
Switch from checking prereq binaries into source control to using NuGet

This is a minor issue though as VS 2017 suggests to install ASP.NET MVC 4 support tooling automatically.

Will allow us to host docs on oslc4net.github.io and to set up various apps like https://github.com/marketplace/codefactor/ and https://github.com/marketplace/codecov without security concerns for the rest of the projects here.