• Interoperability
• Semantic Web & Linked Data
• Requirements Management (RM)
• Crystal Project
• OSLC
• Example 
• Conclusions and Future Work

• Common and shared data model
• Graph (subject, object, predicate)
• RDF with different serialization formats
• Implicit Multilinguism suport
• Knowledge Representation
• Ontologies
• OWL (Ontology Web Language)
• Logic formalism: DL, F-Logic, etc.
• Reasoning

• Knowledge management
• Expert systems
• Standards
• Query Languages
• Vocabularies
• Datasets
• ...

jose-foaf: http://www.josemalvarez.es/foaf.rdf#.
diego:foaf: http://berrueta.net/foaf.rdf#.

jose-foaf:me foaf:name “Jose”.

jose-foaf:me foaf:family_name “Alvarez”.

jose-foaf:me foaf:knows diego-foaf:me.

diego-foaf:me foaf:name “Diego”.

• We are a public body
  
• We want to buy "beds" for a new hospital
  
• The call is open to any European entity
• Data
• Type of object (Common Procurement Vocabulary)
• Location (Greece)
• Multilingual environment 
• Value / Quantity / currency
• ....

• Data sources
• Official bulletins, web pages, newspaper, etc.
• Formats
• HTML, PDF, XML, PNG, etc.
• Languages
• 23 official languages in Europe
• Models, services and APIs
• XML-Schema, SQL, REST, WSDL/SOAP, etc.

1. Use URIs to name things
   
2. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL).
3. Use HTTP URIs.
4. Include links to other URIs.

• Web-based standards
• HTTP URIs
• Common and shared data model RDF graph
• Syntaxis: RDF/XML, JSON, Turtle, etc.
• SPARQL  as query language
• Implicit multilingualism support
• Reasoning enabled
•  Meta-described properties
• E.g. value and currency

• Activities
• Elicitation
• Analysis and negotiation
• Documentation
• Quality assessment 
• ...
• A key-process in critical systems
• Validation
• Verification

• Requirements-driven engineering ( What? )
  
• Focus on  requirements
• E.g. RDE
• Model-based systems engineering ( How? )
• Focus on models
• E.g. MDA, MDE, MDD, etc.
• Model-driven requirements engineering ( What + How? )
• Conjunction of models and requirements
• E.g. MDRE

• Tangled environment of tools/techniques/methods
• Data sources
• IBM Doors, Reqtify, Rational Rose, RAT, KM etc.
• Formats
• XMI, ReqIF, etc.
• Languages
• ...
• Models, services and APIs
• XML-Schema, SQL, REST, WSDL/SOAP, etc.
• Link of requirements to models to...
• share a common vocabulary
• model the Product Breakdown Structure (PBS)
• ensure quality: understandability, traceability, etc.

• Build on the WWW
• HTTP REST
• CRUD operations
• Auth methods
• Keep things simple
• Consensus
• Accommodate different schemas
• Accommodate different representations
• RDF/XML, JSON, ATOM, etc.
• Align with the W3C Linked Data initiative
• Follow the Linked Data principles

• Domain
• Service
• Service Provider
• Resource
• Resource Shape
• Creation Factory
• Query Capability
• Response Info Resource
• ...

• Defined Resources

• Defined Properties

• Management of requirements through OSLC
• Defined resources

• Requirements Resource
• Requirement Collection Resource
• Service Provider
• Service Consumer

• A Linked Data approach for a specific domain
  
• OSLC Resource shape similar to describe a dataset
• How RDF is generated? 
• On-the-fly
• Wrapper on existing database
• Two synchronized databases (e.g. Virtuoso and SQL)
• See:  http://linkeddatabook.com/editions/1.0/#htoc65
• SPARQL is missing...
• New syntax for same functionality
• Specifications under development
• Authentication
• HTTPAuth is recommend
• OAuth was not created for these purposes (http://insanecoding.blogspot.com.es/2013/03/oauth-great-way-to-cripple-your-api.html)

• Good approach but...
• It requires more information on how to...

1. Controlled vocabulary and ontology
   
2. Product Breakdown Structure
   
3. Services to manage domain knowledge
   

• SIMPLE
• KNOWLEDGE
• ORGANIZATION
• SYSTEM




USE OF SKOS

• Controlled vocabulary
• Taxonomies
• Thesauri
• Folksonomies,  etc.

• Define concepts and concept schemes

• Classes and categories
  
• skos:Concept and skos:ConceptScheme
• Properties
• Lexical labels
• Notation
• Documentation
• Mapping
• Semantic

1. Model Concepts in SKOS
2. URI Design
3. Create concepts
4. Add authoring properties
5. Add labeling properties
6. Add notation properties
7. Add  documentation properties
   
8. Add semantic properties
9. Add mapping properties
10. Add concepts to a scheme
11. Describe the concept scheme

http://patterns.dataincubator.org/book/identifier-patterns.html

http://data.gov.uk/resources/uris

• Select type of property
• Transitive
• Symmetric
• ...

http:// www.w3.org/2004/02/skos/extensions/spec/2004-10-18.html#broaderPartitive

• A concept-oriented model
  
• RDF-based 
  
• a common and shared data model
• Crucial contribution to interoperability
  
• A way of porting KOS to RDF
  
• Align to existing standards (ISO 25964)
• Lightweight reasoning
  
• Simple but powerful
  
• Extensible
  
• Widely-used in existing semantic web vocabularies
  
• Boosting the Linked Data initiative

• OSLC Requirements Management
• A first prototype to tackle the aforementioned challenges
• A SKOS-based approach
• Use of the Eclipse Lyo OSLC API
• OSLC Quality Management
• First approach on top of the RDF-Data Cube vocabulary
• To model (reuse existing quality metrics)  and
• ... compute
• ... quantitative indexes
• Services for knowledge management
• Inspired by the JENA OntModel interface
• http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/ontology/OntModel.html
  

• Requirements Management is a key-process for the development of critical systems
• Requirement as a basic unit of specification
• Link requirements to models
• Verification and Validation
• Model-driven Requirements Engineering (MDRE)
• Quality Management
• Support ISO standards (250XX)
• OSLC to ensure compatibility among tools
• Linked Data in a controlled environment...

• Research
• Identify more services to be offered via OSLC
• Apply the Linked Data principles to Requirements and Quality Management specs.
• Development
• Full prototype
• Innovation
• Support to The Reuse Company Inc. to offer through OSLC
• RAT (Requirements Authoring Tool)
• KM (Knowledge Manager)
• RQA (Requirements Quality Analyzer)
• http://www.reusecompany.com/

• Speaker: Dr. Jose María Alvarez-Rodríguez
• Carlos III University of Madrid, Spain
• Member of the OSLC RM working group
• E-mail: josemaria.alvarez@uc3m.es
• WWW: 
• http://purl.org/krgroup/web
• http://www.josemalvarez.es
• Team:
• KR group
• Prof. Dr. Juan Llorens
• Prof. Dr. Juan Miguel Gómez, 
• Dr. Anabel Fraga
• Dr. Valentín Moreno
• Ms. Manuela Alejandres
• Mr. Jose Fuentes (The ReuseCompany Inc.)

• Diagrams from OSLC specs. http://open-services.net/
• http://www.slideshare.net/josem.alvarez/skos-intro