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=59697#comment-59697 ] 

James Amsden commented on OSLCCORE-9:

Martin, can you describe how that would work, and provide the 2.0 compatibility? 

Currently OSLC Core 3.0 discovery is simply an OPTIONS request on an LDPC which returns link headers that contain metadata about the capabilities of that container. Are you suggesting a Service Provider Catalog would be an LDPC, as would a Service Provider and a Service? I can see that - with Service Provider Catalog and Service Provider representing LDPCs that only contain other LDPCs in a hierarchy. Not sure that restriction is really needed. 

So a rootservices URI would reference an LDPC whose type is also ServiceProviderCatalog which could contain ServiceProvider LDPCs which could contain Service LDPCs? Is that what you mean?

> 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]