OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCORE-9) Bootstrapping discovery

    [ https://issues.oasis-open.org/browse/OSLCCORE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59593#comment-59593 ] 

James Amsden commented on OSLCCORE-9:

One answer for the root URL might be / itself. With no other information, that would be a logical starting point. However, we can expect that clients have to at least be given some information about the source of OSLC domain information including:
- the required protocol and authentication requirements
- the server
- the correct port to access
- what information domains are availble
- and possibly the LDP container to start with.
That is, they will be given a URL, and that URL would be the starting point for discovery. Clients will have to make some assumptions if any of this information isn't provided in the URL - including default ports and / as the root LDP container for a server. 

I'm not sure there's anything else we could require, or if this is any different than any other URL a client might need to access.

Do we need to say anything about this? e.g., Servers SHOULD make known LDP containers supporting OSLC discovery? / SHOULD be discoverable? OSLC servers SHOULD use 9443 as the default port? I'm not convinced this is really necessary, or that there is any standard way outside of LDP containers that discoverable URLs could be made known.

> Bootstrapping discovery
> -----------------------
>                 Key: OSLCCORE-9
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-9
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: Martin Pain 
>            Assignee: James Amsden
> See https://lists.oasis-open.org/archives/oslc-core/201503/msg00016.html
> See also a draft from Mark Nottingham about HTTP home documents: http://tools.ietf.org/html/draft-nottingham-json-home-03 (I haven't read it yet)

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]